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:35:39 -0600 [thread overview]
Message-ID: <45E5BD6B.1010509@freescale.com> (raw)
In-Reply-To: <46F6BF70-2922-4E05-8DAB-6B0830B0AB47@embeddedalley.com>
Dan Malek wrote:
> I don't think that would be a problem, and I'd like the
> CPM/QE to share devices because it makes the
> software distributions common to all Freescale
> embedded processors.
I'm willing to use whatever minor number and range the community agrees upon.
An alternative idea, which one person already shot down, was to allow only 4 devices
normally, but allow more devices if you use udev, since udev doesn't care about minor
number assignments. This eliminates the overlap and encourages people to use udev.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-02-28 17:36 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 [this message]
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
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=45E5BD6B.1010509@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 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.