From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Missing firmware files
Date: Mon, 24 Nov 2014 09:04:43 -0700 [thread overview]
Message-ID: <5473571B.9080702@mlbassoc.com> (raw)
I have a .bbappend which I use to add some non-public firmware
files to linux-firmware. This set up used to work, but today
I'm getting only empty packages. Here's my .bbappend fragment
#---------------------------------------------------------------------------------------
# Wi2Wi (based on Marvell SDIO 86xx devices
#
LICENSE_${PN}-wi2wi = "Firmware:LICENCE.Wi2Wi_firmware.txt"
PROVIDES += " linux-firmware-wi2wi "
SRC_URI += " \
http://www.not-public.com/Wi2Wi-firmware.tgz;name=Wi2Wi-firmware \
"
SRC_URI[Wi2Wi-firmware.md5sum] = "2b400aee75e7522eb7f9a299aaa6d023"
SRC_URI[Wi2Wi-firmware.sha256sum] = "33b08d06169074e3d680df20f057580bbc5aa3aaa07e8ba3744c9318d0cbba5d"
do_install_append() {
cd ${S}
install -d ${D}/lib/firmware/
# Wi2Wi via libertas
install -m 0666 ${WORKDIR}/sd8688.bin ${D}/lib/firmware
install -m 0666 ${WORKDIR}/sd8688_helper.bin ${D}/lib/firmware
install -m 0666 ${WORKDIR}/LICENCE.Wi2Wi_firmware.txt ${D}/lib/firmware/
}
PACKAGES += "${PN}-wi2wi"
FILES_${PN}-wi2wi = "/lib/firmware/sd86*.bin /lib/firmware/LICENCE.Wi2Wi_firmware.txt"
RPROVIDES_${PN}-wi2wi = "${PN}-wi2wi"
The desired files do end up in my install image, but not in the
split package linux-firmware-wi2wi
Any ideas what I'm missing in the packaging that is ending up with
empty packages?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2014-11-24 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 16:04 Gary Thomas [this message]
2014-11-24 16:52 ` Missing firmware files Paul Eggleton
2014-11-24 17:33 ` Gary Thomas
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=5473571B.9080702@mlbassoc.com \
--to=gary@mlbassoc.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.