From: "H. Peter Anvin" <hpa@zytor.com>
To: Timur Tabi <timur@freescale.com>
Cc: Dan Malek <dan@embeddedalley.com>,
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 10:00:19 -0800 [thread overview]
Message-ID: <45E5C333.2060100@zytor.com> (raw)
In-Reply-To: <45E5C128.7020204@freescale.com>
Timur Tabi wrote:
> Dan Malek wrote:
>
>> I'd shoot that down, too. Using udev in an
>> embedded, reliable environment is very
>> troublesome. Although, products I've
>> developed using more than 4 UARTs had
>> some custom /dev work done to it just
>> to get everything mapped. My only
>> concern is we don't add a new range for
>> QE UARTs, that we use the same minors
>> for both CPM and QE.
>
> Then it appears that the only possible solution is to assign numbers 46
> - 53 to the CPM/QE and accept that it overlaps with the Altix. Is
> everyone okay with that?
>
I would much rather see these devices moved to a different minor range.
-hpa
next prev parent reply other threads:[~2007-02-28 18:00 UTC|newest]
Thread overview: 42+ 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 15:46 ` 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 [this message]
[not found] ` <ED6BD6F0-827F-4ADC-9D66-F9C3DD7FC470@embeddedalley.com>
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
2007-02-28 12:07 ` Mathiasen, Torben
2007-02-28 13:00 ` H. Peter Anvin
2007-02-28 13:14 ` Mathiasen, Torben
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=45E5C333.2060100@zytor.com \
--to=hpa@zytor.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 \
--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