|
From: Tyler N. <tyl...@co...> - 2003-09-16 21:37:07
|
OK. I found the file README_MISSING_SYSCALL_OR_IOCTL. This answers most of my questions. So I traced through the defines, and the USB_BULK_READ is a define to some: _IOWR(...) This seems to be my problem, is that right? If I went in and changed them to be _IOW or _IOR, then the default ioctl would work correctly. Thanks for the help, -- Tyler Nielsen <tyl...@co...> |
|
From: Jeremy F. <je...@go...> - 2003-09-24 14:35:49
|
On Tue, 2003-09-16 at 23:37, Tyler Nielsen wrote: > OK. I found the file README_MISSING_SYSCALL_OR_IOCTL. This answers > most of my questions. So I traced through the defines, and the > USB_BULK_READ is a define to some: > > _IOWR(...) > > This seems to be my problem, is that right? > > If I went in and changed them to be _IOW or _IOR, then the default ioctl > would work correctly. But that would change the ioctl number, and break binary compatibility, no? The better solution is to either add client calls into libusb (VALGRIND_MAKE_READABLE, etc), or add code to Valgrind itself to understand these calls. J |