From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] rpi-bt-firmware: new package
Date: Mon, 20 Mar 2017 22:42:06 +0100 [thread overview]
Message-ID: <20170320224206.33fa1dbb@free-electrons.com> (raw)
In-Reply-To: <20170320213039.wlpa2tdplbon6f2n@tarshish>
Hello,
On Mon, 20 Mar 2017 23:30:39 +0200, Baruch Siach wrote:
> Do you have any indication that this is indeed the same file that RPi uses? My
> impression was that this firmware is tailored specifically for the RPi board,
> but I don't know for sure. That fact that Broadcom licenses the file may
> indicate that this is the same one. But ...
>
> > 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".
>
> ... this is not the same file:
>
> ls -l bcm43430a1.hcd pi-bluetooth/BCM43430A1.hcd
> -rw-r--r-- 1 baruch baruch 14265 Mar 20 23:22 bcm43430a1.hcd
> -rw-r--r-- 1 baruch baruch 35976 Jan 17 12:25 pi-bluetooth/BCM43430A1.hcd
Gaah, what a mess. Why don't they just post it for integration in the
linux-firmware project? Why is it that RPi people always have to do
things the weird way?
> I have not tested the Variscite firmware on the RPi, though. There is a small
> chance it might damage the hardware.
>
> And since the git repo we use is named 'pi-bluetooth' maybe rpi-bt-firmware is
> not such a bad name after all.
Yeah, indeed :-/
Can you resend the patch with just an extended explanation as to why
the package is named this way, and the fact that even though the
WiFi chip isn't RPi specific, the firmware might be.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-20 21:42 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
2017-03-20 21:30 ` Baruch Siach
2017-03-20 21:42 ` Thomas Petazzoni [this message]
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=20170320224206.33fa1dbb@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