Hi Greg,
How do I get USB device info, such as bus, level and port? Is there any
way other than reading the proc (/proc/bus/usb/device)file.
Regards,
Shalini G
---
SF email is sponsored by - The IT Product Guide
Read honest & candid re
On Wed, Mar 31, Greg KH wrote:
> Other than that, it looks sane. Let us know if there are any problems
> reported with it.
I will add this version.
diff -purNX /kernel_exclude.txt
linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/driverfs.c
linux-2.6.5-rc3-olh-usb/drivers/usb/core/driverfs.c
-
On Wed, Mar 31, 2004 at 06:05:32PM +0200, Olaf Hering wrote:
> diff -purNX /kernel_exclude.txt linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/usb.c
> linux-2.6.5-rc3-olh-usb/drivers/usb/core/usb.c
> --- linux-2.6.5-rc3-olh-usb.orig/drivers/usb/core/usb.c 2004-03-31
> 11:17:44.0 +
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
> >
> > No. make it static. Always.
>
> How about adding a patch that does this to your tree and see if any of
> your users's devices break? If such a patch lives successfully in a
> distro patch for
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
> >
> > No. make it static. Always.
>
> How about adding a patch that does this to your tree and see if any of
> your users's devices break? If such a patch lives successfully in a
> distro patch for
On Tue, Mar 30, 2004 at 08:15:52PM +0200, Olaf Hering wrote:
>
> No. make it static. Always.
How about adding a patch that does this to your tree and see if any of
your users's devices break? If such a patch lives successfully in a
distro patch for a release cycle or two, I'd be willing to add i
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 08:18:12PM +0200, Olaf Hering wrote:
> > On Tue, Mar 30, Greg KH wrote:
> >
> > > On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> > > >
> > > > WHY is all the vendor, product, serial and what not info still dynamic?
> > >
On Tue, Mar 30, 2004 at 08:18:12PM +0200, Olaf Hering wrote:
> On Tue, Mar 30, Greg KH wrote:
>
> > On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> > >
> > > WHY is all the vendor, product, serial and what not info still dynamic?
> > > How can the info change during the "lifetime"
On Tue, Mar 30, Greg KH wrote:
> On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
> >
> > WHY is all the vendor, product, serial and what not info still dynamic?
> > How can the info change during the "lifetime" of an attached USB device?
>
> Because the device can change those stri
On Tue, Mar 30, David Brownell wrote:
> Olaf Hering wrote:
> >
> >The current situation is, that reading the "serial" file of an USB
> >storage device leads to an empty serial file, in some situations.
>
> What are those situations?
There is some silly sort of media change polling. This keeps
Olaf Hering wrote:
The current situation is, that reading the "serial" file of an USB
storage device leads to an empty serial file, in some situations.
What are those situations?
I keep thinking the code to fetch string (and config, and device)
descriptors needs some fault handling and retry logi
On Tue, Mar 30, 2004 at 05:58:31PM +0200, Olaf Hering wrote:
>
> WHY is all the vendor, product, serial and what not info still dynamic?
> How can the info change during the "lifetime" of an attached USB device?
Because the device can change those strings at any time if it wants to
(and I've seen
Hello,
we had that /proc/bus/usb/devices file, which was nice and the whole
world used it to find info about the attached usb devices. The bug in
this file was (and still is) that it is created on the fly, its content
is not static.
Now we have sysfs, and to my surprise, the content is STILL dyna
13 matches
Mail list logo
