>No, it's the correct place. But you should start out by learning the
>basics. Read through parts of the USB 2.0 spec and then you'll be in
>better shape.
>
>
>
I've READ the specs, examined countless examples, browsed innumerable
websites. This is a silly, simple little keyboard device cu
Alan Stern wrote:
>On Wed, 18 Apr 2007, John Wojnaroski wrote:
>
>
>
>>OK, so an IN transfer might look something like <22 09 0200 >
>>
>>
>
>Except that it couldn't use 0x22 in the first byte. The high-order bit of
>that byte d
Alan Stern wrote:
>On Mon, 16 Apr 2007, John Wojnaroski wrote:
>
>
>
>>OK, attached is a log report.Not all that conversant in analyzing
>>the log. about the only item I note is the order of the last two bytes
>>defining the packet size; SnoopyPro shows
Alan Stern wrote:
On Mon, 16 Apr 2007, John Wojnaroski wrote:
Okay, I will do that, so if I understand your direction
get SnoopyPro from sourceforge, install it under MS windows, and run
some traces with the device working under that OS
then post the results
correct?
That&#
Alan Stern wrote:
>On Sun, 15 Apr 2007, John Wojnaroski wrote:
>
>
>
>>Hi Alan,
>>
>>Thanks for working your way through my mess.
>>
>>I was trying a numer of ideas last night and things got a little convoluted.
>>
>>You've answered my
Hi,
I've been plowing through the various specs on USB trying to find an
answer, but my eyes are starting to hurt ;-)
Perhaps some one knows the answer and a pointer to the reference
Does USB require a CRC of the data packet for the four types of msgs
sent? If so is that value calculated by t
Alan Stern wrote:
>On Sat, 14 Apr 2007, John Wojnaroski wrote:
>
>
>
>>Is there a simple, quick, uncomplicated tool to look see what is
>>actually going down the wire? Lots of sniffers for MS stuff, could not
>>find similar tools for the linux OS. Something al
ally performed and added to the message. I
suspect the USB Host device automatically puts that in. Would seem
reasonable, can't find anything to expicitly confirm the CRC calculation.
Any suggestions would be appreciated... in the interest of brevity,
I'll not include the source for n
Hi,
I'm writing a simple little driver to read three bytes from a hid device
when plugged in it reports as hiddev96:__--usb-:00:1d.0-2
and shows up in /dev/usb/hiddev0 and is enumerated in
/proc/bus/usb/devices.
Thinking a simple usb_control_msg will be good and simple enough t
