From: Timur Tabi <timur@freescale.com>
To: Dan Malek <dan@embeddedalley.com>
Cc: Torben.Mathiasen@hp.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices
Date: Wed, 28 Feb 2007 11:04:04 -0600 [thread overview]
Message-ID: <45E5B604.904@freescale.com> (raw)
In-Reply-To: <BD465924-7387-47EF-B90F-606F215819C2@embeddedalley.com>
Dan Malek wrote:
> 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.
Minor nit: On the QE, they'll be called ttyQE0 through ttyQE7.
I agree that the CPM and the QE should share the same starting minor number, so that
ttyCPM0 has the same major/minor number as ttyQE0, since it's not possible to have a CPM
and a QE on the same device. However, ttyCPM0 is currently assigned to 46, and device 50
is an Altix serial card. The only way to give the CPM 6 or 8 slots without moving it is
to overlap the Altix card.
Now I don't know anything about the Altix card, so I don't know if it's possible to use
that card on a system with a CPM or a QE. If it isn't, then I don't know if overlapping
minor numbers is still a problem.
(Note that the Altix card has a range of 50-81, which is pretty big.)
If we move CPM/QE to 192, then I can change the CPM device driver to reflect that, but I
don't know what that means for older kernels.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-28 17:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45E46976.6060600@freescale.com>
[not found] ` <29c13109971547687159078eacdea008@kernel.crashing.org>
[not found] ` <45E592DC.9060700@freescale.com>
2007-02-28 14:54 ` lanana: Add major/minor entries for PPC QE UART devices Segher Boessenkool
2007-02-28 15:46 ` Dan Malek
2007-02-28 17:04 ` Timur Tabi [this message]
2007-02-28 17:27 ` Dan Malek
2007-02-28 17:35 ` Timur Tabi
2007-02-28 17:46 ` Dan Malek
2007-02-28 17:51 ` Timur Tabi
2007-02-28 18:00 ` H. Peter Anvin
2007-02-28 18:20 ` Dan Malek
2007-02-28 19:18 ` Kumar Gala
2007-02-28 19:21 ` H. Peter Anvin
2007-02-28 19:30 ` Timur Tabi
2007-02-28 19:33 ` Kumar Gala
2007-02-28 19:43 ` Timur Tabi
2007-02-28 20:57 ` Dan Malek
2007-02-28 22:08 ` Segher Boessenkool
2007-03-01 15:48 ` Dan Malek
2007-03-01 15:55 ` Timur Tabi
2007-03-01 16:06 ` Dan Malek
2007-03-01 16:13 ` Timur Tabi
2007-03-01 16:43 ` Segher Boessenkool
2007-03-01 13:38 ` Mathiasen, Torben
2007-02-28 19:21 ` Timur Tabi
2007-02-28 19:25 ` Segher Boessenkool
2007-02-28 19:27 ` H. Peter Anvin
2007-02-28 19:45 ` Segher Boessenkool
2007-02-28 22:40 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E5B604.904@freescale.com \
--to=timur@freescale.com \
--cc=Torben.Mathiasen@hp.com \
--cc=dan@embeddedalley.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).