On Wed, 2 Apr 2003, David Brownell wrote: > >>Sounds right. Perhaps also listing any device quirks. > > > > > > 5. There's a handful of flags that could be listed. That > > information should really be made available through the /proc/scsi/usb > > interface. Maybe you feel that the entire /proc/scsi/usb thing should be > > moved to sysfs anyhow. > > Maybe, but it wasn't providing this kind of info last time I looked. > Just some info about the devices, not about driver state.
Sure it was. That is, /proc/scsi/usb does provide that _kind_ of info (since device quirks falls into the category of info about the device, not about driver state); it just doesn't provide the actual pieces you want. If Matt doesn't object, I'll add the quirks listing over here instead of using sysfs. > I for the pragmatic approach, where reading the contents of the > debug file is just a "spinlock, sprintf everything, unlock". > One "Big" (1KB?) file is easiest to use when debugging, since > only that approach provides a consistent snapshot. Not all the information I listed before is protected by the spinlock in question. In fact, some of it isn't protected by a spinlock at all. But that's probably all right -- I think things will end up being sufficiently consistent anyway. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
