From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: benh@kernel.crashing.org, eger@havoc.gtf.org,
rmk+serial@arm.linux.org.uk
Subject: Re: [PATCH] pmac_zilog: insert correct failure path for device numbers being taken
Date: 16 Jul 2004 21:05:45 -0400 [thread overview]
Message-ID: <1090026344.1232.412.camel@cube> (raw)
> I'll talk to him at KS/OLS and see if we can come up with
> some solution, this is actually a regression since 2.4
> could "offset" macserial, so we could accomodate, for
> example, a driver for a pcmcia modem _and_ the zilog ports.
That's the wrong way around. The zilog ports are always
there, and thus could have stable numbers. The PCMCIA
ports can not have stable numbers; they might be gone even.
In general, the platform-specific (motherboard, generally)
ports should get to grab device numbers first. Anthing
connected by a normally hot-plug bus goes last. Plain PCI
is in the middle, because PCI cards are occasionally moved.
For a PC, serial ports hanging off the motherboard's LPC bus
(what amounts to built-in ISA) should go before serial ports
that might be on normal PCI cards, which in turn go before
those on PCMCIA.
next reply other threads:[~2004-07-17 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 1:05 Albert Cahalan [this message]
2004-07-17 17:33 ` [PATCH] pmac_zilog: insert correct failure path for device numbers being taken Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2004-07-12 7:51 pmac oops: devfs versus power management - fight! David Eger
2004-07-12 8:21 ` oops: pmac power management David Eger
2004-07-12 22:09 ` pmac_zilog: driver loads (and crashes) without hardware David Eger
2004-07-13 0:39 ` [PATCH] pmac_zilog: initialize port spinlock on all init paths David Eger
2004-07-13 4:16 ` Benjamin Herrenschmidt
2004-07-16 18:58 ` [PATCH] pmac_zilog: insert correct failure path for device numbers being taken David Eger
2004-07-16 19:01 ` Benjamin Herrenschmidt
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=1090026344.1232.412.camel@cube \
--to=albert@users.sf.net \
--cc=benh@kernel.crashing.org \
--cc=eger@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+serial@arm.linux.org.uk \
/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.