Date: Fri, 2 Jan 2004 00:36:52 +0000
From: viro@parcelfarce.linux.theplanet.co.uk
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Tommi Virtanen <tv@tv.debian.net>, Rob Love <rml@ximian.com>,
       Nathan Conrad <lk@bungled.net>, Pascal Schmidt <der.eremit@email.de>,
       linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: udev and devfs - The final word
Message-ID: <20040102003651.GT4176@parcelfarce.linux.theplanet.co.uk>
References: <3FF34522.8060106@tv.debian.net> <15B77182-3CB9-11D8-A498-000A95A0560C@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <15B77182-3CB9-11D8-A498-000A95A0560C@us.ibm.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1301
Lines: 28

On Thu, Jan 01, 2004 at 06:17:43PM -0600, Hollis Blanchard wrote:
> "console=" takes driver-supplied names which usually happen to match 
> /dev node names. For example, drivers/serial/8250.c names itself 
> "ttyS", so "console=ttyS0" will end up going to that driver, regardless 
> of the state of /dev.
> 
> I'm not saying that's good or bad, but what's the alternative? 
> "console=class/tty/ttyS0"?

Console code will need serious work anyway; note that current names
do _not_ refer to tty devices - there is some overlap, but right now
we have
	* console drivers
	* some of them being connected with tty drivers; those can tell
which tty driver corresponds to them
	* console ouput code maintaining chain of console drivers; output
is sent to them, attempt to open() /dev/console ends up picking the first
console driver that has corresponding tty one (== has console->device())
and opening the tty device in question
	* unholy mess with redirects.

There's no device nodes for console drivers.  So names in console=... are
something very odd, indeed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/