staging/chunkeey/package, branch master

base-files: leds: do reverse lookup in get_dt_led()

2022-05-19T14:39:11Z

In order to match the "label"-less DT properties we have to get creative. In theory the dt-node should have everything (i.e.: color, function and function-enumerator) to make the device-name in /sys/class/leds. But thanks to color being a binary value and not a "string", we would have to maintain a lookup table that keeps in sync with the dt-binding. It's much easier to use the "uevent" property of every led-class device and do reverse lookup with it by comparing the OF_FULLNAME with the alias pathname. (This works with gpio-leds ... let's see where it breaks) Signed-off-by: Christian Lamparter

ath79: add Cisco Meraki MR18

2022-05-19T14:39:11Z

Specifications: SOC: Atheros/Qualcomm QCA9557-AT4A @ 720MHz RAM: 2x Winbond W9751G6KB-25 (128 MiB) FLASH: Hynix H27U1G8F2BTR-BC TSOP48 ONFI NAND (128 MiB) WIFI1: Atheros AR9550 5.0GHz (SoC) WIFI2: Atheros AR9582-AR1A 2.4GHz WIFI2: Atheros AR9582-AR1A 2.4GHz + 5GHz PHYETH: Atheros AR8035-A, 802.3af PoE capable Atheros (1x Gigabit LAN) LED: 1x Power-LED, 1 x RGB Tricolor-LED INPUT: One Reset Button UART: JP1 on PCB (Labeled UART), 3.3v-Level, 115200n8 (VCC, RX, TX, GND - VCC is closest to the boot set jumper under the console pins.) Flashing instructions: Depending on the installed firmware, there fastly different methods to flash a MR18. These have been documented on: Note: upgrades from AR71XX are possible, but require the force sysupgrade option. The LEDs has changed since AR71XX. The white LED is now used during the boot and when upgrading instead of the green tricolor LED. Signed-off-by: Christian Lamparter

lldpd: always depend on libbsd

2022-05-19T14:39:11Z

lldpd calls setproctitle() and strtonum(); its configure.ac script has fallbacks for when they're not found, but they should come from libbsd instead. Signed-off-by: Guilherme Janczak

ipq40xx: add support for Linksys WHW01 v1

2022-05-19T14:39:11Z

This patch adds support for Linksys WHW01 v1 ("Velop") [FCC ID Q87-03331]. Specification ------------- SOC: Qualcomm IPQ4018 WiFi 1: Qualcomm QCA4019 IEEE 802.11b/g/n WiFi 2: Qualcomm QCA4019 IEEE 802.11a/n/ac Bluetooth: Qualcomm CSR8811 (A12U) Ethernet: Qualcomm QCA8072 (2-port) SPI Flash 1: Mactronix MX25L1605D (2MB) SPI Flash 2: Winbond W25M02GV (256MB) DRAM: Nanya NT5CC128M16IP-DI (256MB) LED Controller: NXP PCA963x (I2C) Buttons: Single reset button (GPIO). Notes ----- There does not appear to be a way to trigger TFTP recovery without entering U-Boot. The device must be opened to access the serial console in order to first flash OpenWrt onto a device from factory. The device has automatic recovery backed by a second set of partitions on the larger of the two SPI flash ICs. Both the primary and secondary must be flashed to prevent accidental rollback to "factory" after 3 failed boot attempts. Serial console -------------- A serial console is available on the following pins of the populated J2 connector on the device mainboard (115200 8n1). (<-- Top of PCB / Device) J2 [o o o o o o] | | | | | `-- GND | `---- TX `--------- RX Installation instructions ------------------------- 1. Setup TFTP server with server IP set to 192.168.1.236. 2. Copy compiled `...squashfs-factory.bin` to `nodes-jr.img` in tftp root. 3. Connect to console using pinout detailed in the serial console section. 4. Power on device and press enter when prompted to drop into U-Boot. 5. Flash first partition device via `run flashimg`. 6. Once complete, reset device and allow to power up completely. 7. Once comfortable with device upgrade reboot and drop back into U-Boot. 8. Flash the second partition (recovery) via `run flashimg2`. Revert to "factory" ------------------- 1. Download latest firmware update from vendor support site. 2. Copy extracted `.img` file to `nodes-jr.img` in tftp root. 3. Connect to console using pinout detailed in the serial console section. 4. Power on device and press enter when prompted to drop into U-Boot. 5. Flash first partition device via `run flashimg`. 6. Once complete, reset device and allow to power up completely. 7. Once comfortable with device upgrade reboot and drop back into U-Boot. 8. Flash the second partition (recovery) via `run flashimg2`. Signed-off-by: Peter Adkins (calibration from nvmem, updated to 5.10+5.15) Signed-off-by: Christian Lamparter

ipq-wifi: remove packaged BDF-s for MikroTik devices

2022-05-19T09:07:02Z

Since we now provide the BDF-s for MikroTik IPQ40xx devices on the fly, there is noneed to include package and ship them like we do now. This also resolves the performance issues that happen as MikroTik changes the boards and ships them under the same revision but they actually ship with and require a different BDF. Signed-off-by: Robert Marko

mac80211: ath10k: backport bus and device specific API 1 BDF selection

2022-05-19T09:07:02Z

Some ath10k IPQ40xx devices like the MikroTik hAP ac2 and ac3 require the BDF-s to be extracted from the device storage instead of shipping packaged API 2 BDF-s. This is required as MikroTik has started shipping boards that require BDF-s to be updated, as otherwise their WLAN performance really suffers. This is however impossible as the devices that require this are release under the same revision and its not possible to differentiate them from devices using the older BDF-s. In OpenWrt we are extracting the calibration data during runtime and we are able to extract the BDF-s in the same manner, however we cannot package the BDF-s to API 2 format on the fly and can only use API 1 to provide BDF-s on the fly. This is an issue as the ath10k driver explicitly looks only for the board.bin file and not for something like board-bus-device.bin like it does for pre-cal data. Due to this we have no way of providing correct BDF-s on the fly, so lets extend the ath10k driver to first look for BDF-s in the board-bus-device.bin format, for example: board-ahb-a800000.wifi.bin If that fails, look for the default board file name as defined previously. So, backport the upstream ath10k patch. Signed-off-by: Robert Marko

ath10k-ct: update to 2022-05-13

2022-05-19T09:07:02Z

Update ath10k-ct to the latest version which includes the backported ath10k commit for requesting API 1 BDF-s with a unique name like caldata. Signed-off-by: Robert Marko

bpf-headers: drop HOST_LOADLIBES

2022-05-18T10:32:06Z

HOST_LOADLIBES was renamed to KBUILD_HOSTLDLIBS in kernel 4.19. As the oldest kernel version we support is 5.10, cleanup HOST_LOADLIBES use. Signed-off-by: Stijn Tintel

elfutils: move host build to tools

2022-05-18T10:32:06Z

The upcoming dwarves host package requires elfutils. As dependencies for tools must exist in tools, we need to move elfutils host build there. As there is at least one package that depends on this, and there is no proper way to create such dependency in the build system, build it unconditionally when not building on macOS. Signed-off-by: Stijn Tintel

bcm27xx-gpu-fw: update to latest version

2022-05-17T13:11:22Z

Latest GPU FW contains multiple fixes and improvements. Signed-off-by: Álvaro Fernández Rojas