From: Marcel Holtmann <marcel@holtmann.org>
To: Lu Ran <hephooey@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: New Broadcom chip in W510
Date: Tue, 05 Oct 2010 11:30:48 +0200 [thread overview]
Message-ID: <1286271048.17473.66.camel@aeonflux> (raw)
In-Reply-To: <201009190926.51131.hephooey@gmail.com>
Hi Lu,
> I am having trouble to make my headset work in my new W510, it works fine in an
> T61, with has almost identical software and setup with the new W510. The only
> difference is I am now using a pure 64 bit system, while the old T61 is a 32
> bit one, and the bluetooth chip is different. the id of the chip in T61 is
> 0A5C:2110, while W510 has a chip from Broadcom with id 0A5C:217F. I noticed
> there is a SCO fix for 0A5C:2110 in btusb.c. I tried to copy the line and
> change the id to 0A5C:217F, but nothing changes. The headset can pair with the
> laptop with no problem, but there seems to be no data transmition. And I get a
> lot error messages in dmesg output like this:
>
> btusb_submit_isoc_urb: hci0 urb ffff880060136e00 submission failed (28)
>
> and
>
> btusb_send_frame: hci0 urb ffff8801320e1a00 submission failed
>
> the output of "hciconfig hci0 version" is
>
> hci0: Type: BR/EDR Bus: USB
> BD Address: 70:F3:95:34:2F:29 ACL MTU: 1021:8 SCO MTU: 64:8
> HCI Version: 2.1 (0x4) Revision: 0x168
> LMP Version: 2.1 (0x4) Subversion: 0x4203
> Manufacturer: Broadcom Corporation (15)
>
> And the output of "lsusb -v" is in the attachment. I will try to provide any
> other information you need to analyse the problem.
can you show me the content of /proc/bus/usb/devices (or usbdevices.sh)
for that device.
Regards
Marcel
next prev parent reply other threads:[~2010-10-05 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 13:26 New Broadcom chip in W510 Lu Ran
2010-10-05 9:30 ` Marcel Holtmann [this message]
2010-10-05 11:54 ` Lu Ran
2010-10-05 12:13 ` Marcel Holtmann
2010-11-19 6:08 ` Lu Ran
-- strict thread matches above, loose matches on Subject: below --
2010-10-05 12:59 Lu Ran
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=1286271048.17473.66.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=hephooey@gmail.com \
--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