linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: Torben.Mathiasen@hp.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.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 15:54:37 +0100	[thread overview]
Message-ID: <511cacb7bbe8a65ff72738c84ec9ece4@kernel.crashing.org> (raw)
In-Reply-To: <45E592DC.9060700@freescale.com>

>>>           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'll try to get an answer from someone, but I'm no CPM expert.

Adding linuxppc-embedded to the CC:, someone there surely knows.


Segher

       reply	other threads:[~2007-02-28 14:54 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     ` Segher Boessenkool [this message]
2007-02-28 15:46       ` lanana: Add major/minor entries for PPC QE UART devices Dan Malek
2007-02-28 17:04         ` Timur Tabi
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=511cacb7bbe8a65ff72738c84ec9ece4@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Torben.Mathiasen@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.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 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).