On Thu, May 17, 2001 at 05:22:02AM +1000, Brad Hards wrote:
>
> If you want to be advised when things change, use the usbview code (see
> http://sourceforge.net/projects/usbview/) that Greg K-H wrote as an example. I
> think it polls on /proc/bus/usb/devices for changes. You might be able to use
> I'm writing an application that works with a USB device. The device
> itself is expected to be plugged and unplugged during the lifetime
> of the application, so I'm looking for a way to follow the state of
> the device. It's a GTK application, I have no problem with using
> timers.
[EMAIL PRO
Stephen Williams wrote:
>
> I'm writing an application that works with a USB device. The device
> itself is expected to be plugged and unplugged during the lifetime
> of the application, so I'm looking for a way to follow the state of
> the device. It's a GTK application, I have no problem with u
> I'm writing an application that works with a USB device. The device
> itself is expected to be plugged and unplugged during the lifetime
> of the application, so I'm looking for a way to follow the state of
> the device. It's a GTK application, I have no problem with using
> timers.
>
> I'm con
I'm writing an application that works with a USB device. The device
itself is expected to be plugged and unplugged during the lifetime
of the application, so I'm looking for a way to follow the state of
the device. It's a GTK application, I have no problem with using
timers.
I'm considering usin
