login
Header Space

 
 

USB device debugging & ioctls

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <kernel@...>
Date: Friday, November 30, 2007 - 8:16 am

Hello all -

I'm trying to do a bit of detctive work on a so-called linksys wusb54g
that I thought would work with rum(4) and came across a couple of things:

- If I'm not mistaken, there is no pciconf equivelant for usb devices?
  (e.g. to easily determine vendor ID's, etc)

- Thinking that there wasn't, I started to use the
  USB_GET_DEVICEINFO ioctl, which did the trick.

However, to get the USB ioctls to work my program needed to pull
in sys/ioccom.h in order to have the ioctl '_IOR' macro used in
bus/usb/usb.h to expand properly.

This didn't seem correct and caused me a bit of wasted time to figgure
out..

It seemed like either the ioctl / usb / ? documentation needs to be
updated to list sys/ioccom.h as a needed header, or the usb header
needs to do something like ata.h, e.g.

#ifndef _SYS_IOCCOMM_H_
#include <sys/ioccom.h>
#endif

Comments?

Thinking it might make sense to try to do a sweep of any
ioctl defining headers & add the appropriate includes, but wanted to
check the approach here.

Thanks,

- Chris
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
USB device debugging & ioctls, Chris Turner, (Fri Nov 30, 8:16 am)
Re: USB device debugging &amp; ioctls, Sascha Wildner, (Fri Nov 30, 8:47 am)
Re: USB device debugging &amp; ioctls, Chris Turner, (Sat Dec 1, 10:46 pm)
speck-geostationary