From: Pavel Machek <pavel@suse.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Andre Hedrick <andre@linuxdiskcert.org>,
Russell King <rmk@arm.linux.org.uk>, Pavel Machek <pavel@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: driverfs support for motherboard devices
Date: Wed, 6 Feb 2002 13:22:55 +0100 [thread overview]
Message-ID: <20020206122253.GB446@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10202051445400.6350-100000@master.linux-ide.org> <Pine.LNX.4.33.0202051500510.25114-100000@segfault.osdlab.org>
In-Reply-To: <Pine.LNX.4.33.0202051500510.25114-100000@segfault.osdlab.org>
Hi!
> > > On Tue, Feb 05, 2002 at 10:43:14AM -0800, Patrick Mochel wrote:
> > > > I think that ide should get its own bus, as a child of the ide controller.
> > > > I haven't looked at ide yet at all. But, on most modern systems, the ide
> > > > controller is a function of the southbridge, so ide devices should go
> > > > under that. Like what the usb stuff does now...
> > >
> > > What about, say, a Promise PCI IDE card? You really need to reference
> > > the parent PCI device when the is one.
> >
> > LOL, how about ones that are quad-channel with a DEC-Bridge to slip the
> > local BUSS?
>
> LOL? I don't understand...
>
> I don't see how any of those cases are necessarily hard to visualize.
>
> Case 1: Typical PC with IDE as function of southbridge.
>
> pci0
> |
> -- 07.2 (IDE controller)
> |
> --- disk0
> |
> --- disk1
>
> Case 2: Promise IDE Controller with 2 channels
>
>
> pci0
> |
> --- 03.0 (Promise IDE Controller)
> |
> --- channel0
> |
> ---- disk0
> |
> ---- disk1
>
These are easy ones, but what about
Case 4: 386 with no PCI
and what's worse
Case 5: 486 with both PCI and VLB, where ide is on the VLB?
cases 4 and 5 are IMO hard, because it is difficult to know where it
really is... and I'm not sure current kernel knows it.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
next prev parent reply other threads:[~2002-02-06 22:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 17:39 Pavel Machek
2002-02-05 18:11 ` Xavier Bestel
2002-02-06 7:28 ` Zwane Mwaikambo
2002-02-05 18:36 ` Jeff Garzik
2002-02-05 18:43 ` Patrick Mochel
2002-02-05 20:47 ` Russell King
2002-02-05 22:46 ` Andre Hedrick
2002-02-05 23:06 ` Joel Jaeggli
2002-02-05 23:30 ` Alan Cox
2002-02-05 23:25 ` Patrick Mochel
2002-02-05 23:08 ` Patrick Mochel
2002-02-05 23:17 ` Joel Jaeggli
2002-02-06 12:22 ` Pavel Machek [this message]
2002-02-06 23:34 ` Patrick Mochel
2002-02-07 13:03 ` Pavel Machek
2002-02-07 0:38 ` Alan Cox
2002-02-07 12:31 ` Pavel Machek
2002-02-07 13:23 ` Dave Jones
2002-02-07 17:26 ` Patrick Mochel
2002-02-07 17:28 ` Dave Jones
2002-02-07 18:32 ` Gunther Mayer
2002-02-07 23:03 ` Pavel Machek
2002-02-06 7:33 ` Zwane Mwaikambo
2002-02-06 7:24 ` Zwane Mwaikambo
2002-02-06 12:16 ` Pavel Machek
2002-02-06 20:54 ` Patrick Mochel
2002-02-07 20:21 ` Pavel Machek
2002-02-07 18:18 Thomas Hood
2002-02-07 18:28 ` Patrick Mochel
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=20020206122253.GB446@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andre@linuxdiskcert.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=rmk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®