Bug#355497: [Pkg-bluetooth-maintainers] Bug#355497: bluez-utils: hid2hci --tohid does not work

Mourad De Clerck debian-bugs at aquazul.com
Thu Jun 1 19:25:54 UTC 2006


On 01/06/06 19:10, Filippo Giunchedi wrote:
> On Mon, Mar 06, 2006 at 08:52:13PM +0000, Edd Dumbill wrote:
>> On Mon, 2006-03-06 at 03:47 +0100, Mourad De Clerck wrote:
<snip>
>>> So bottom line is: switching from HID to HCI works, switching back doesn't 
>>> (and never has I might add). For the record: my keyboard is a Logitech DiNovo 
>>> Media Desktop with an MX900 BT mouse.
<snip>
>> We should probably make this configurable and switch it off by default.
<snip>
> So what might be the best thing to do here?
> HID2HCI_ENABLED=0 in /etc/default/bluetooth and modify /etc/init.d/bluetooth
> accordingly? (and put a note in NEWS.Debian about it)
> 
> which are the effects of not switching it on at boot like it is done now?

Well, I'm not sure if this is the case with all dongles, but in my case
not switching means bluetooth won't work.

HID devices will look like fake USB HID devices, so they'll still work,
and at reboot-time (BIOS screen, boot loader etc) these HID devices will
be usable too. However, non-HID bluetooth devices won't work until the
user chooses to switch it from HID to HCI mode.

I tend to think it should stay on by default, because I'd presume that
users that install the bluetooth package would actually want to use
bluetooth. It sucks for people like me who have to manually switch it
off again so they can access their bootloader/bios on reboot, but I can
either not install the bluetooth package if I only have HID devices, or
manually deactive it if I "sometimes" use other types of devices.

I think the best thing of course would be to get hid2hci fixed so it
works in both directions, and I'll probably file a bug upstream. This
might not be possible to fix because of lack of documentation, and/or
hardware to reverse-engineer - I don't know anything about USB sniffing.

Another option I might look into, is to power down the USB port/hub in
the shutdown scripts (via sysfs for example), so the dongle gets reset
(a hard reset usually brings the dongle back to its original state, ie
HID mode).

However even if both of these wouldn't work I think it's best to leave
it on. No sense in causing problems for users with working hardware, if
it doesn't even solve the problem for users with problematic hardware.

Thanks,

-- M




More information about the Pkg-bluetooth-maintainers mailing list