Rather than launching hid2hci upon every boot even when the user
doesn't have hardware that needs it installed, launch it from
a set of udev rules that matches the hardware by attributes.
---
scripts/Makefile.am | 9 ++++++++-
scripts/bluetooth.default | 3 ---
scripts/bluetooth.init | 7 -------
scripts/hid2hci.rules | 38 ++++++++++++++++++++++++++++++++++++++
4 files changed, 46 insertions(+), 11 deletions(-)
create mode 100644 scripts/hid2hci.rules
--
Mario Limonciello
*Dell | Linux Engineering*
[email protected]
Hi Mario,
> Rather than launching hid2hci upon every boot even when the user
> doesn't have hardware that needs it installed, launch it from
> a set of udev rules that matches the hardware by attributes.
>
> ---
> scripts/Makefile.am | 9 ++++++++-
> scripts/bluetooth.default | 3 ---
> scripts/bluetooth.init | 7 -------
> scripts/hid2hci.rules | 38 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 46 insertions(+), 11 deletions(-)
> create mode 100644 scripts/hid2hci.rules
I had to redo the whole thing, but should be working :)
Regards
Marcel