aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708/base-files/lib
Commit message (Collapse)AuthorAgeFilesLines
* brcm2708: rename target to bcm27xxAdrian Schmutzler2020-02-144-142/+0
| | | | | | | | | | | | | | | | | 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>
* brcm2708: add support for Raspberry Pi 2B 1.2Álvaro Fernández Rojas2019-09-191-0/+1
| | | | | | RPi 2B 1.2 has a BCM2710/BCM2837 like RPi 3 devices. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* treewide: use new procd sysupgrade $UPGRADE_BACKUP variableRafał Miłecki2019-09-051-2/+2
| | | | | | | | | | It's a variable set by procd that should replace hardcoded /tmp/sysupgrade.tgz. This change requires the most recent procd with the commit 0f3c136 ("sysupgrade: set UPGRADE_BACKUP env variable"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: when copying a backup file always specify dest nameRafał Miłecki2019-09-051-1/+1
| | | | | | | $CONF_TAR shouldn't be assumed to always point to the sysupgrade.tgz. This change makes code more generic and allows refactoring $CONF_TAR. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: don't hardcode "sysupgrade.tgz" file nameRafał Miłecki2019-09-051-1/+3
| | | | | | | | 1) Add BACKUP_FILE and use it when copying an archive to be restored after sysupgrade (on the next preinit). 2) Use CONF_TAR for copying backup prepared by the /sbin/sysupgrade Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: sysupgrade: pass "save_partitions" option to the "sysupgrade" methodRafał Miłecki2019-08-221-1/+1
| | | | | | | This explicitly lets stage2 know if partitions should be preserved. No more "touch /tmp/sysupgrade.always.overwrite.bootdisk.partmap" hack. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm2708: Add Raspberry Pi 4 supportÁlvaro Fernández Rojas2019-07-141-0/+1
| | | | | | | - Support added to bcm2709 subtarget (32 bit). - 64 bit kernel still requires many hacks on RPi 4B. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* base-files: improve lib/upgrade/common.shKlaus Kudielka2019-05-111-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recently, upgrade device autodetection has been added to the mvebu target. This exposes some shortcomings of the generic export_bootdevice function, e.g. on the Turris Omnia: export_bootdevice silently reports the root partition to be the boot device. This makes the sysupgrade process fail at several places. Fix this by clearly distinguishing between /proc/cmdline arguments which specify the boot disk, and those which specify the root partition. Only in the latter case, strip off the partition, and do it consistently. root=PARTUUID=<pseudo PARTUUID for MBR> (any partition) and root=/dev/* (any partition) are accepted. The root of the problem is that the *existing* export_bootdevice in /lib/upgrade/common.sh behaves differently, if the kernel is booted with root=/dev/..., or if it is booted with root=PARTUUID=... In the former case, it reports back major/minor of the root partition, in the latter case it reports back major/minor of the complete boot disk. Targets, which boot with root=/dev/... *and* use export_bootdevice / export_partdevice, have added workarounds to this behaviour, by specifying *negative* increments to the export_partdevice function. Consequently, those targets have to be adapted to use positive increments, otherwise they are broken by the change to export_bootdevice. Fixes: 4e8345ff68 ("mvebu: base-files: autodetect upgrade device") Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com> Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* brcm2708: fix early bootloader config restoreStijn Tintel2019-02-061-1/+1
| | | | | | | | | Restoring the bootloader config before rebooting fails: tar: invalid tar magic Add the -z option to the tar command to fix this. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: platform.sh: fix tar directory directiveAlexandru Ardelean2018-07-071-1/+1
| | | | | | | | BusyBox's `tar` command does not support the `--directory` directive, which is essentially `-C` in short-form option. BusyBox's `tar` command supports `-C`. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* brcm2708: move wifi calibration EEPROMs out of base-filesDaniel Golle2018-06-143-158/+0
| | | | | | | | Ship EEPROM blobs for specific supported board only and don't have them lurking around in our source tree but rather download them from @github/RPi-Distro/firmware-nonfree upstream. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* brcm2708: add RPi3+ wifi calibration dataDaniel Golle2018-06-142-0/+92
| | | | | | | | Add files from https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.txt https://github.com/RPi-Distro/firmware-nonfree/raw/master/brcm/brcmfmac43455-sdio.clm_blob Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* brcm2708: Add support for raspberry pi 3 b+.Christo Nedev2018-04-271-0/+1
| | | | Signed-off-by: Christo Nedev <christo.nedev@me.com>
* brcm2708: use x86's upgrade scripts for all rpi targetsChristian Lamparter2017-12-251-9/+93
| | | | | | | | | | | | | | | Advantages: - preserves existing partition layout on the sd-card. Only the boot and rootfs partition will be overwritten. Please note that sysupgrade will refuse to upgrade, if the existing installation has an incompatible partition layout. Future changes to the bootfs and/or rootfs partition size will likely cause breakage to the sysupgrade procedure. In these cases, the ext4-sdcard.img.gz will have to be written to the sdcard manually. Please don't forget to backup your configuration in this case. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: convert to dt-based board-detectionChristian Lamparter2017-12-253-57/+5
| | | | | | | | | | | | Use the values populated by the generic board detect function. The first compatible from the device tree source file will be the board name in userspace. The model property from the device tree source file will be the model name. Change the board name where used in the userspace and drop the target specific board detect, to use the generic one. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: convert to metadataChristian Lamparter2017-12-251-15/+2
| | | | | | | | | | This patch converts all the raspberrypi images to utilize the common metadata-based image verification. Note: the CM1 and CM3 currently use the same "rpi-cm" boardname. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm2708: restore /boot/config.txt before rebootStijn Tintel2017-10-232-0/+2
| | | | | | | | | | | | | | The Raspberry Pi bootloader reads configuration values from config.txt in the boot partition. This file allows to specify the amount of memory to assign to the GPU, the license keys for hardware MPEG-2 and VC-1 decoding, Device Tree parameters and overlays, and lots of other things. Since sysupgrade only restores the configuration after booting the newly flashed image, these values will not be active, even if sysupgrade would save /boot/config.txt. To solve this, add the file to the files to be backed up, and restore it in platform_copy_config, before reboot. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* treewide: drop target board_name functionsMathias Kresin2017-07-151-9/+0
| | | | | | They are not used any longer. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: use the generic board_name functionMathias Kresin2017-07-151-3/+3
| | | | | | Use the generic function instead ot the target specific ones. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: populate boardname and model earlierMathias Kresin2017-07-151-0/+0
| | | | | | | | | | | | | For targets using the generic board detection and board specific settings in diag.sh, the board name is still unset at the time the set_state() provided by diag.sh is called by 10_indicate_preinit. Change the execution order to ensure the boardname is populated before required the first time. Do the target specific board detection as early as possible, directly followed by the generic one to allow a seamless switch to the generic function for populating /tmp/sysinfo/. Signed-off-by: Mathias Kresin <dev@kresin.me>
* brcm2708: detect Raspberry Pi Zero WStijn Tintel2017-03-081-0/+3
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: order boards and models alphabeticallyStijn Tintel2017-03-082-13/+15
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcmfmac43430-firmware: remove package and switch to linux-firmwareÁlvaro Fernández Rojas2016-09-291-0/+66
| | | | | | | Now that the firmware for BCM43430 has been submitted to linux-firmware use it and remove RPiDistro package. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: properly detect the Raspberry Pi ZeroÁlvaro Fernández Rojas2016-06-211-0/+3
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: implement sysupgrade image checkChristian Lamparter2016-04-071-1/+15
| | | | | | | | | | Implement a crude but functioning sysupgrade image check for the Raspberry Pi. The code only checks if the master boot record boot signature (0x55aa) is present in the first 512-bytes at the correct location. This can prevent the odd bricking of a system when flashing the wrong file. Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
* brcm2708: add Raspberry Pi 3 supportJohn Crispin2016-03-082-5/+7
| | | | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 48967
* brcm2708: fix RPi model B plus supportFelix Fietkau2016-01-181-0/+1
| | | | | | | | Not sure if B+ is used or not (mine has B Plus) so leave both Signed-off-by: Roman Yeryomin <roman@advem.lv> SVN-Revision: 48311
* brcm2708: add device detection and use it for network, leds and preinitJohn Crispin2015-11-223-0/+69
| | | | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 47572
* brcm2708: keep boot partition mounted to allow users to change config.txtJohn Crispin2015-10-052-6/+7
| | | | | | | | | This way it's easier to configure device tree overlays, customize other parameters... Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 47126
* brcm2708: remove unneeded base-filesJohn Crispin2015-07-172-45/+0
| | | | | | | | Device tree exports board name/model and device LEDs. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 46397
* brcm2708: Implement sysupgradeJohn Crispin2015-07-142-0/+35
| | | | | | | | | | | | | Implement sysupgrade for Raspberry Pi, similar to the way it is done on x86: The config files are saved in the boot partition and moved to where they are normally expected in preinit. Also add optional gzip compression for the SD card image, since this can save a lot of space (76M vs 6M), also similar to x86. Signed-off-by: Bruno Randolf <br1@einfach.org> SVN-Revision: 46347
* brcm2708: add board detection and LED supportJohn Crispin2015-02-142-0/+45
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> SVN-Revision: 44447
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 06:08:06 +0000