From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 4/6] package/rpi-bt-firmware: bump version to d4f7087
Date: Sun, 29 Mar 2020 19:37:19 +0200 [thread overview]
Message-ID: <20200329173719.GN22325@scaer> (raw)
In-Reply-To: <20200329132535.4811-4-ps.report@gmx.net>
Peter, All,
On 2020-03-29 15:25 +0200, Peter Seiderer spake thusly:
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/rpi-bt-firmware/rpi-bt-firmware.hash | 4 ++--
> package/rpi-bt-firmware/rpi-bt-firmware.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/rpi-bt-firmware/rpi-bt-firmware.hash b/package/rpi-bt-firmware/rpi-bt-firmware.hash
> index a3c7281d75..6e88552544 100644
> --- a/package/rpi-bt-firmware/rpi-bt-firmware.hash
> +++ b/package/rpi-bt-firmware/rpi-bt-firmware.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> -sha256 51a33d23127300dffd6ac088f372b83ab862053f5e4dc7130676ebaaa824e626 rpi-bt-firmware-688531da4bcf802a814d9cb0c8b6d62e3b8a3327.tar.gz
> -sha256 b16056fc91b82a0e3e8de8f86c2dac98201aa9dc3cbd33e8d38f1b087fcec30d LICENCE.broadcom_bcm43xx
> +sha256 05db087504be2f6bc1d902cca605114c7f9d458be0adb3b8026369357a329f7a rpi-bt-firmware-d4f7087ecbc8eff9cb64a4650765697157821d64.tar.gz
> +sha256 b16056fc91b82a0e3e8de8f86c2dac98201aa9dc3cbd33e8d38f1b087fcec30d LICENCE.broadcom_bcm43xx
> diff --git a/package/rpi-bt-firmware/rpi-bt-firmware.mk b/package/rpi-bt-firmware/rpi-bt-firmware.mk
> index 23923453c4..785f007cc3 100644
> --- a/package/rpi-bt-firmware/rpi-bt-firmware.mk
> +++ b/package/rpi-bt-firmware/rpi-bt-firmware.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -RPI_BT_FIRMWARE_VERSION = 688531da4bcf802a814d9cb0c8b6d62e3b8a3327
> +RPI_BT_FIRMWARE_VERSION = d4f7087ecbc8eff9cb64a4650765697157821d64
> RPI_BT_FIRMWARE_SITE = $(call github,LibreELEC,brcmfmac_sdio-firmware-rpi,$(RPI_BT_FIRMWARE_VERSION))
Any reason why rpi-bt-firmware and rpi-wifi-firmware are two different
packages, rather than a single one with an option for each of bt and
wifi?
(yes I know that in the past, they had different upstreams, but now
they've been merged into yet a third upstream, it would have made sense
to mnerge them too...)
Yet, as I said to the first patch in the series: applied to master,
thanks!
Regards,
Yann E. MORIN.
> RPI_BT_FIRMWARE_LICENSE = PROPRIETARY
> RPI_BT_FIRMWARE_LICENSE_FILES = LICENCE.broadcom_bcm43xx
> --
> 2.26.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-03-29 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 13:25 [Buildroot] [PATCH v1 1/6] configs/raspberrypi*: bump kernel version to 4f2a4cc Peter Seiderer
2020-03-29 13:25 ` [Buildroot] [PATCH v1 2/6] package/rpi-userland: bump version to 6fb5973 Peter Seiderer
2020-03-29 13:25 ` [Buildroot] [PATCH v1 3/6] package/rpi-firmware: bump version to 5574077 Peter Seiderer
2020-03-29 13:25 ` [Buildroot] [PATCH v1 4/6] package/rpi-bt-firmware: bump version to d4f7087 Peter Seiderer
2020-03-29 17:37 ` Yann E. MORIN [this message]
2020-03-29 13:25 ` [Buildroot] [PATCH v1 5/6] package/rpi-wifi-firmware: " Peter Seiderer
2020-03-29 13:25 ` [Buildroot] [PATCH v1 6/6] package/localedef: fix gcc-10.0.1 compile Peter Seiderer
2020-03-29 13:51 ` Peter Seiderer
2020-03-29 17:34 ` [Buildroot] [PATCH v1 1/6] configs/raspberrypi*: bump kernel version to 4f2a4cc Yann E. MORIN
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=20200329173719.GN22325@scaer \
--to=yann.morin.1998@free.fr \
--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