From: Matt_Domsch@Dell.com
To: greg@kroah.com
Cc: mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: RE: devicefs requests
Date: Wed, 25 Sep 2002 17:03:09 -0500 [thread overview]
Message-ID: <20BF5713E14D5B48AA289F72BD372D68C1E8C0@AUSXMPC122.aus.amer.dell.com> (raw)
> But what do you do with the usb_bus_type? Why would your code use
> anything that is private to the driver core?
Fair enough. I actually only need the 64-bit unique ID that the USB device
provides, and its parent PCI device. EDD provides this info as x86 BIOS
sees it, so my code compares the two, and will make a symlink between the
two. This lets the OS know which device BIOS thinks it is (i.e. to know
what disk you're booting from).
True, I don't (today) see a unique ID in struct usb_device. Hopefully
that's something that can be added in the future. Functions which expose
this info separate from exporting the bus type would be great.
SCSI has a different set of things that EDD needs exported (channel, id,
lun). IDE still different (channel, number (master/slave)), plus parent PCI
device.
> Oh yeah, it's "driverfs" not "devicefs" :)
Yes, my bad.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer, Architect
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next reply other threads:[~2002-09-25 21:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 22:03 Matt_Domsch [this message]
2002-09-25 22:46 ` devicefs requests Greg KH
2002-10-01 1:39 ` Patrick Mochel
-- strict thread matches above, loose matches on Subject: below --
2002-09-26 16:13 Matt_Domsch
2002-09-27 4:41 ` Greg KH
2002-09-26 3:48 Matt_Domsch
2002-09-26 4:14 ` Greg KH
2002-09-26 14:41 ` Randy.Dunlap
2002-09-25 22:11 Matt_Domsch
2002-09-25 19:28 Matt_Domsch
2002-09-25 21:33 ` Greg KH
2002-09-25 21:33 ` Greg KH
2002-10-01 1:32 ` 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=20BF5713E14D5B48AA289F72BD372D68C1E8C0@AUSXMPC122.aus.amer.dell.com \
--to=matt_domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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;
as well as URLs for NNTP newsgroup(s).