Device drivers ported from the Linux kernel USB ### Controller configuration ~~~~~~~~~~~~~~~~~~~~~~~~ The driver can be started using different or all USB controller types a platform offers (USB 1.0/2.0/3.0). Note that not all controllers are supported by all platforms. Controllers can be enabled as attribute in the config node of the driver. Supported attributes are: 'uhci', 'ehci', and 'xhci'. Configuration snippet to enable UHCI and EHCI ! HID ~~~ Supports keyboard and mouse. A run script can be found under 'run/usb_hid.run'. Configuration snippet: ! ! ! ! ! ! ! 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. HID - Touchscreen support ~~~~~~~~~~~~~~~~~~~~~~~~~ Touchscreen absolute coordinates must be calibrated (e.g. re-calculated) to screen absolute coordinates. The screen resolution is not determined automatically by the USB driver, but can be configured as sub node of the hid xml tag: !... ! ! ! !... If a touchscreen is multi-touch-capable than the multitouch attribute gears which type of Genode input events are generated. If set to 'no' (default) than absolute events are generated and no multitouch events. If set to 'yes' solely multitouch events are generated. 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: ! ! ! ! ! Network (Nic) ~~~~~~~~~~~~~ Configuration snippet: ! ! ! ! ! ! ! ! ! ! ! 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. LXIP #### LXIP is a port of the Linux TCP/IP stack to Genode. It is build as a shared library named 'lxip.lib.so'. The IP stack can be interfaced using Genode's version of 'libc' by linking your application to 'lxip_libc' plugin in your 'target.mk' file. WIFI #### The wifi_drv component is a port of the Linux mac802.11 stack, including the iwlwifi driver as well as libnl and wpa_supplicant, to Genode. Configuration snippet: ! ! ! ! ! ! ! ! ! ! ! !network={ ! id_str="foobar" ! ssid="foobar" ! key_mgmt=WPA-PSK ! psk="foobarfoobar" !} ! ! ! ! ! ! ! ! ! ! ! ! ! Each accesspoint node has attributes that contain the SSID and the BSSID of the accesspoint as well as the link quality (signal strength). These attributes are mandatory. If the network is protected, the node will also have an attribute describing the type of protection in addition. The second report provides information about the state of the connection to the currently connected accesspoint: ! ! ! Valid state values are 'connected', 'disconnected', 'connecting' and 'disconnecting'. In return, the wifi_drv get its configuration via a ROM module. This ROM module contains the configuration for the selected accesspoint. To connect to an open accesspoint a configuration like the following is used: ! If the network is protected by, e.g., WPA/WPA2, the protection type as well as the the pre-shared key have to be specified: ! If a network consists of several different access points and a particular one should be used it can be selected by specifing its BSSID in a 'bssid' attribute. Of all attributes only the 'ssid' attribute is mandatory, all others are optional and should only be used when needed. To disconnect from an accesspoint, a empty configuration is sent: ! By subscribing to both reports and providing the required ROM module, a component can control the wireless driver. An example therefore is the Qt based component in 'src/app/qt_wifi_connect'. Currently only WPA/WPA2 protection using a pre-shared key is supported. RAW ~~~ Allows raw access to USB devices via the 'Usb' session interface. Configuration snippet: ! ! ! ! ! ! ! ! ! The optional 'devices' report lists the connected devices and gets updated when devices are added or removed. Example report: There is no distinction yet for multiple devices of the same type.