Re: [Pyusb-users] Newbie Question

2008-09-03 Thread Christopher Moore
docs) and then piece that together into some controlMsg strings. Will I have to read back the interrupts after I send a control message? I've seen this in an example I came across from somewhere. Is the purpose of this to get a return on the status of the controlMsg command? Thanks. > &

Re: [Pyusb-users] Newbie Question

2008-09-03 Thread Sarah Messer
ul. -Sarah --- On Tue, 9/2/08, Christopher Moore <[EMAIL PROTECTED]> wrote: > From: Christopher Moore <[EMAIL PROTECTED]> > Subject: [Pyusb-users] Newbie Question > To: pyusb-users@lists.sourceforge.net > Date: Tuesday, September 2, 2008, 6:58 PM > Hey everyone, >

Re: [Pyusb-users] Newbie Question

2008-09-03 Thread Christopher Moore
I mean, if I do aplay -D plughw:CIT200,0 somewav.wav, nothing plays ... nor does arecord. I sent an email to libusb as well. It seems that there's an HID interface on this device that I need to talk to. Once I figure that out (I'm reading the hid docs as we speak), I would just "claim" that inte

Re: [Pyusb-users] Newbie Question

2008-09-03 Thread Wander Lairson
What do you mean by "not activated", does any write or read operation raise an exception? Wander 2008/9/2 Christopher Moore <[EMAIL PROTECTED]>: > Hey everyone, > > I'm trying to write my first program with pyUSB. I have already figured > out how to identify my device, open it, add it to a handl

[Pyusb-users] Newbie Question

2008-09-02 Thread Christopher Moore
Hey everyone, I'm trying to write my first program with pyUSB. I have already figured out how to identify my device, open it, add it to a handle, close it and claim it's interface. Here's my situation: The kernel recognizes my device ( a linksys cit200) as a device already and it actually shows

[Pyusb-users] Newbie Question

2008-09-02 Thread Christopher Moore
Hey everyone, I'm trying to write my first program with pyUSB. I have already figured out how to identify my device, open it, add it to a handle, close it and claim it's interface. Here's my situation: The kernel recognizes my device ( a linksys cit200) as a device already and it actually shows