From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] New package: linux-firmware
Date: Thu, 26 Jan 2012 19:58:31 +0100 [thread overview]
Message-ID: <877h0e2svc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1327590802-17503-1-git-send-email-yegorslists@googlemail.com> (yegorslists@googlemail.com's message of "Thu, 26 Jan 2012 16:13:22 +0100")
>>>>> "yegorslists" == yegorslists <yegorslists@googlemail.com> writes:
yegorslists> From: Yegor Yefremov <yegorslists@googlemail.com>
yegorslists> add infrastructure for closed binary blobs
Committed with minor fixes (see below) - Thanks!
yegorslists> new file mode 100644
yegorslists> index 0000000..b4fa645
yegorslists> --- /dev/null
yegorslists> +++ b/package/linux-firmware/Config.in
yegorslists> @@ -0,0 +1,46 @@
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE
yegorslists> + bool "linux-firmware"
yegorslists> + help
yegorslists> + This package provides various binary firmware files
yegorslists> + (closed binary blobs) for such devices like LAN, WLAN cards etc.
Trailing spaces. We normally add an upstream URL here as well. I've
added the link to gitweb for it.
yegorslists> +
yegorslists> +if BR2_PACKAGE_LINUX_FIRMWARE
yegorslists> +
yegorslists> +menu "Devices"
yegorslists> +
yegorslists> +menu "Ralink"
I don't like too many sub menus, so I've dropped the outer "Devices"
one.
yegorslists> +
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT61
yegorslists> + bool "Ralink rt2501/rt61"
yegorslists> + help
yegorslists> + Ralink rt2501/rt61
yegorslists> +
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT73
yegorslists> + bool "Ralink rt73"
yegorslists> + help
yegorslists> + Ralink rt73
yegorslists> +
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT2XX
yegorslists> + bool "Ralink rt27xx/rt28xx/rt30xx"
yegorslists> + help
yegorslists> + Ralink rt27xx/rt28xx/rt30xx
yegorslists> +
yegorslists> +endmenu
yegorslists> +
yegorslists> +menu "Texas Instruments"
yegorslists> +
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE_TI_WL127X
yegorslists> + bool "wl127X"
yegorslists> + help
yegorslists> + Firmware files for WLAN and Bluetooth modules wl1271 and wl1273
yegorslists> +
yegorslists> +config BR2_PACKAGE_LINUX_FIRMWARE_TI_WL128X
yegorslists> + bool "wl128X"
yegorslists> + help
yegorslists> + Firmware files for WLAN and Bluetooth modules wl128x
yegorslists> +
yegorslists> +endmenu
yegorslists> +
yegorslists> +endmenu
yegorslists> +
yegorslists> +endif
yegorslists> diff --git a/package/linux-firmware/linux-firmware.mk b/package/linux-firmware/linux-firmware.mk
yegorslists> new file mode 100644
yegorslists> index 0000000..af48d13
yegorslists> --- /dev/null
yegorslists> +++ b/package/linux-firmware/linux-firmware.mk
yegorslists> @@ -0,0 +1,56 @@
yegorslists> +#############################################################
yegorslists> +#
yegorslists> +# linux-firmware
yegorslists> +#
yegorslists> +#############################################################
yegorslists> +LINUX_FIRMWARE_VERSION = a2995d38c234e3d767df7223d84a0f33a1a24997
yegorslists> +LINUX_FIRMWARE_SITE = git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
yegorslists> +LINUX_FIRMWARE_SITE_METHOD = git
yegorslists> +
yegorslists> +# rt2501/rt61
yegorslists> +LINUX_FIRMWARE_FILES_$(BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT61) += \
yegorslists> + rt2561.bin rt2561s.bin rt2661.bin LICENCE.ralink-firmware.txt
yegorslists> +
yegorslists> +
yegorslists> +# rt73
yegorslists> +LINUX_FIRMWARE_FILES_$(BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT73) += \
yegorslists> + rt73.bin LICENCE.ralink-firmware.txt
yegorslists> +
yegorslists> +# rt2xx
yegorslists> +LINUX_FIRMWARE_FILES_$(BR2_PACKAGE_LINUX_FIRMWARE_RALINK_RT2XX) += \
yegorslists> + rt2860.bin rt2870.bin rt3070.bin rt3071.bin rt3090.bin \
yegorslists> + LICENCE.ralink-firmware.txt
A number of trailing spaces here as well.
Does it make sense to install the license files? We don't otherwise
install other license documentation.
yegorslists> +
yegorslists> +# wl127x
yegorslists> +LINUX_FIRMWARE_FILES_$(BR2_PACKAGE_LINUX_FIRMWARE_TI_WL127X) += \
yegorslists> + ti-connectivity/wl1271-fw-2.bin \
yegorslists> + ti-connectivity/wl1271-fw-ap.bin \
yegorslists> + ti-connectivity/wl1271-fw.bin \
yegorslists> + ti-connectivity/wl1271-nvs.bin \
yegorslists> + ti-connectivity/wl127x-fw-3.bin \
yegorslists> + ti-connectivity/wl127x-fw-plt-3.bin \
yegorslists> + ti-connectivity/wl127x-nvs.bin \
yegorslists> + ti-connectivity/TIInit_7.2.31.bts \
yegorslists> + LICENCE.ti-connectivity
yegorslists> +
yegorslists> +# wl128x
yegorslists> +LINUX_FIRMWARE_FILES_$(BR2_PACKAGE_LINUX_FIRMWARE_TI_WL128X) += \
yegorslists> + ti-connectivity/wl128x-fw-3.bin \
yegorslists> + ti-connectivity/wl128x-fw-ap.bin \
yegorslists> + ti-connectivity/wl128x-fw-plt-3.bin \
yegorslists> + ti-connectivity/wl128x-fw.bin \
yegorslists> + ti-connectivity/wl1271-nvs.bin \
yegorslists> + ti-connectivity/wl128x-nvs.bin \
yegorslists> + ti-connectivity/wl12xx-nvs.bin \
yegorslists> + ti-connectivity/TIInit_7.2.31.bts \
yegorslists> + LICENCE.ti-connectivity
yegorslists> +
yegorslists> +
yegorslists> +define LINUX_FIRMWARE_INSTALL_TARGET_CMDS
yegorslists> + mkdir -p $(TARGET_DIR)/lib/firmware
yegorslists> + for i in $(LINUX_FIRMWARE_FILES_y); do \
yegorslists> + cp -af $(@D)/$$i $(TARGET_DIR)/lib/firmware/$$i; \
yegorslists> + done
yegorslists> +endef
I've changed this to use 2x tar instead.
yegorslists> +
yegorslists> +$(eval $(call GENTARGETS))
yegorslists> --
yegorslists> 1.7.1.1
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-01-26 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:13 [Buildroot] [PATCH v4] New package: linux-firmware yegorslists at googlemail.com
2012-01-26 15:16 ` Yegor Yefremov
2012-01-26 15:23 ` Peter Korsgaard
2012-01-26 15:33 ` Gustavo Zacarias
2012-01-26 15:41 ` Yegor Yefremov
2012-01-26 16:13 ` Peter Korsgaard
2012-01-26 17:02 ` Thomas Petazzoni
2012-01-26 19:15 ` Peter Korsgaard
2012-01-26 18:58 ` Peter Korsgaard [this message]
2012-01-26 20:05 ` Yegor Yefremov
2012-01-26 20:49 ` Michael S. Zick
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=877h0e2svc.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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