Problem with input device

Bill Nottingham notting at
Wed Jun 2 11:32:38 PDT 2004

Joe Shaw (joeshaw at said: 
> > I can see there is no sysfs device for those devices, the closest thing 
> > is the keyboard controller /sys/devices/system/i8042, I guess.  So of 
> > course HAL can't see those devices.  What's the best way to change that?
> The really correct thing would be to add sysdevice support to the kernel
> driver, I think.
> Failing that you could probably write an accept function for the input
> class device handler which doesn't check for sysdevices and instead
> checks the name against a pattern (mouse%d, for example).  You'd also
> have to implement a compute_udi method.  That way they'd get added to
> the City of Lost Devices.  You can look in net_class_device.c to see how
> it's done for PCMCIA cards.
> Problem with this approach is that you have absolutely no identifying
> information about the device.  I guess you could just assume that it's a
> PS/2 mouse.

Well, all of the input devices are in /proc/bus/input/devices; so you
can determine keyboard/ps2-mouse/touchpad, etc.


hal mailing list
hal at

More information about the Hal mailing list