You wrote:
> My current driver for our IR sensor peripheral uses the HIDDEV
> interface. It performs read() on /dev/usb/hiddevX, which results in
> interrupt transfers of all inbound data. Kudos to Mr. Stewart and Mr.
> Pavlik for making this very simple!
Do read()s actually result in interrupt tr
On Sun, Feb 09, 2003 at 01:24:55PM -0500, John Homppi wrote:
>
> An aside for Jeff:
> Please indicate whether the following analysis matches your research
> regarding the Evolution Robots platform.
>
Your analysis follows mine exactly.
> It is important to differentiate the endpoints
Hi Brad,
Thanks for your message and the web link:
>http://www.frogmouth.net/hid-doco/examples/hiddev-misc/write-events.c
Unforunately the HIDIOCSREPORT ioctl will not meet the need.
Perhaps I need to be more explicit about the problem.
There is a discrepancy between the hiddev architecture and t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 9 Feb 2003 05:46, John Homppi wrote:
> The HID device interface would appear to be the answer except
> the hiddev.c source code for 2.4.20 and 2.5.59 reads:
> static ssize_t hiddev_write(..
> {
> return -EINVAL;
> }
You don'
My apologies to the group about the content of this thread.
My original message was E-mailed offline but the replies
from others appeared on linux-usb-devel.
I was attempting to explain my motives for moving my
experimental driver development off-line from the group.
Any deficiencies are in MY
