From: Aaron Seibert <aaron@awseibert.net>
To: linux-bluetooth@vger.kernel.org
Subject: hid2hci not switching to hci mode
Date: Mon, 17 Aug 2009 10:17:34 -0400 [thread overview]
Message-ID: <1250518654.2813.458.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Tried forcing hci mode through 2 seperate methods.
[root@scannell ~]# cat /etc/sysconfig/bluetooth
# Enable this to use hid2hci to switch a Bluetooth device in USB HID mode
# to HCI mode for Bluetooth operation.
HID2HCI_ENABLE=true
# Enable this to switch capable devices back to HID mode on Bluetooth shutdown
#HID2HCI_UNDO=true
And also hid2hci:
[root@scannell ~]# lsusb | grep Logitech
Bus 001 Device 028: ID 046d:c70a Logitech, Inc. MX5000 Cordless Desktop
Bus 001 Device 027: ID 046d:c70e Logitech, Inc. MX1000 Bluetooth Laser Mouse
Bus 001 Device 026: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy
mode)
[root@scannell ~]# hid2hci -v 046d -p 0b02 -m logitech
Attempting to switch device 046d:0b02 to HCI mode was successful
However, the device does not actually go into HCI mode:
[root@scannell ~]# lsusb | grep Logitech
Bus 001 Device 028: ID 046d:c70a Logitech, Inc. MX5000 Cordless Desktop
Bus 001 Device 027: ID 046d:c70e Logitech, Inc. MX1000 Bluetooth Laser Mouse
Bus 001 Device 026: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy
mode)
I tried running through gdb, this is the output:
(gdb) run -v 046d -p 0b02 -m logitech
Starting program: /usr/sbin/hid2hci -v 046d -p 0b02 -m logitech
Attempting to switch device 046d:0b02 to HCI mode was successful
Program exited with code 02.
(gdb) thread apply all bt
(gdb) bt
No stack.
(gdb)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2009-08-17 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250518654.2813.458.camel@localhost.localdomain \
--to=aaron@awseibert.net \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox