sorry, I forgot to cc the list. Since I just got the welcome to the -
[email protected] Mailinglist, this mess should stop now

Christof
-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments
--- Begin Message ---
Hello,

> Have you looked at libusb?
I had not looked at it. I have to admit that I made a mistake concerning the 
device names.
This is what the kernel finds when plugging in the device:

ugen0.3: <Logitech> at usbus0
ums0: <Logitech USB Receiver, class 0/0, rev 2.00/42.00, addr 3> on usbus0
ums0: 16 buttons and [XYZ] coordinates ID=0
uhid0: <Logitech USB Receiver, class 0/0, rev 2.00/42.00, addr 3> on usbus0

so the led-device gets recognized as uhid0. Maybe that is why that your sample 
code from http://archive.netbsd.se/?ml=freebsd-usb&a=2008-12&t=9232208
never returns from a  libusb20_dev_wait_process in do_io()?

Now I am unsure whether I should stick with hid or fully get rid of it :)
Considering the fact that the author of libusb seems to be willing to help & 
considering the state of the usbhid documentation I am tempted to get rid of 
it. 

In that case I would have to convince the kernel that this is not a hid drive 
and create different device class. How would I go about that?

After all I would find it cool if it worked for *my* mouse but it would be 
much cooler if other people could use that software too. Please be easy on me 
if this is a beginners question - but that is what I am as this is my first 
attempt for doing some FreeBSD-specific coding.

> what version of FreeBSD are you using?
This is a 8_RELENG system.

Regards

Christof

-- 
()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to