From: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Alain RICHARD <alain.richard@equation.fr>,
Benjamin Herrenschmidt <bh40@calva.net>,
Paul Mackerras <paulus@linuxcare.com>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: MacSerial and Serial driver cohabitation
Date: Mon, 17 Jul 2000 17:33:35 +0200 [thread overview]
Message-ID: <3973274F.F305D3FD@biophys.uni-duesseldorf.de> (raw)
In-Reply-To: Pine.LNX.4.10.10007171426170.449-100000@cassiopeia.home
Geert Uytterhoeven wrote:
> And CHRP boxes, which may have both 16550 and 8530 serial ports on the
> motherboard. Never tried my 8530 ports, though.
>
> To me it would sound logical to start counting serial ports from ttyS0 in one
> driver, and continue counting in a second driver, and so on. We had that on
> m68k, but the PC guys didn't like it and want to keep the current scheme (one
> major device for 16550 serial, and one for each type of multiserial board on
> the market).
I think the fight was rather about other design decisions in the m68k
driver, not as much about the device numbering. As far as I recall, the
proposed solution was to have the 'builtin' serials at least on m68k use
the default (16550) major but cut out the midlevel abstraction. I never
understood what was supposed to perform hardware abstraction though.
I'd say agree on a fixed order of probing, allocate minors in that order
(with the possible exception of allowing a driver to allocate specific
minors out of order if someone wants to make sure their driver always
gets the same minors).
Michael
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-17 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.10.10007150057110.4812-100000@unix1.wm.edu>
[not found] ` <20000715082955.6590@192.168.1.10>
2000-07-17 9:22 ` MacSerial and Serial driver cohabitation Alain RICHARD
2000-07-17 9:46 ` Andreas Tobler
2000-07-17 10:21 ` Benjamin Herrenschmidt
2000-07-17 12:32 ` Geert Uytterhoeven
2000-07-17 15:33 ` Michael Schmitz [this message]
2000-07-25 21:56 ` Michel Lanners
2000-07-28 8:37 ` Benjamin Herrenschmidt
2000-07-28 10:39 ` Michael Schmitz
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=3973274F.F305D3FD@biophys.uni-duesseldorf.de \
--to=schmitz@opal.biophys.uni-duesseldorf.de \
--cc=alain.richard@equation.fr \
--cc=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.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).