From: Patrick Mochel <firstname.lastname@example.org>
Cc: email@example.com, <firstname.lastname@example.org>
Subject: RE: devicefs requests
Date: Mon, 30 Sep 2002 18:39:33 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.email@example.com> (raw)
On Wed, 25 Sep 2002 Matt_Domsch@Dell.com wrote:
> > 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.
UUIDs are something that many people have asked for in struct device. I've
put it off because they're used in only a few places today, because it's
impossible to standardize them across different device types, and it's
difficult to extract one from devices that don't inherently support them.
It's a valid request though. What we've talked about is:
- making it struct device::char * uuid;
- the bus that discovers the device is responsible for allocating and
freeing the field.
- It must be a NULL-terminated ASCII string.
- It will be exported in the device's drivefs directory in a file 'uuid'.
next prev parent reply other threads:[~2002-10-01 1:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 22:03 devicefs requests Matt_Domsch
2002-09-25 22:46 ` Greg KH
2002-10-01 1:39 ` Patrick Mochel [this message]
-- 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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).