Mario Limonciello schrieb:
> Hi Ari:
> Given that it can't grab a lock on the device, this probably is because the hald-addon-input service has the tight grip on it.
>
> Perusing the man page for hal, I don't see an easy way to turn this off.
> If you find a scriptable way to do so, we'd be glad to adapt.
>
> ** Changed in: lirc (Ubuntu)
> Importance: Undecided => Wishlist
> Status: New => Incomplete
>
>
Mario,
it's possible to tell HAL to ignore certain devices. Here's what we do
to tell HAL to ignore network interfaces (found on Cardoe's blog):
That file goes into usr/share/hal/fdi/preprobe/20thirdparty/. Maybe we
can do something similar for remotes, eg by expanding the hwdb to
contain a field which triggers a remote-specific HAL rule.. Or at least
document the ability to ignore devices somewhere.
Mario Limonciello schrieb:
> Hi Ari:
> Given that it can't grab a lock on the device, this probably is because the hald-addon-input service has the tight grip on it.
>
> Perusing the man page for hal, I don't see an easy way to turn this off.
> If you find a scriptable way to do so, we'd be glad to adapt.
>
> ** Changed in: lirc (Ubuntu)
> Importance: Undecided => Wishlist
> Status: New => Incomplete
>
>
Mario,
it's possible to tell HAL to ignore certain devices. Here's what we do
to tell HAL to ignore network interfaces (found on Cardoe's blog):
<?xml version="1.0" encoding="UTF-8"?> >true</ merge>
<deviceinfo version="0.2">
<device>
<match key="net.interface" exists="true">
<merge key="info.ignore" type="bool"
</match>
</device>
</deviceinfo>
That file goes into usr/share/ hal/fdi/ preprobe/ 20thirdparty/ . Maybe we
can do something similar for remotes, eg by expanding the hwdb to
contain a field which triggers a remote-specific HAL rule.. Or at least
document the ability to ignore devices somewhere.