From: Jonathan Liu <net147@gmail.com>
To: yocto@yoctoproject.org
Subject: [meta-raspberrypi][PATCH] linux-firmware: Fix "No generic license file exists" warning
Date: Sun, 16 Oct 2016 13:27:39 +1100 [thread overview]
Message-ID: <20161016022739.26984-1-net147@gmail.com> (raw)
The NO_GENERIC_LICENSE map value for Firmware-broadcom_brcm80211 needs
to have the full path to LICENSE.broadcom_brcm80211 from the URL
instead of just the filename.
Fixes the following warning building the linux-firmware recipe:
WARNING: linux-firmware-1_0.0+gitAUTOINC+42ad5367dd-r0 do_populate_lic: linux-firmware: No generic license file exists for: Firmware-broadcom_brcm80211 in any provider
Signed-off-by: Jonathan Liu <net147@gmail.com>
---
recipes-kernel/linux-firmware/linux-firmware_git.bbappend | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
index 20ef05f..b4408cb 100644
--- a/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
+++ b/recipes-kernel/linux-firmware/linux-firmware_git.bbappend
@@ -4,7 +4,7 @@ LICENSE_append = " & Firmware-broadcom_brcm80211"
LIC_FILES_CHKSUM_append = " file://${WORKDIR}/LICENSE.broadcom_brcm80211;md5=8cba1397cda6386db37210439a0da3eb"
-NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = "LICENSE.broadcom_brcm80211"
+NO_GENERIC_LICENSE[Firmware-broadcom_brcm80211] = "${WORKDIR}/LICENSE.broadcom_brcm80211"
SRC_URI_append = " \
file://brcmfmac43430-sdio.bin \
--
2.10.0
next reply other threads:[~2016-10-16 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 2:27 Jonathan Liu [this message]
2016-10-31 16:59 ` [meta-raspberrypi][PATCH] linux-firmware: Fix "No generic license file exists" warning Andrei Gherzan
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=20161016022739.26984-1-net147@gmail.com \
--to=net147@gmail.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.