On Tue, 16 Apr 2002 11:24, Steve Bangert wrote: > Hi, > > I'm trying to get my hid buttons on my USB speakers working and ran into > a little trouble with the hiddev driver, > If I "cat /dev/usb/hiddev0" (with kernel 2.4.19-pre6) i get "No such > device". However if i reboot into the Redhat > errata kernel (2.4.9) I get output when I push the volume up/down > buttons on the speakers, I've recompiled the > 2.4.19-pre6 kernel with USB debugging enabled. I've attached output > from both /var/log/messages and > /var/log/dmesg, Any thoughts? Thanks I've been doing some test coding with hiddev and evdev with 2.4.19-pre6, and it works fine for me. Perhaps you just need some documentation?
I've enclosed an extract of the SGML from my HID documentation project :) Basically, there was a change in 2.4.10 that reworked the input support. HID devices now get routed to hiddev or input depending on the Application(s?) reported by the HID device (see IS_INPUT_APPLICATION() in drivers/usb/hid.h) 2.4.19-pre6 also has some changes, so that input can be removed, and everything goes to hiddev. You say "I get output". Is this on hiddev? Do you have HIDDEV support and INPUT support in your kernel config? Specifically, what are the values of CONFIG_USB_HID CONFIG_USB_HIDINPUT CONFIG_USB_HIDDEV what are you reading, and what are you reading with? For speakers, we probably shouldn't be using hiddev (despite an earlier mistake I made, writing a hiddev plugin to xmms). USB speakers are not different from multimedia keyboards (from a HID view), and it all should work through input. If it doesn't work, we probably just need to add the right application to the IS_INPUT_APPLICATION test. Brad - - <Sect1><title>How HID devices relate to the hiddev interface</title> <para> As stated in a prior chapter, the USB host controller interacts with the USB devices on its bus. The USB core functionality ensures that information associated with HID devices is delivered to the HID device driver (<filename>hid.o</filename>). The HID device driver then uses the Application of the particular USB device interface to determine whether the device is an input type device (such as a keyboard, mouse, joystick or gamepad) or is some other HID device (such as a USB monitor control, or a uninterruptable power supply). </para> <para> If the device appears to be an input type device, and the HID device driver was compliled to support the input subsystem, then the information from the HID device will be provided to the input subsystem (where it can be accessed using joystick, mouse, keyboard or event interfaces, as discussed in later chapters). </para> <para> If the device does not appear to be an input device (or there is no input subsystem support in the HID device driver) and the HID device driver has been compiled to support the hiddev driver, then the information provided by the HID device will be made available on the hiddev interface, which is the subject of this chapter. </para> </Sect1> _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
