Josef Söntgen c10ad4ff01 ps2_drv: back down after unsucessful AUX access ... The driver might end up in an endless loop on systems that do not contain an i8042 controller when probing the AUX interface. This leads to busy looping and in the end to not annoucing the Input service. Components that wait for the announcement of the service will therefore hang as well. Normally a service gets announced only if it is usable but in this case this is inconvient because it renders all scenarios that use the input_merger non working on x86 systems that only provide USB input and do not have PS/2 at all. Ideally, the PS/2 driver should only be started if the system needs it. That is currently not feasible and for the time being we post-pone the inevitable and back down after several unsucessful attempts to read from the AUX interface while initializing the driver. Fixes #1871.		2016-02-05 10:59:10 +01:00
..
app	os: add component for filtering USB devices report	2016-01-27 16:15:34 +01:00
drivers	ps2_drv: back down after unsucessful AUX access	2016-02-05 10:59:10 +01:00
init	Introduce 'spec' subdirectories to outline aspects	2015-09-16 13:58:50 +02:00
lib	base: Dispatch server signal in entry point	2015-10-28 15:06:22 +01:00
server	nic_bridge: use the server framework (fix #1865)	2016-02-05 10:47:45 +01:00
test	vfs stress: prevent warnings when logging size_t	2016-02-05 10:47:45 +01:00