mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cox <steel300@gentoo.org>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change number of tty devices
Date: Thu, 22 Apr 2004 02:24:06 +0000	[thread overview]
Message-ID: <E1BGTsk-0000va-Bx@smtp.gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0404212109580.10680-100000@phoenix.infradead.org>

On Wed, 21 Apr 2004 21:14:38 +0100 (BST)
James Simmons <jsimmons@infradead.org> wrote:

> 
> > Often, I have wondered what the need for 64 tty devices in /dev is.
> > I began tinkering with the code and am wondering why it's not user
> > configurable. I came up with a quick patch to add it as an option
> > under drivers/char/Kconfig. I also made a lower bound of 12. If this
> > is an idea worth pursuing, please let me know. If this idea has been
> > rejected before, I apologize. What do you think of this idea?
> 
> The reason for 64 is that the major number is shared between the
> serial tty and VT tty drivers. The first 64 to Vts and the rest to
> serial devices. 

First off, thanks for the reply. Does lowering the number of tty devices
interfer with the creation of serial consoles? Can't they start at the
same major number without an issue?

> What is even more is that there exist ioctls that return shorts 
> which means only 16 VCs can be accounted for on a VT. 

So is my limit wrong? Should I up the lower limit to 16 to account for
this? 

> When the kernel supports multi-desktop systems we will have to deal
> with the serial and VT issue. Most likely the serial tty drivers will
> be given a different major number. 

Why isn't this done now?

> I personally believe that because
> of the 16 bit limit that there should be 16 VCs per VT terminal. 

That does make sense.

Just a side note: I have been running with 12 (0 - 11) tty devices
without issue. I haven't tried a serial console, but will shortly, just
to see if it interferes with serial console creation.

Thanks,
Jason Cox


  reply	other threads:[~2004-04-22  2:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 22:38 Jason Cox
2004-04-20 12:38 ` [PATCH] " Jason Cox
2004-04-21 20:14 ` James Simmons
2004-04-22  2:24   ` Jason Cox [this message]
2004-04-22  8:33     ` Russell King
2004-04-25  3:15       ` James Simmons
2004-04-25  4:01         ` Horst von Brand
2004-04-25  7:33         ` Russell King
2004-04-25  3:19     ` James Simmons
2004-04-22  3:15   ` Jason Cox

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=E1BGTsk-0000va-Bx@smtp.gentoo.org \
    --to=steel300@gentoo.org \
    --cc=jsimmons@infradead.org \
    --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 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®