Problem with input device

Kristian Høgsberg krh at
Mon Jun 7 09:43:54 PDT 2004

Joe Shaw wrote:
> On Fri, 2004-06-04 at 15:46 +0200, Kristian Høgsberg wrote:
>>OK, here's an attempt.  Once you figure out how the callbacks work, HAL 
>>is actually pretty easy to work with.  For now I only accept the event%d 
>>devices when there is no sysfs device, since I couldn't figure out how 
>>to use ioctl()'s to correlate e.g. mouse5 with event7.  Maybe it's 
>>necessary to parse /proc anyway :-(.  Or maybe just add the kernel 
>>support so HAL can merge them.
> This is nice!  I'll commit it.

Great, thanks for writing the changelog entry.

> You probably won't be able to fix the
> mouse5/event7 thing w/o fixing the kernel, but I'd highly recommend
> doing that anyway. :)

Yeah, that's the better solution.  I might just look into that, but for 
now this works well enough for me.

>>Oh, and the problem I had with missing input.* properties was because 
>>udev didn't call  It works now.  Could HAL use the udev helper 
> The dbus support in udev you mean?  It's being removed because dev.d is
> the Right Way to do this stuff.

Ah, okay, so /etc/dev.d/default/ is removed from udev and udev 
clients (like HAL) are then required to install their own callout in 


hal mailing list
hal at

More information about the Hal mailing list