Strange issue with hal and Xorg

[Justin Mattock]

On Fri, Jun 12, 2009 at 11:06 AM, Matt Hayes<dominian at slackadelic.com> wrote:
> walt wrote:
>> Matt Hayes wrote:
>>> Dan Nicholson wrote:
>>>> On Fri, Jun 12, 2009 at 5:46 AM, Matt Hayes<dominian at slackadelic.com>  wrote:
>>>>> Hrm.. so where the heck is the "32" buttons coming from?  That's very
>>>>> odd and causes mapping of buttons to be a pita.
>>>> The evdev driver. Perhaps you were using the mouse driver in xorg.conf?
>>>>
>>> That is possible.  I will have to look at changing the mouse driver in a
>>> hal policy or Xorg.conf and see what that reveals.
>>
>> I recently switched to using evdev and when I removed the InputDevice sections
>> from xorg.conf I had to add an fdi file to /etc/hal/fdi/policy (which I cleverly
>> named 10-x11-logitech.fdi) containing this:
>>
>> <?xml version="1.0" encoding="ISO-8859-1"?>
>> <deviceinfo version="0.2">
>>    <device>
>>      <match key="info.product" contains="ImExPS/2">
>>        <merge key="input.x11_options.EmulateWheel" type="string">true</merge>
>>        <merge key="input.x11_options.EmulateWheelButton" type="string">8</merge>
>>      </match>
>>    </device>
>> </deviceinfo>
>>
>> I constructed that file by looking at mouse-oriented parts of the output of
>> 'lshal' and just stuck the options in where it looked reasonable.
>>
>> It worked, and I'm still amazed.
>
> Well, I will give that a shot.  I need to learn how this hal stuff works
> anyway :)
>
> -Matt
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>

Don't want to confuse you, but hal
is being fazed out.
udev-142 is now responsible for handling
volumeid etc...


-- 
Justin P. Mattock