From: Timur Tabi <timur@freescale.com>
To: Dan Malek <dan@embeddedalley.com>, Torben.Mathiasen@hp.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
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: Thu, 01 Mar 2007 09:55:54 -0600 [thread overview]
Message-ID: <45E6F78A.7070603@freescale.com> (raw)
In-Reply-To: <BE8D549F-71E4-43DE-B624-A8E4A50D094D@embeddedalley.com>
Dan Malek wrote:
> People have used more than 4, but we just
> allocated the additional /dev entries to cover
> them. I know of only one time this has happened.
> It's such a custom case that the other device
> names didn't matter.
Ok guys, I need a consensus here. Are we going to allocate a second block of 4 minor
numbers for the QE/CPM UART or not?
My driver already has a macro that limits the number of UARTS to 4, and it just uses minor
numbers 47 through (47 + UCC_MAX_UART - 1). So my driver can easily be modified to spill
into the Altic's range if some custom board needs it.
I'll add a second TTY struct to handle the 2nd set of minor numbers if and only if
devices-2.6+.txt is updated with that information.
--
Timur Tabi
Linux Kernel Developer @ Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Dan Malek <dan@embeddedalley.com>, Torben.Mathiasen@hp.com
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Kumar Gala <galak@kernel.crashing.org>,
linux-ppc-embedded <linuxppc-embedded@ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: lanana: Add major/minor entries for PPC QE UART devices
Date: Thu, 01 Mar 2007 09:55:54 -0600 [thread overview]
Message-ID: <45E6F78A.7070603@freescale.com> (raw)
In-Reply-To: <BE8D549F-71E4-43DE-B624-A8E4A50D094D@embeddedalley.com>
Dan Malek wrote:
> People have used more than 4, but we just
> allocated the additional /dev entries to cover
> them. I know of only one time this has happened.
> It's such a custom case that the other device
> names didn't matter.
Ok guys, I need a consensus here. Are we going to allocate a second block of 4 minor
numbers for the QE/CPM UART or not?
My driver already has a macro that limits the number of UARTS to 4, and it just uses minor
numbers 47 through (47 + UCC_MAX_UART - 1). So my driver can easily be modified to spill
into the Altic's range if some custom board needs it.
I'll add a second TTY struct to handle the 2nd set of minor numbers if and only if
devices-2.6+.txt is updated with that information.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-03-01 15:56 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 [this message]
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=45E6F78A.7070603@freescale.com \
--to=timur@freescale.com \
--cc=Torben.Mathiasen@hp.com \
--cc=dan@embeddedalley.com \
--cc=hpa@zytor.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.