Advantech RSB-4210 Evaluation Kit User Manual Page 100

  • Download
  • Add to my manuals
  • Print
  • Page
    / 104
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 99
RSB-4210 User Manual 92
Device drivers are the modules that generate events. The events are however not
useful without being handled, so you also will need to use some of the modules from
section 3.10.9.3.2.
A. usbhid
usbhid is the largest and most complex driver of the whole suite. It handles all HID
devices, and because there is a very wide variety of them, and because the USB
HID specification isn't simple, it needs to be this big.
Currently, it handles USB mice, joysticks, gamepads, steering wheels keyboards,
trackballs and digitizers.
However, USB uses HID also for monitor controls, speaker controls, UPSs, LCDs
and many other purposes.
The monitor and speaker controls should be easy to add to the hid/input interface,
but for the UPSs and LCDs it doesn't make much sense. For this, the hiddev inter-
face was designed. See Documentation/usb/hiddev.txt for more information about
it.
The usage of the usbhid module is very simple, it takes no parameters, detects
everything automatically and when a HID device is inserted, it detects it appropri-
ately.
However, because the devices vary wildly, you might happen to have a device that
doesn't work well. In that case #define DEBUG at the beginning of hid-core.c and
send me the syslog traces.
B. usbmouse
For embedded systems, for mice with broken HID descriptors and just any other
use when the big usbhid wouldn't be a good choice, there is the usbmouse driver.
It handles USB mice only. It uses a simpler HIDBP protocol. This also means the
mice must support this simpler protocol. Not all do. If you don't have any strong
reason to use this module, use usbhid instead.
C. usbkbd
Much like usbmouse, this module talks to keyboards with a simplified HIDBP proto-
col. It's smaller, but doesn't support any extra special keys. Use usbhid instead if
there isn't any special reason to use this.
D. wacom
This is a driver for Wacom Graphire and Intuos tablets. Not for Wacom PenPart-
ner, that one is handled by the HID driver. Although the Intuos and Graphire tab-
lets claim that they are HID tablets as well, they are not and thus need this specific
driver.
E. iforce
A driver for I-Force joysticks and wheels, both over USB and RS232. It includes
ForceFeedback support now, even though Immersion Corp. considers the proto-
col a trade secret and won't disclose a word about it.
2. Event handlers
Event handlers distribute the events from the devices to userland and kernel, as
needed.
A. keybdev
keybdev is currently a rather ugly hack that translates the input events into archi-
tecture-specific keyboard raw mode (Xlated AT Set2 on x86), and passes them
into the handle_scancode function of the keyboard.c module. This works well
enough on all architectures that keybdev can generate rawmode on, other archi-
tectures can be added to it.
Page view 99
1 2 ... 95 96 97 98 99 100 101 102 103 104

Comments to this Manuals

No comments