From: "Jason Dravet" <dravet@hotmail.com>
To: rmk+lkml@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: wrong number of serial port detected
Date: Fri, 09 Dec 2005 08:37:01 -0600 [thread overview]
Message-ID: <BAY103-F33F72FF201DD9A0728D2EBDF450@phx.gbl> (raw)
In-Reply-To: <20051208105425.GA28397@flint.arm.linux.org.uk>
>From: Russell King <rmk+lkml@arm.linux.org.uk>
>To: Jason Dravet <dravet@hotmail.com>
>CC: linux-kernel@vger.kernel.org
>Subject: Re: wrong number of serial port detected
>Date: Thu, 8 Dec 2005 10:54:26 +0000
>
>On Wed, Dec 07, 2005 at 09:02:03PM -0600, Jason Dravet wrote:
> > >As for your 64 VT tty device nodes - these "devices" are created
> > >dynamically when the device node is opened. The act of opening the
> > >device node is defined to be the creation event. If the device node
> > >did not exist, there would be no way to create _any_ virtual terminals.
> >
> > I thought there were only 7 tty devices (Ctrl-F1 to Ctrl-F7) for local
> > system login? Ctrl-F7 being for Xwindows. Did I miss something?
>
>If you look in the "init" configuration file, /etc/inittab, you'll
>see lines similar to these:
>
The /etc/inittab file is where I got the number 7 from (6 tty plus 1
Xwindows). I have to change the inittab everytime I install FC since they
switched to graphical boot (FC does not like my monitor). Let me see if I
got this right: Is the reason 64 tty devices exist similiar to the reason
you gave me about the 32 serial ports? You create all the nodes so they can
be used at anytime. If there were only the 6 tty nodes created then if you
want to direct your logger to tty12, you would first have to create that
node and then tty12 could be used. If this is true how are the other 52 tty
devices accessed? I don't have a F13 or F44 keys on my keyboard.
I like the idea of the patch that Dave Jones created. The question I have
is with all of this plug and play stuff in our PCs shouldn't it be possible
to get the correct number of ports, ask the bios or the pci bus or
something?
Thanks,
Jason
next prev parent reply other threads:[~2005-12-09 14:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 3:02 Jason Dravet
2005-12-08 10:54 ` Russell King
2005-12-09 14:37 ` Jason Dravet [this message]
2005-12-09 17:27 ` Russell King
2005-12-09 19:54 ` Bjorn Helgaas
2005-12-10 1:46 ` Jason Dravet
2005-12-10 10:35 ` Russell King
2005-12-10 14:24 ` Jason Dravet
2005-12-10 15:46 ` Russell King
2005-12-10 17:56 ` Jason Dravet
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 15:44 Jason Dravet
2005-12-07 15:50 ` Russell King
2005-12-07 19:59 ` Jason Dravet
2005-12-07 21:15 ` Russell King
2005-12-07 21:28 ` Xavier Bestel
2005-12-07 21:31 ` Russell King
2005-12-07 21:38 ` Russell King
2005-12-07 23:03 ` Dave Jones
2005-12-07 23:46 ` Russell King
2005-12-08 0:50 ` Dave Jones
2005-12-08 3:09 ` Dave Jones
2006-01-07 16:46 ` Russell King
2006-01-07 21:05 ` Dave Jones
2006-01-08 1:23 ` Jason Dravet
2006-01-08 9:08 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY103-F33F72FF201DD9A0728D2EBDF450@phx.gbl \
--to=dravet@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®