evdev-1.2.0 / hal-0.5.10 combo broken?

pcpa at mandriva.com.br pcpa at mandriva.com.br
Thu Jan 17 19:20:03 PST 2008


Quoting Daniel Stone <daniel at fooishbar.org>:

> On Thu, Jan 17, 2008 at 11:01:21PM -0200, pcpa at mandriva.com.br wrote:
>>   I believe one the issues is the "forcing" on using evdev instead of
>> "kbd" or "mouse".
>
> Yes, it is being 'forced', as it were.  You say that as if it's a bad
> thing.

  I did not say it is a bad thing, if I had said, I would quote it
differently, like as in *forcing*. I belive evdev X Input driver is
almost functional to replace kbd and mouse, but may need some tweaking,
at least 3 button mouse emulation...

>>   Other issue is that there is no full integration with configuration
>> from xorg.conf, and to make things worse, hal configuration code doesn't
>> know about xorg.conf configuration code, and both do "its own thing"
>> when starting the X Server, i.e. frequently 2 instances of the same
>> module or 2 different modules handling the same device.
>
> Can you please show me where this ever happens?  evdev was specifically
> designed to avoid this, and I'd like to see some proof of it going
> wrong.  I've seen it go badly wrong when Ubuntu merged a patch from some
> derivative distro whose name I forget (maybe it was PepperPad) that
> broke evdev, but that's it.

  Check "inputInfo.devices" list at the first call to
xserver/config/hal.c:device_added(). This of course if there is
any "InputDevice" section in xorg.conf.
  This is what I asked in other email, see also
https://bugs.freedesktop.org/show_bug.cgi?id=13361
for more details.

>>   Hal config code also only knows about what hal queries return, and
>> I believe there are only graphical "user friendly" configuration tools,
>> i.e. chicken and egg problem :-) If only hal config code is used, and
>> hal is misconfigured, things will not go very well...
>
> No, that's completely and utterly wrong.  HAL cannot be configured with
> any GUI tool that I know of, and only parses text files.  Oh well.

  I was expecting that some tool would already exist or be in the works,
cut&paste of hal udis and uuids in a terminal isn't much easy for
configuration purposes :-)

> Cheers,
> Daniel

Paulo






More information about the xorg mailing list