From: Adam <ambx1@netscape.net>
To: linux-kernel@vger.kernel.org
Subject: driverfs question
Date: Thu, 21 Feb 2002 15:37:30 -0500 [thread overview]
Message-ID: <3C755A8A.90000@netscape.net> (raw)
How will the devices in the driverfs be arranged?
It seems to me that it could only be one of the following three methods.
Method 1:
All devices will be arranged according to type. There will be a folder
for video, sound, joysticks, etc.
Pros: - Easy to read and understand while browsing the driverfs.
Cons: - Similar interface already implemented in device fs.
- arrangement shows no hierarchy and doesn't involve the buses.
Method 2:
Folders are created for each bus then devices are placed within them.
If a bus has another bus for a parent, like a pci USB controller,
it doesn't matter. The bus still gets a root level folder.
Pros: - Useful and unique information to the user.
Cons: - Still doesn't truly represent devices by their actual connection
- Makes root level device detection APIs more difficult to write
Method 3:
Devices are arranged by their true connection. If a usb controller is a
member of a pci bus, it's folder will be within the pci folder. The
root level bus will either be PnP BIOS, APIC device tables, or, for
legacy computers, an emulation of some sort.
Pros: - Devices are arranged by their actual connection.
- PnP and APIC will finally be truly integrated into the kernel.
Cons: - Legacy emulation could be challenging.
I tend to prefer method 3. Not only does it provide a perfect interface
for user level daemons but also it shows the devices in their true
locations. This is very important. Perhaps all or some of these
methods should be compile time options.
Sincerely,
Adam
next reply other threads:[~2002-02-21 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 20:37 Adam [this message]
2002-02-21 20:48 ` driverfs question Patrick Mochel
2002-02-21 21:25 ` Richard B. Johnson
2002-02-21 21:56 ` Adam
2002-02-21 21:59 ` Richard B. Johnson
2002-03-12 21:17 ` H. Peter Anvin
2002-02-21 21:53 ` Greg KH
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=3C755A8A.90000@netscape.net \
--to=ambx1@netscape.net \
--cc=linux-kernel@vger.kernel.org \
/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