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: <45E6F78A.7070603@freescale.com>
Date:	Thu, 01 Mar 2007 09:55:54 -0600
From:	Timur Tabi <timur@...escale.com>
To:	Dan Malek <dan@...eddedalley.com>, Torben.Mathiasen@...com
CC:	Segher Boessenkool <segher@...nel.crashing.org>,
	Kumar Gala <galak@...nel.crashing.org>,
	linux-ppc-embedded <linuxppc-embedded@...abs.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices

Dan Malek wrote:

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

Ok guys, I need a consensus here.  Are we going to allocate a second block of 4 minor 
numbers for the QE/CPM UART or not?

My driver already has a macro that limits the number of UARTS to 4, and it just uses minor 
numbers 47 through (47 + UCC_MAX_UART - 1).  So my driver can easily be modified to spill 
into the Altic's range if some custom board needs it.

I'll add a second TTY struct to handle the 2nd set of minor numbers if and only if 
devices-2.6+.txt is updated with that information.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale
-
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/