From: Harvey <harv@gmx.de>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Add support for BCM20702A0 [0489:e031]
Date: Tue, 10 Jan 2012 08:12:11 +0100 [thread overview]
Message-ID: <4F0BE4CB.30907@gmx.de> (raw)
In-Reply-To: <1326137984.6454.152.camel@aeonflux>
Hi all,
>> drivers/bluetooth/btusb.c | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index 55ac349..07622141a 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -101,6 +101,7 @@ static struct usb_device_id btusb_table[] = {
>> { USB_DEVICE(0x0c10, 0x0000) },
>>
>> /* Broadcom BCM20702A0 */
>> + { USB_DEVICE(0x0489, 0xe031) },
>> { USB_DEVICE(0x0a5c, 0x21e3) },
>> { USB_DEVICE(0x413c, 0x8197) },
I fear this alone won't be enough. We are discussing this topic here:
https://bbs.archlinux.org/viewtopic.php?pid=1038521#p1038521
Short summary:
The adapter seems to work in first but the log files say:
'localhost bluetoothd[1718]: Inquiry Failed with status 0x12'
while scanning.
From a short look in the Windows inf. file:
Fujitsu is listed there in a separate section called RAMUSBE031. There
is also this "BCM20702A0_001.001.024.0023.0055.hex" file copied along
with the driver, which is then referenced in the registry as
"RAMPatchFileName". There is a long list of other 20702 adapters divided
in those that need a 'RAM patch' or not. Maybe you could complete your
list of compatible devices bases on this.
I own one of these Fujitsu laptops (E751 0x0489:0xe031) with the need
for the hex file. If you want me to I can do more testing with to your
guidance.
Thanks for your attention
Harvey
next prev parent reply other threads:[~2012-01-10 7:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 11:09 [PATCH] Bluetooth: Add support for BCM20702A0 [0489:e031] Thilo Cestonaro
2012-01-09 19:39 ` Marcel Holtmann
2012-01-10 7:12 ` Harvey [this message]
2012-01-10 8:11 ` Marcel Holtmann
2012-01-10 12:55 ` Harvey
2012-01-10 16:51 ` Marcel Holtmann
2012-01-11 8:15 ` Harvey
2012-01-11 10:35 ` Marcel Holtmann
2012-01-11 10:49 ` Harvey
2012-01-11 10:56 ` Marcel Holtmann
2012-01-11 11:12 ` Harvey
2012-01-14 13:27 ` David Strobach
2012-01-15 10:58 ` Johan Hedberg
2012-01-15 11:21 ` David Strobach
2012-01-11 7:43 ` Thilo Cestonaro
2012-01-11 10:34 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2012-08-27 19:56 thilo
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=4F0BE4CB.30907@gmx.de \
--to=harv@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).