From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rpi-bt-firmware: new package
Date: Sun, 19 Mar 2017 22:00:43 +0100 [thread overview]
Message-ID: <20170319220043.6f819196@free-electrons.com> (raw)
In-Reply-To: <094f74654295373c7cadd47044cbcfb9a80d8c87.1489093234.git.baruch@tkos.co.il>
Hello,
On Thu, 9 Mar 2017 23:00:34 +0200, Baruch Siach wrote:
> Add firmware file for the Raspberry Pi 3 Bluetooth module.
>
> Note that to successfully download the firmware bluez5_utils needs a patch[1].
>
> [1] http://www.spinics.net/lists/linux-bluetooth/msg69470.html
Wonderful patch :)
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
I think the name of the package is wrong, it shouldn't be
rpi-bt-firmware. Indeed, it has nothing to do with the RPi itself, but
with the WiFi chip. And other boards, such as
http://www.armadeus.org/wiki/index.php?title=OPOS6UL, use a WiFi chip
that need the same firmware. See
http://www.armadeus.org/wiki/index.php?title=Bluetooth#OPOS6UL where
they tell to use exactly that BCM43430A1.hcd firmware.
So perhaps the package should be bcrm-43430-firmware or something along
those lines.
> +RPI_BT_FIRMWARE_VERSION = a439f892bf549ddfefa9ba7ad1999cc515f233bf
> +RPI_BT_FIRMWARE_SITE = https://aur.archlinux.org/pi-bluetooth.git
Is there a better upstream than this? I found
https://github.com/varigit/bcm_4343w_fw but I'm not sure it really
qualifies as "better".
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-19 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 21:00 [Buildroot] [PATCH] rpi-bt-firmware: new package Baruch Siach
2017-03-19 21:00 ` Thomas Petazzoni [this message]
2017-03-20 21:30 ` Baruch Siach
2017-03-20 21:42 ` Thomas Petazzoni
2017-03-21 5:41 ` Baruch Siach
-- strict thread matches above, loose matches on Subject: below --
2017-02-01 13:23 Baruch Siach
2017-03-07 10:34 ` Martin Bark
2017-03-08 7:17 ` Baruch Siach
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=20170319220043.6f819196@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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