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: <A6EED9FC-4CE4-4089-ACB8-A1C7A3C50FDD@embeddedalley.com>
Date:	Wed, 28 Feb 2007 15:57:48 -0500
From:	Dan Malek <dan@...eddedalley.com>
To:	Timur Tabi <timur@...escale.com>
Cc:	Kumar Gala <galak@...nel.crashing.org>,
	"H. Peter Anvin" <hpa@...or.com>, Torben.Mathiasen@...com,
	linux-ppc-embedded <linuxppc-embedded@...abs.org>,
	Segher Boessenkool <segher@...nel.crashing.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices


On Feb 28, 2007, at 2:43 PM, Timur Tabi wrote:

> What about major number 205?  It also has the screwed-up /dev/ 
> ttyCPM entries, but it has more room, and the CPM driver doesn't  
> actually use it.  At least, I can't see where it uses it.

Please, let's just leave the four we have and let
the driver just allocate increasing minor numbers.
If anyone has a product with more than 4 UARTs,
they will have to figure out what to do with the
additional minors.

We are making a very complicated problem
out of nothing.  This hasn't caused any problems
in the past, and changing the existing names and
minors will cause problems for everyone today.

Just leave it alone, fix up the documentation,
and have the driver print some warning if it
allocates more than 4 UARTs.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ