From: Jeff Randall <randall@bif.digi.com>
To: rmk@arm.linux.org.uk (Russell King)
Cc: hpa@transmeta.com (H. Peter Anvin),
alan@lxorguk.ukuu.org.uk (Alan Cox),
torvalds@transmeta.com (Linus Torvalds),
Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
tytso@MIT.EDU
Subject: Re: Larger dev_t
Date: Wed, 28 Mar 2001 10:59:09 -0600 (CST) [thread overview]
Message-ID: <200103281659.KAA29060@bif.digi.com> (raw)
In-Reply-To: <20010327234308.B5411@flint.arm.linux.org.uk> from "Russell King" at Mar 27, 2001 11:43:08 PM
Russell King wrote:
> I for one would like to see a major number for all 'serial ports' whether
> they be embedded ARM serial ports _or_ standard 16550 ports, but at the
> moment its not easily acheivable without introducing more mess.
>
> Ted indicated to me a while ago (just after I wrote serial_core.c for
> yet-another-type-of-ARM-serial-port) his visions of the direction serial
> stuff should take in 2.5; this is obviously one of the things that I'm
> keen to discuss and solve in 2.5.
A change to a 12:20 major:minor dev_t would be a great help for the various
serial drivers that I write and help maintain. We currently as a company
maintain 4 different serial device drivers for linux and all of them
currently use between 4 and 10 majors in order to have enough raw minors
available to identify the maximum port count supported. We had to do the
same think on SunOS (which also has 8:8) in order to support reasonable port
counts there. I'd absoultely love the ability to get back on a single major
per driver.
I'd like to see all of the serial drivers shipped in the kernel tree be
configured by default to use the same major.. but I wouldn't want to have
external drivers forced onto that major as well.
--
Jeff Randall - Jeff_Randall@digi.com "A paranoid person is never alone,
he knows he's always the center
of attention..."
next prev parent reply other threads:[~2001-03-28 17:01 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 9:29 Larger dev_t Andries.Brouwer
2001-03-27 18:48 ` Linus Torvalds
2001-03-27 19:28 ` H. Peter Anvin
2001-03-27 19:51 ` Linus Torvalds
2001-03-27 21:21 ` Alan Cox
2001-03-27 21:35 ` Linus Torvalds
2001-03-27 22:02 ` Andre Hedrick
2001-03-27 23:57 ` Linus Torvalds
2001-03-28 21:23 ` Martin Dalecki
2001-03-28 21:40 ` H. Peter Anvin
2001-03-28 21:44 ` Andre Hedrick
2001-03-27 22:16 ` Alan Cox
2001-03-27 22:16 ` H. Peter Anvin
2001-03-27 22:43 ` Russell King
2001-03-28 16:59 ` Jeff Randall [this message]
2001-03-28 0:07 ` Linus Torvalds
2001-03-28 0:10 ` H. Peter Anvin
2001-03-28 0:24 ` Linus Torvalds
2001-03-28 2:19 ` Alan Cox
2001-03-28 7:08 ` Andre Hedrick
2001-03-28 21:32 ` Martin Dalecki
2001-03-29 3:53 ` Alan Cox
2001-03-29 11:02 ` Martin Dalecki
2001-04-02 20:02 ` Alan Cox
2001-04-03 7:25 ` Martin Dalecki
2001-04-03 12:19 ` Alan Cox
2001-04-03 12:13 ` Martin Dalecki
2001-04-03 12:38 ` Alan Cox
2001-04-04 8:08 ` Rogier Wolff
2001-03-30 6:54 ` Kai Henningsen
2001-03-28 21:18 ` Martin Dalecki
2001-03-27 22:13 ` H. Peter Anvin
2001-03-27 22:55 ` Dan Hollis
2001-03-27 22:58 ` H. Peter Anvin
2001-03-27 23:42 ` Richard Gooch
2001-03-28 1:03 ` Paul Jakma
2001-03-28 1:35 ` Alexander Viro
2001-03-27 23:44 ` Andrew Pimlott
2001-03-28 0:28 ` Albert D. Cahalan
2001-03-28 3:58 ` Johan Kullstam
2001-03-28 4:23 ` Alexander Viro
2001-03-28 11:57 ` Jesse Pollard
2001-03-28 18:13 ` Oliver Neukum
2001-03-28 19:05 ` Jesse Pollard
2001-03-28 19:50 ` Oliver Neukum
2001-03-28 21:36 ` Martin Dalecki
2001-03-28 21:09 ` Martin Dalecki
2001-03-28 21:24 ` H. Peter Anvin
2001-03-28 21:46 ` Alexander Viro
2001-03-28 20:54 ` Martin Dalecki
2001-03-28 11:52 ` Pjotr Kourzanoff
2001-03-28 12:11 ` Tim Jansen
2001-03-27 19:27 ` Albert D. Cahalan
-- strict thread matches above, loose matches on Subject: below --
2001-04-03 14:48 Wayne.Brown
2001-04-03 15:34 ` Bart Trojanowski
2001-04-02 21:59 Andries.Brouwer
2001-04-02 20:17 Andries.Brouwer
2001-04-02 21:45 ` Alan Cox
2001-04-03 7:28 ` Martin Dalecki
2001-04-03 10:09 ` Ingo Oeser
2001-04-03 12:06 ` Alan Cox
2001-04-03 12:20 ` Ingo Oeser
2001-04-03 12:15 ` Martin Dalecki
2001-04-03 12:53 ` Alan Cox
2001-04-03 16:05 ` Richard Gooch
2001-04-03 16:34 ` Alexander Viro
2001-04-03 16:58 ` Richard Gooch
2001-04-03 16:54 ` Alan Cox
2001-04-03 17:02 ` Richard Gooch
2001-04-03 12:41 ` Alan Cox
2001-04-03 23:28 ` Tim Wright
2001-03-27 22:38 Jesse Pollard
2001-03-27 22:44 ` H. Peter Anvin
2001-03-26 21:18 John Byrne
2001-03-26 22:12 ` Linus Torvalds
2001-03-26 23:41 ` Guest section DW
2001-03-25 12:31 Andries.Brouwer
2001-03-25 15:35 ` Wichert Akkerman
2001-03-25 16:15 ` Mitchell Blank Jr
2001-03-25 16:54 ` Michel Wilson
2001-03-25 17:12 ` Jeff Garzik
2001-03-25 17:00 ` Jamie Lokier
2001-03-25 17:07 ` Anton Altaparmakov
2001-03-25 17:37 ` Michel Wilson
2001-03-25 18:21 ` Guest section DW
2001-03-25 20:50 ` diego
2001-03-25 17:55 ` Gerry
2001-03-27 6:03 ` Linus Torvalds
2001-03-24 16:13 Andries.Brouwer
2001-03-24 14:25 Andries.Brouwer
2001-03-24 14:40 ` Jeff Garzik
2001-03-24 15:00 ` Alexander Viro
2001-03-25 14:22 ` Martin Dalecki
2001-03-25 3:24 ` Linus Torvalds
2001-03-25 14:35 ` Martin Dalecki
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=200103281659.KAA29060@bif.digi.com \
--to=randall@bif.digi.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=Jeff_Randall@digi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.com \
--cc=tytso@MIT.EDU \
/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