From: "Mathiasen, Torben" <Torben.Mathiasen@hp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Timur Tabi" <timur@freescale.com>, <linux-kernel@vger.kernel.org>
Subject: RE: lanana: Add major/minor entries for PPC QE UART devices
Date: Wed, 28 Feb 2007 14:14:41 +0100 [thread overview]
Message-ID: <93C4769E3BED6B42B7203BD6F065654C08C5D7FF@dmoexc01.emea.cpqcorp.net> (raw)
In-Reply-To: <45E57CE5.5010003@zytor.com>
> Mathiasen, Torben wrote:
> >
> > Got around looking at this one. I'm fine with this approach, but the
> > CPM5 fix looks wrong. Shouldn't it be:
> >
> > 49 = /dev/ttyCPM3 PPC CPM (SCC or SMC) - port 3
> >
> > instead?
> >
>
> Well, how many CPM devices can exist? If there are really 6 ports
> possible, they need minors up to 51.
>
> Also, if QE really is just CPM v3, and they share the same minors, why
> change the name?
>
Assuming QE has 4 entries, I would expect CPM to be the same. But we
need verification of that. If it needs 6, we are in more trouble.
Torben
next prev parent reply other threads:[~2007-02-28 13:17 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 17:25 lanana: Add major/minor entries for PPC QE UART devices Timur Tabi
2007-02-27 17:36 ` Randy Dunlap
2007-02-28 1:45 ` Segher Boessenkool
2007-02-28 14:34 ` Timur Tabi
2007-02-28 14:54 ` Segher Boessenkool
2007-02-28 14:54 ` Segher Boessenkool
2007-02-28 15:46 ` Dan Malek
2007-02-28 15:46 ` Dan Malek
2007-02-28 17:04 ` Timur Tabi
2007-02-28 17:04 ` Timur Tabi
2007-02-28 17:27 ` Dan Malek
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:00 ` H. Peter Anvin
2007-02-28 18:20 ` Dan Malek
2007-02-28 19:18 ` Kumar Gala
2007-02-28 19:18 ` Kumar Gala
2007-02-28 19:21 ` H. Peter Anvin
2007-02-28 19:21 ` H. Peter Anvin
2007-02-28 19:30 ` Timur Tabi
2007-02-28 19:30 ` Timur Tabi
2007-02-28 19:33 ` Kumar Gala
2007-02-28 19:33 ` Kumar Gala
2007-02-28 19:43 ` Timur Tabi
2007-02-28 19:43 ` Timur Tabi
2007-02-28 20:57 ` Dan Malek
2007-02-28 20:57 ` Dan Malek
2007-02-28 22:08 ` Segher Boessenkool
2007-02-28 22:08 ` Segher Boessenkool
2007-03-01 15:48 ` Dan Malek
2007-03-01 15:48 ` Dan Malek
2007-03-01 15:55 ` Timur Tabi
2007-03-01 15:55 ` Timur Tabi
2007-03-01 16:06 ` Dan Malek
2007-03-01 16:06 ` Dan Malek
2007-03-01 16:13 ` Timur Tabi
2007-03-01 16:13 ` Timur Tabi
2007-03-01 16:43 ` Segher Boessenkool
2007-03-01 16:43 ` Segher Boessenkool
2007-03-01 13:38 ` Mathiasen, Torben
2007-03-01 13:38 ` Mathiasen, Torben
2007-02-28 19:21 ` Timur Tabi
2007-02-28 19:21 ` Timur Tabi
2007-02-28 19:25 ` Segher Boessenkool
2007-02-28 19:25 ` Segher Boessenkool
2007-02-28 19:27 ` H. Peter Anvin
2007-02-28 19:27 ` H. Peter Anvin
2007-02-28 19:45 ` Segher Boessenkool
2007-02-28 19:45 ` Segher Boessenkool
2007-02-28 22:40 ` Jan Engelhardt
2007-02-28 22:40 ` Jan Engelhardt
2007-02-28 12:07 ` Mathiasen, Torben
2007-02-28 13:00 ` H. Peter Anvin
2007-02-28 13:14 ` Mathiasen, Torben [this message]
2007-02-28 14:32 ` Kumar Gala
2007-02-28 14:37 ` Timur Tabi
2007-02-28 14:51 ` Mathiasen, Torben
2007-02-28 14:54 ` Kumar Gala
2007-02-28 15:13 ` H. Peter Anvin
2007-02-28 16:29 ` Timur Tabi
2007-02-28 16:33 ` H. Peter Anvin
2007-02-28 16:20 ` Timur Tabi
2007-02-28 14:35 ` Timur Tabi
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=93C4769E3BED6B42B7203BD6F065654C08C5D7FF@dmoexc01.emea.cpqcorp.net \
--to=torben.mathiasen@hp.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timur@freescale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.