mirror of
https://github.com/genodelabs/genode.git
synced 2024-12-28 09:38:53 +00:00
da2076e52a
This fixes issues with several HID keyboards by implementing get_unaligned_le16(), which obviously may also fix other not-yet-known issues. Hint: I had to look out for suspicious lines like follows in the verbose log. [init -> usb_drv] get_unaligned_le16 called, not implemented Also, quirks for cherry keyboards are now applied. |
||
|---|---|---|
| .. | ||
| lib/mk | ||
| patches | ||
| run | ||
| src | ||
| Makefile | ||
| README | ||
Device drivers ported from the Linux kernel USB ### HID ~~~ Supports keyboard and mouse. A run script can be found under 'run/usb_hid.run'. Configuration snippet: !<start name="usb_drv"> ! <resource name="RAM" quantum="3M"/> ! <provides><service name="Input"/></provides> ! <config> ! <hid/> ! </config> !</start> Note: It has been observed that certain 1.0 versions of Qemu do not generate mouse interrupts. The mouse driver should work correctly on Qemu 1.0.93 and above. Storage ~~~~~~~ Currently supports one USB storage device. Hot plugging has not been tested. A run script can be found under 'run/usb_storage.run'. Configuration snippet: !<start name="usb_drv"> ! <resource name="RAM" quantum="2M"/> ! <provides> <service name="Block"/> </provides> ! <config><storage /></config> !</start> Network (Nic) ~~~~~~~~~~~~~ Supported on PandaBoard only using the 'smsc95xx' driver. Configuration snippet: !<start name="usb_drv"> ! <resource name="RAM" quantum="3M"/> ! <provides> ! <service name="Nic"/> ! <service name="Input"/> ! </provides> ! <config> ! <nic mac="2e:60:90:0c:4e:01" /> ! <hid/> ! </config> !</start> Please observe that this setup starts the HID and Nic service at the same time. Also there is the 'mac' attribute where one can specify the hardware address of the network interface. This is necessary in case the EEPROM of the network card cannot be accessed via the host controller making it impossible to retrieve the devices hardware address. If this is the case and no 'mac' attribute is given a fallback address will be assigned to the network device. Note that the fallback address will always be the same.