On Thu, Jul 28, 2005 at 03:05:25AM +0800, Dan Jacobson wrote:
> Well all I know is "tell upstream that 2.6 proc_usb_info.txt needs
> those blank lines if they aren't there already"... as I am unfamiliar
> with upstream.
I took a closer look at your patch, and to be honest, other than the
last three fragments that add a blank line between E:... and T:...
I can't see what it does, other than perhaps adding some extra whitepace,
that seems spurious.
I personally don't think the spaces between the E:... and T:... lines
are neccessary, its just the dump of a log, but I can see why you would
want them.
I have attached the latest version of this file from upstream to
this mail for reference. If you want to submit you change upstream,
please read this http://linux.yyz.us/patch-format.html Sorry its a bit
long winded, but its probably easier for me to just give you the link
than try and explain it. I'd send it to
linux-usb-devel@lists.sourceforge.net and CC Andrew Morton <[EMAIL PROTECTED]>
If you are not comfortable with this, please make a unified diff of
your change (diff -u), follow the instructions in step 5. "Sign your work",
and send it here, I will be happy to forward it on. However, I can't in
any way gaurantee success.
> H> If it is in 2.6.12 then it is already in unstable.
>
> Say, on sid all I see is 11 being the highest. Not that I can
> download any of them on my modem.
12 has recently been added.
ftp://ftp.debian.org/debian/pool/main/l/linux-2.6/
I agree that downloading that behemouth is a bit of an ask.
--
Horms
/proc/bus/usb filesystem output
===
(version 2003.05.30)
The usbfs filesystem for USB devices is traditionally mounted at
/proc/bus/usb. It provides the /proc/bus/usb/devices file, as well as
the /proc/bus/usb/BBB/DDD files.
**NOTE**: If /proc/bus/usb appears empty, and a host controller
driver has been linked, then you need to mount the
filesystem. Issue the command (as root):
mount -t usbfs none /proc/bus/usb
An alternative and more permanent method would be to add
none /proc/bus/usb usbfs defaults 0 0
to /etc/fstab. This will mount usbfs at each reboot.
You can then issue `cat /proc/bus/usb/devices` to extract
USB device information, and user mode drivers can use usbfs
to interact with USB devices.
There are a number of mount options supported by usbfs.
Consult the source code (linux/drivers/usb/core/inode.c) for
information about those options.
**NOTE**: The filesystem has been renamed from "usbdevfs" to
"usbfs", to reduce confusion with "devfs". You may
still see references to the older "usbdevfs" name.
For more information on mounting the usbfs file system, see the
"USB Device Filesystem" section of the USB Guide. The latest copy
of the USB Guide can be found at http://www.linux-usb.org/
THE /proc/bus/usb/BBB/DDD FILES:
Each connected USB device has one file. The BBB indicates the bus
number. The DDD indicates the device address on that bus. Both
of these numbers are assigned sequentially, and can be reused, so
you can't rely on them for stable access to devices. For example,
it's relatively common for devices to re-enumerate while they are
still connected (perhaps someone jostled their power supply, hub,
or USB cable), so a device might be 002/027 when you first connect
it and 002/048 sometime later.
These files can be read as binary data. The binary data consists
of first the device descriptor, then the descriptors for each
configuration of the device. That information is also shown in
text form by the /proc/bus/usb/devices file, described later.
These files may also be used to write user-level drivers for the USB
devices. You would open the /proc/bus/usb/BBB/DDD file read/write,
read its descriptors to make sure it's the device you expect, and then
bind to an interface (or perhaps several) using an ioctl call. You
would issue more ioctls to the device to communicate to it using
control, bulk, or other kinds of USB transfers. The IOCTLs are
listed in the file, and at this writing the
source code (linux/drivers/usb/devio.c) is the primary reference
for how to access devices through those files.
Note that since by default these BBB/DDD files are writable only by
root, only root can write such user mode drivers. You can selectively
grant read/write permissions to other users by using "chmod". Also,
usbfs mount options such as "devmode=0666" may be helpful.
THE /proc/bus/usb/devices FILE:
---
In /proc/bus/usb/devices, each device's output has multiple
lines of ASCII output.
I made it ASCII instead of binary on purpose, so that someone
can obtain some useful data from it without the use of an
auxiliary program. However, with an auxiliary program, the numbers
in the first 4 columns of each "T:" line (topology info:
