It is not the ioctl command itself that I really had a question about. My
real question should have been:
What parameter do you pass to the 'open' command to retrieve a file
descriptor to use in subsequent ioctl commands?
Thanks again,
Dan
Greg KH <[EMAIL PROTECTED]>
Sent by: To:
[EMAIL PROTECTED]
[EMAIL PROTECTED] cc:
[EMAIL PROTECTED]
eforge.net Subject: Re:
[linux-usb-devel] Application ioctl to USB driver
12/17/2001 01:00 PM
On Mon, Dec 17, 2001 at 12:47:13PM -0600, [EMAIL PROTECTED] wrote:
> Hello,
>
> We have a stand-alone device with a USB I/F for downloading code to Flash
> memory. Currently the only means of downloading the Flash code is via a
> DOS program (actually running from DOS, not Windows). We are trying to
> move this to Linux to eliminate the need for DOS. A skeleton driver is
up
> and answers the probe requests.
> The question is, how does an application attach to and send IOCTL to a
USB
> driver?
If you are only downloading firmware, I'd recommend using
usbdevfs/usbfs. This allows userspace programs to talk to usb devices.
See libusb for an easier interface to the devices: http://libusb.sf.net/
As for sending an ioctl to a driver, see the ioctl(2) man page :)
thanks,
greg k-h
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
