Hi Christoph,

I had a brief ponder over this.
A couple of years ago I modified & expanded Atmel's original MSD project
(for SAM7 which is ARM7) to compile under GCC, but since it's been so
long I'm somewhat fuzzy. I do recall the class USBGenericRequest.
I can't readily access my project files right now to verify my
conjecture but by looking at your log, I think your device might be
using the USBGenericRequest Class to query/report the button press.

IIRC USBGenericRequest can specify which pipe will be used for the data
transfer, its length/direction, recipient etc.

I do recall that Snoopy didn't log nor display string descriptors et al,
but I thought it did display what's going on in the control pipe (ie.
EP0). If so, see if such requests are used. Is this traffic rate also
observed when you're mounted to a Linux host ? (I dunno if Snoopy runs
under Linux, must check that). Else it could be that WIN's standard
driver somehow was told that it should issue some poll on the control
pipe, I'd have thought using GET_STATUS in USBGenericRequest...

Also, it's not clear whether the button poll is when that little WIN
button app is installed, or whether usbstor.sys itself is doing that ?

HTH.



On Fri, 2009-02-13 at 09:58 +0100, Christoph Gysin wrote:

> The traffic from/to the device doesn't seem to settle. It keeps on
> flooding the log. Around 100 pakets per second. After ~25s:
> 
> up   25.875   BULK_OR_INTERRUPT_TRANSFER      -       0x00000000
> down 25.875   BULK_OR_INTERRUPT_TRANSFER      00 00 00 00 7f 20 00 00 
> up   25.875   BULK_OR_INTERRUPT_TRANSFER      70 00 02 00 00 00 00 0a 
> 0x00000000
> down 25.875   BULK_OR_INTERRUPT_TRANSFER      55 53 42 43 08 8d e2 81 
> up   25.875   BULK_OR_INTERRUPT_TRANSFER      55 53 42 53 08 8d e2 81 
> 0x00000000
> down 25.875   BULK_OR_INTERRUPT_TRANSFER      55 53 42 43 08 8d e2 81 
> up   25.891   BULK_OR_INTERRUPT_TRANSFER      -       0x00000000
> down 25.891   BULK_OR_INTERRUPT_TRANSFER      00 00 00 00 00 00 00 00 
> up   25.891   BULK_OR_INTERRUPT_TRANSFER              0xc0000004
> down 25.891   RESET_PIPE              
> up   25.891   RESET_PIPE              0x00000000

> Thanks for your help,
> Chris



--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ

Reply via email to