aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm27xx/base-files
Commit message (Collapse)AuthorAgeFilesLines
* bcm27xx: add support for Raspberry Pi Zero 2Stijn Tintel2022-07-012-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to licensing uncertainty, we do not include the firmwares for the wireless chips used in the Raspberry Pi Zero 2 W. To have working wireless, follow the instructions below. For people building their own images: mkdir -p files/lib/firmware/brcm wget -P files/lib/firmware/brcm/ https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436-sdio.bin wget -P files/lib/firmware/brcm/ https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436-sdio.txt wget -P files/lib/firmware/brcm/ https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436s-sdio.bin wget -P files/lib/firmware/brcm/ https://github.com/RPi-Distro/firmware-nonfree/raw/bullseye/debian/config/brcm80211/brcm/brcmfmac43436s-sdio.txt Now build the OpenWrt image as usual, and it will include the firmware files in the correct location. For people using ext4 images: Write the ext4 image to the sdcard, then mount the 2nd partition and put the firmware files from the links above in /lib/firmware/brcm relative from the mount point where the partition is mounted. For people using squashfs images: Write the squashfs image to the sdcard, place it in the Raspberry Pi Zero 2 W, boot it and wait for the overlay filesystem to be created. Find the offset of the overlay filesystem in sysfs: # cat /sys/devices/virtual/block/loop0/loop/offset 25755648 Shut down the device, unplug the power and move the SD card to a Linux computer. Mount the 2nd partition of the sdcard as a loop device with the offset found earlier. sudo mount /dev/sdh2 -o loop,offset=25755648 /mnt/temp Put the firmware files from the links above in /upper/lib/firmware/brcm relative to the mount point where the loop device is mounted. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Tested-by: Peter van Dijk <peter@7bits.nl>
* bcm27xx: base-files: align network filesÁlvaro Fernández Rojas2022-05-192-4/+6
| | | | | | | | - Use the same order for /etc/board.d/02_network and /lib/preinit/05_set_preinit_iface_brcm2708. - Add missing RPi 400 and CM4 to /lib/preinit/05_set_preinit_iface_brcm2708. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: diag.sh: fix whitespaceÁlvaro Fernández Rojas2022-05-191-1/+1
| | | | | | No idea how this ended up here... Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* treewide: remove execute bit and shebang from board.d filesAdrian Schmutzler2021-03-061-1/+0
| | | | | | | | | | | | | | | | So far, board.d files were having execute bit set and contained a shebang. However, they are just sourced in board_detect, with an apparantly unnecessary check for execute permission beforehand. Replace this check by one for existance and make the board.d files "normal" files, as would be expected in /etc anyway. Note: This removes an apparantly unused '#!/bin/sh /etc/rc.common' in target/linux/bcm47xx/base-files/etc/board.d/01_network Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm27xx: add diag LEDsÁlvaro Fernández Rojas2021-02-191-0/+7
| | | | | | | We can now use the power LED for diag in more devices thanks to the latest patches from the RPi foundation. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: add support for RPI CM4 and RPI 400Álvaro Fernández Rojas2021-02-181-0/+2
| | | | | | Support added to bcm2709 (32 bits) and bcm2711 (64 bits). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* treewide: drop shebang from non-executable target filesAdrian Schmutzler2020-06-162-2/+0
| | | | | | | | | | | | | | This drops the shebang from all target files for /lib and /etc/uci-defaults folders, as these are sourced and the shebang is useless. While at it, fix the executable flag on a few of these files. This does not touch ar71xx, as this target is just used for backporting now and applying cosmetic changes would just complicate things. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm27xx: fix unmounting /boot after sysupgradeStijn Tintel2020-06-071-1/+1
| | | | | | | | Due to a typo, /boot is not properly unmounted after copying the backup file to it. Fix the typo to solve this. Fixes: 246916ddf4a1 ("brcm2708: use x86's upgrade scripts for all rpi targets") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm27xx: backup /boot/cmdline.txt and restore earlyStijn Tintel2020-05-032-1/+2
| | | | | | | | | | | | If you want to use the Raspberry Pi UART, "console=serial0,115200" needs to be removed from the kernel cmdline. This is done by editing /boot/cmdline.txt. However, this file is not currently backed up during sysupgrade, so this effectively breaks HATs that require the use of the UART every sysupgrade. Backup this file during sysupgrade, and restore it before rebooting. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: rename target to bcm27xxAdrian Schmutzler2020-02-147-0/+213
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Despite, since subtargets range from bcm2708 to bcm2711, it seems appropriate to use bcm27xx instead of bcm2708 (again, as already done for BOARDNAME). This also renames the packages brcm2708-userland and brcm2708-gpu-fw. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>