linux-kernel - Re: lanana: Add major/minor entries for PPC QE UART devices

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: <BE8D549F-71E4-43DE-B624-A8E4A50D094D@embeddedalley.com>
Date:	Thu, 1 Mar 2007 10:48:45 -0500
From:	Dan Malek <dan@...eddedalley.com>
To:	Segher Boessenkool <segher@...nel.crashing.org>
Cc:	Kumar Gala <galak@...nel.crashing.org>,
	linux-ppc-embedded <linuxppc-embedded@...abs.org>,
	Timur Tabi <timur@...escale.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>, Torben.Mathiasen@...com
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices

On Feb 28, 2007, at 5:08 PM, Segher Boessenkool wrote:

> Since you say no one has ever used more than 4 UARTs,
> there are two options:

People have used more than 4, but we just
allocated the additional /dev entries to cover
them.  I know of only one time this has happened.
It's such a custom case that the other device
names didn't matter.

> - Cap the driver at 4 UARTs;

Let's do this, but design the code to
allow more by just changing a #define.

> Just randomly using some extra minors that aren't
> assigned to you isn't such a great idea.

Maybe for a desktop or generic server where
you don't know what's going to be configured,
but it's not unusual to do so with custom
embedded systems.  The small experimental
or user allocations often don't cover what
is needed, so we just grab some allocation
from a device that isn't ever going to be
used on the system.

Thanks.

	-- Dan

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