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: <BD465924-7387-47EF-B90F-606F215819C2@embeddedalley.com>
Date:	Wed, 28 Feb 2007 10:46:53 -0500
From:	Dan Malek <dan@...eddedalley.com>
To:	Segher Boessenkool <segher@...nel.crashing.org>
Cc:	Timur Tabi <timur@...escale.com>, Torben.Mathiasen@...com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ppc-embedded <linuxppc-embedded@...abs.org>
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices


On Feb 28, 2007, at 9:54 AM, Segher Boessenkool wrote:

>>>>           46 = /dev/ttyCPM0        PPC CPM (SCC or SMC) - port 0
>>>>              ...
>>>> -         47 = /dev/ttyCPM5        PPC CPM (SCC or SMC) - port 5
>>>> +         49 = /dev/ttyCPM5        PPC CPM (SCC or SMC) - port 5
>>> If CPM0 is 46, then CPM5 is not 47, but not 49 either.
>>> Unless it's not CPM5 but CPM3?
>>
>> Honestly, I don't know.  I was just correcting the obvious typo (47
>> instead of 49).
>
> It's obvious it shouldn't be 47, but it's not obvious it
> should be 49 instead.

I don't know the origin of this thread, but none of
that looks correct.  Today, there can be up to 8
CPM UART devices, 6 on CPM/CPM2 and 8
on the QE.  If ttyCPM0 starts at minor 46, they
should be at least monotonically incrementing
up to ttyCPM7 with minor 53.


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/