From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 100461] No BCM43341 uart support on T100TAF
Date: Wed, 06 Jan 2016 19:54:27 +0000 [thread overview]
Message-ID: <bug-100461-62941-Q3mPOaeMvP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-100461-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=100461
jbMacAZ <jbmacbrodie@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbmacbrodie@yahoo.com
--- Comment #7 from jbMacAZ <jbmacbrodie@yahoo.com> ---
(In reply to Weiwu Zhang from comment #6)
> Hi Luka Karinja - I followed your instruction to have a patched-up kernel
> 4.3.3 and bluez 5.37 and the set of firmwares provided by you. It doesn't
> work for me.
<snip>
> $ sudo btattach --bredr /dev/ttyS4 -P bcm
> Attaching BR/EDR controller to /dev/ttyS4
> Switched line discipline from 0 to 15
> Device index 1 attached
> [not returning to command line]
>
> $ sudo hciconfig
> hci1: Type: BR/EDR Bus: UART
> BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> DOWN
> RX bytes:0 acl:0 sco:0 events:0 errors:0
> TX bytes:9 acl:0 sco:0 commands:2 errors:0
>
> hci0: Type: BR/EDR Bus: SDIO
> BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
> DOWN
> RX bytes:0 acl:0 sco:0 events:0 errors:0
> TX bytes:0 acl:0 sco:0 commands:0 errors:0
>
I had the same result. The solution is to move the BCM4324B.hcd file up 1
folder from /lib/firmware/brcm/ to /lib/firmware/ I don't understand why that
would matter, so YMMV.
The btattach still won't return, but the BD Address from hciconfig is real and
it is possible to pair bt devices. I haven't figured out how to make the
btattach auto connect at boot time, for me it is still manual after each boot.
Like other T100CHI users, I need the device ID patched to include BCM2E71.
Debian kernels seem to use ttyS4, ARCH derivatives use ttyS1.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-01-06 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 9:48 [Bug 100461] New: No BCM43341 uart support on T100TAF bugzilla-daemon
2015-06-25 10:13 ` [Bug 100461] " bugzilla-daemon
2015-12-17 16:20 ` bugzilla-daemon
2015-12-18 8:19 ` bugzilla-daemon
2015-12-23 12:48 ` bugzilla-daemon
2015-12-29 16:04 ` bugzilla-daemon
2016-01-06 6:53 ` bugzilla-daemon
2016-01-06 19:54 ` bugzilla-daemon [this message]
2016-01-09 10:45 ` bugzilla-daemon
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=bug-100461-62941-Q3mPOaeMvP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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