From: Kris Bahnsen via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Eugen Hristev <eugen.hristev@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Mark Featherston <mark@embeddedTS.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Kris Bahnsen <kris@embeddedTS.com>
Subject: [Buildroot] [PATCH 1/4] package/wilc1000-firmware: bump to 15.6
Date: Thu, 24 Mar 2022 13:20:23 -0700 [thread overview]
Message-ID: <20220324202026.5688-2-kris@embeddedTS.com> (raw)
In-Reply-To: <20220324202026.5688-1-kris@embeddedTS.com>
Supports both WILC1000 (Wi-Fi only) and WILC3000 (Wi-Fi/BLE) hardware
To support WILC3000 this commit adds a separate config option,
the original config option from this package is still valid.
Signed-off-by: Kris Bahnsen <kris@embeddedTS.com>
---
package/wilc1000-firmware/Config.in | 27 +++++++++++++++++++++--
package/wilc1000-firmware/wilc1000-firmware.hash | 2 +-
package/wilc1000-firmware/wilc1000-firmware.mk | 28 ++++++++++++++++--------
3 files changed, 45 insertions(+), 12 deletions(-)
diff --git a/package/wilc1000-firmware/Config.in b/package/wilc1000-firmware/Config.in
index df8a7a6b60..0734c7ad99 100644
--- a/package/wilc1000-firmware/Config.in
+++ b/package/wilc1000-firmware/Config.in
@@ -1,6 +1,29 @@
config BR2_PACKAGE_WILC1000_FIRMWARE
bool "wilc1000-firmware"
help
- Firmware for Atmel Wilc1000 wireless device
+ Firmware for Microchip WILC1000 wireless device
- https://github.com/linux4sc/wireless-firmware.git
+ These binary blobs are provided directly from Microchip.
+ Ideally, the firmware version should match driver version.
+ Generally, the latest firmware would be acceptible regardless
+ of driver version.
+
+ These will be installed to /lib/firmware/mchp/
+
+ https://github.com/linux4wilc/firmware
+
+if BR2_PACKAGE_WILC1000_FIRMWARE
+config BR2_PACKAGE_WILC3000_FIRMWARE
+ bool "wilc3000-firmware"
+ help
+ Firmware for Microchip WILC3000 wireless device
+
+ These binary blobs are provided directly from Microchip.
+ Ideally, the firmware version should match driver version.
+ Generally, the latest firmware would be acceptible regardless
+ of driver version.
+
+ These will be installed to /lib/firmware/mchp/
+
+ https://github.com/linux4wilc/firmware
+endif
diff --git a/package/wilc1000-firmware/wilc1000-firmware.hash b/package/wilc1000-firmware/wilc1000-firmware.hash
index 5344efe517..9d55be9edc 100644
--- a/package/wilc1000-firmware/wilc1000-firmware.hash
+++ b/package/wilc1000-firmware/wilc1000-firmware.hash
@@ -1,2 +1,2 @@
# Locally calculated
-sha256 a2e7a327dd545ba2051946f7613005cbde88fdd952afb8eecdd1dacda7e767d2 v14.1_Firmware.zip
+sha256 29bb5739136cdb4088cb52af59badce05cc7e562bca40e9f29fef7f8f7c19cb8 wilc1000-firmware-wilc_linux_15_6.tar.gz
diff --git a/package/wilc1000-firmware/wilc1000-firmware.mk b/package/wilc1000-firmware/wilc1000-firmware.mk
index 6f504d67a0..2bea9febe2 100644
--- a/package/wilc1000-firmware/wilc1000-firmware.mk
+++ b/package/wilc1000-firmware/wilc1000-firmware.mk
@@ -4,21 +4,31 @@
#
################################################################################
-WILC1000_FIRMWARE_VERSION = 14.1
-WILC1000_FIRMWARE_SITE = https://github.com/linux4sc/wireless-firmware/archive
-WILC1000_FIRMWARE_SOURCE = v$(WILC1000_FIRMWARE_VERSION)_Firmware.zip
+WILC1000_FIRMWARE_VERSION = wilc_linux_15_6
+WILC1000_FIRMWARE_SITE = $(call github,linux4wilc,firmware,$(WILC1000_FIRMWARE_VERSION))
WILC1000_FIRMWARE_LICENSE = PROPRIETARY
-define WILC1000_FIRMWARE_EXTRACT_CMDS
- $(UNZIP) -d $(BUILD_DIR) $(WILC1000_FIRMWARE_DL_DIR)/$(WILC1000_FIRMWARE_SOURCE)
- mv $(BUILD_DIR)/wireless-firmware-$(WILC1000_FIRMWARE_VERSION)_Firmware/* $(@D)
- rmdir $(BUILD_DIR)/wireless-firmware-$(WILC1000_FIRMWARE_VERSION)_Firmware
+ifeq ($(BR2_PACKAGE_WILC1000_FIRMWARE),y)
+WILC1000_FIRMWARE_FILES += \
+ wilc1000_wifi_firmware.bin
+endif
+
+ifeq ($(BR2_PACKAGE_WILC3000_FIRMWARE),y)
+WILC1000_FIRMWARE_FILES += \
+ wilc3000_ble_firmware.bin \
+ wilc3000_wifi_firmware.bin
+endif
+
+define WILC1000_FIRMWARE_INSTALL_FILES
+ cd $(@D) && \
+ $(TAR) cf install.tar $(sort $(WILC1000_FIRMWARE_FILES)) && \
+ $(TAR) xf install.tar -C $(TARGET_DIR)/lib/firmware/mchp
endef
define WILC1000_FIRMWARE_INSTALL_TARGET_CMDS
- $(INSTALL) -D -m 0644 $(@D)/wilc1003_firmware.bin \
- $(TARGET_DIR)/lib/firmware/atmel/wilc1003_firmware.bin
+ $(INSTALL) -d -m 0755 $(TARGET_DIR)/lib/firmware/mchp/
+ $(WILC1000_FIRMWARE_INSTALL_FILES)
endef
$(eval $(generic-package))
--
2.11.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-03-24 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 20:20 [Buildroot] [PATCH 0/4] Pull in WILC Wi-Fi updates Kris Bahnsen via buildroot
2022-03-24 20:20 ` Kris Bahnsen via buildroot [this message]
2022-03-24 20:20 ` [Buildroot] [PATCH 2/4] package/wilc-firmware: rename from wilc1000-firmware Kris Bahnsen via buildroot
2022-03-24 20:20 ` [Buildroot] [PATCH 3/4] configs: add WILC3000_FIRMWARE to compatible devices Kris Bahnsen via buildroot
2022-03-24 20:20 ` [Buildroot] [PATCH 4/4] package/wilc-driver: new package Kris Bahnsen via buildroot
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=20220324202026.5688-2-kris@embeddedTS.com \
--to=buildroot@buildroot.org \
--cc=eugen.hristev@microchip.com \
--cc=kris@embeddedTS.com \
--cc=ludovic.desroches@microchip.com \
--cc=mark@embeddedTS.com \
--cc=thomas.petazzoni@bootlin.com \
/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