Loïc: no need to provide the lshal information anymore, the fdi file in -joystick won't be updated, and for Jaunty there is no need to list every model there is to use the driver, since hopefully by then the kernel/hal will know when the input device is a joystick (not true atm).
If you use the AutoAddDevices -trick, you'll also disable input-hotplug completely (for mice & keyboards etc). That is not recommended. Like I said, just put a file like this in /etc/hal/fdi/policy and you should be able to use the joystick in games like before:
---
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="PRODUCT ID OF YOUR JOYSTICK">
<merge key="input.x11_driver" type="string"></merge>
</match>
</device>
</deviceinfo>
---
and replace the PRODUCT.. stuff with the name of the device, use lshal or lsinput to find it out. Note that the x11_driver is empty. It means that evdev (or any other driver for that matter) will not use the device.
Loïc: no need to provide the lshal information anymore, the fdi file in -joystick won't be updated, and for Jaunty there is no need to list every model there is to use the driver, since hopefully by then the kernel/hal will know when the input device is a joystick (not true atm).
If you use the AutoAddDevices -trick, you'll also disable input-hotplug completely (for mice & keyboards etc). That is not recommended. Like I said, just put a file like this in /etc/hal/fdi/policy and you should be able to use the joystick in games like before: "ISO-8859- 1"?> x11_driver" type="string" ></merge>
---
<?xml version="1.0" encoding=
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="PRODUCT ID OF YOUR JOYSTICK">
<merge key="input.
</match>
</device>
</deviceinfo>
---
and replace the PRODUCT.. stuff with the name of the device, use lshal or lsinput to find it out. Note that the x11_driver is empty. It means that evdev (or any other driver for that matter) will not use the device.