From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Problem with the i-Tec dongle solved
Date: Thu, 04 Mar 2004 01:47:15 +0100 [thread overview]
Message-ID: <1078361235.2921.12.camel@pegasus> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
Hi Folks,
I got the problematic i-Tec dongle working. The important thing is to
send a HCI_Reset as the first command at initialization. We don't do
this, but I can't remember why not. Maybe there were some problematic
chips in the early times of BlueZ. The attached patch is against 2.6.
And here is the new dongle:
hci0: Type: USB
BD Address: 00:03:C9:xx:xx:xx ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING PSCAN ISCAN
RX bytes:107 acl:0 sco:0 events:14 errors:0
TX bytes:303 acl:0 sco:0 commands:14 errors:0
Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link>
<HV2 packets> <HV3 packets> <u-law log> <A-law log>
<CVSD> <power control> <transparent SCO> <enhanced iscan>
<interlaced iscan> <interlaced pscan> <AFH cap. slave> <AFH cap. master>
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Broadcom BCM2035'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x69 LMP Ver: 1.1 (0x1) LMP Subver: 0xe00
Manufacturer: Broadcom Corporation (15)
The nice thing is that it already supports AFH ;)
Regards
Marcel
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 413 bytes --]
===== net/bluetooth/hci_core.c 1.25 vs edited =====
--- 1.25/net/bluetooth/hci_core.c Thu Feb 26 00:53:38 2004
+++ edited/net/bluetooth/hci_core.c Thu Mar 4 01:06:44 2004
@@ -189,6 +189,9 @@
/* Mandatory initialization */
+ /* Reset */
+ hci_send_cmd(hdev, OGF_HOST_CTL, OCF_RESET, 0, NULL);
+
/* Read Local Supported Features */
hci_send_cmd(hdev, OGF_INFO_PARAM, OCF_READ_LOCAL_FEATURES, 0, NULL);
reply other threads:[~2004-03-04 0:47 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=1078361235.2921.12.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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