From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 98021] Broadcom 43341 sdio bluetooth module is not recognized.
Date: Thu, 16 Jun 2016 15:21:11 +0000 [thread overview]
Message-ID: <bug-98021-62941-PmuRkm3p74@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-98021-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=98021
--- Comment #4 from Francesco Bonanno <mibofra@frozenbox.org> ---
Hello, after some time I have started to work again with the my asus t200ta. I
have the bluetooth module working now!
https://github.com/LGSInnovations/edison-yocto-image/raw/master/edison-image-edison-ext4/etc/firmware/bcm43341.hcd
this is the firmware used to get it working (I've originally unpacked it from
the intel edison image, anyway I have found this repository where it is pushed
already, so you can take the firmware here for tests)
After I have discovered that the bcm43341 (at least on my t200ta and with linux
4.7rc3) is seen as a bcm43341B0 on /dev/ttyS4
[ 1251.074780] Bluetooth: hci1: BCM: chip id 82
[ 1251.074792] Bluetooth: hci1: BCM43341B0 (002.001.014) build 0000
So I have put the firmware under /lib/firmware/brcm/BCM43341B0.hcd where
btattach is looking for it and after I have launched it with:
"btattach --bredr /dev/ttyS4 -P bcm" as root, and it is working without issues!
I have put the command under /etc/rc.local as workaround, however I imagine
that you will find a better solution to have it recognised automatically by the
kernel.
I hope all this will be usefull!
--
You are receiving this mail because:
You are the assignee for the bug.
parent reply other threads:[~2016-06-16 15:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-98021-62941@https.bugzilla.kernel.org/>]
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-98021-62941-PmuRkm3p74@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;
as well as URLs for NNTP newsgroup(s).