All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 9 Dec 2005 17:27:17 +0000	[thread overview]
Message-ID: <20051209172717.GC31708@flint.arm.linux.org.uk> (raw)
In-Reply-To: <BAY103-F33F72FF201DD9A0728D2EBDF450@phx.gbl>

On Fri, Dec 09, 2005 at 08:37:01AM -0600, Jason Dravet wrote:
> 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?

I guess so - I don't look after the virtual console stuff.

> 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.

There is a key combination, but it's dependent on the keymap.
dumpkeys -f and search for "Console_" - it's in keymap 2 (but
I don't know what activates keymap 2.)

> 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?

If you're considering only legacy free systems, yes you are probably
right.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-12-09 17:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  3:02 wrong number of serial port detected Jason Dravet
2005-12-08 10:54 ` Russell King
2005-12-09 14:37   ` Jason Dravet
2005-12-09 17:27     ` Russell King [this message]
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=20051209172717.GC31708@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=dravet@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.