From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: driverfs support for motherboard devices
Date: Tue, 05 Feb 2002 13:36:13 -0500 [thread overview]
Message-ID: <3C60261D.2CECD6F4@mandrakesoft.com> (raw)
In-Reply-To: <20020205173912.GA165@elf.ucw.cz>
Pavel Machek wrote:
>
> Hi!
>
> This patch adds support for motherboard devices, so that you can see
> them in driverfs.
>
> Should ide be presented to driverfs as bus with two devices on it?
This is a tough one... Since there is a typically a single PCI device
for IDE, a PCI or HOST bridge should register an IDE device. The IDE
device would in turn register two IDE controllers, which would in turn
register up to two disks.
> What about "legacy" bus? It is not in this release, and I'm not 100%
> sure who should generate it. Many architectures will need such bus so
> maybe it belongs in drivers/base in order to avoid duplicate code?
I think one should have a conceptual "system bus" as a virtual parent,
when none is present. For example my old 486 has PCI, but the only PCI
device is IDE. There are the standard legacy devices like parallel and
serial, but they do not show up under an ISA bridge device. This 486
system would be a candidate for this system bus.
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-02-05 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 17:39 driverfs support for motherboard devices Pavel Machek
2002-02-05 18:11 ` Xavier Bestel
2002-02-06 7:28 ` Zwane Mwaikambo
2002-02-05 18:36 ` Jeff Garzik [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=3C60261D.2CECD6F4@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@suse.cz \
/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