linux-kernel - Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070403.182125.77058566.davem@davemloft.net>
Date:	Tue, 03 Apr 2007 18:21:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	alan@...rguk.ukuu.org.uk
Cc:	paulus@...ba.org, dwmw2@...radead.org, linuxppc-dev@...abs.org,
	benh@...nel.crashing.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers.

From: Alan Cox <alan@...rguk.ukuu.org.uk>
Date: Wed, 4 Apr 2007 02:19:24 +0100

> > I totally agree with Paul, the onboard serial device should get
> > ttyS0 regardless of what hardare is used to drive it.
> 
> Thats between you and udev.

That might be true when udev exists, but it doesn't for the console
specification on the kernel command line.

I don't care about ordering, but the name matters just like "eth%d"
is the default name for all ethernet devices.

Using different majors for different instances of the exact same kind
of device is really not smart.  It's a serial port, and if you try
to dress it up to be something else you run into all kinds of problems.

Not the least of which is the user has to scratch his head figuring
out what kind of chip drives his serial console, he just wants the
first serial port and he should have a way to say just that even
on the kernel command line.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/