From: Benjamin Herrenschmidt <bh40@calva.net>
To: <mlan@cpu.lu>
Cc: <schmitz@opal.biophys.uni-duesseldorf.de>, <geert@linux-m68k.org>,
<linuxppc-dev@lists.linuxppc.org>, <paulus@linuxcare.com>
Subject: Re: MacSerial and Serial driver cohabitation
Date: Fri, 28 Jul 2000 10:37:43 +0200 [thread overview]
Message-ID: <20000728083743.21545@mailhost.mipsys.com> (raw)
In-Reply-To: <200007252156.XAA00879@piglet.grunz.lu>
>Hi all,
>
>On 17 Jul, this message from Michael Schmitz echoed through cyberspace:
>> 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).
>
>Whoever fixes this problem should be decorated, and a statue put up in
>his memory. ;-)
>
>But if anyone is brave enough to attempt it, don't forget that there are
>_two_ places where serial ports are probed for: serial console init very
>early in the booting, and driver init much later in the boot process.
>Those two should be guaranteed to be in sync re minor assignment/device
>naming. Right now, that's not the case.
My current rsync tree contains a fix done by Andreas Tobler that helps
cohabitation of macserial and legacy serial. I know Paul and Theodore
have been working on a more definitive fix, I don't know it's status however,
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-28 8:37 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
2000-07-25 21:56 ` Michel Lanners
2000-07-28 8:37 ` Benjamin Herrenschmidt [this message]
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=20000728083743.21545@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=paulus@linuxcare.com \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).