summaryrefslogtreecommitdiffstats
path: root/configs/platform-v7a
Commit message (Collapse)AuthorAgeFilesLines
...
* rauc: add initial supportRoland Hieber2023-09-151-1/+24
| | | | | | | | | | | | | | | | Set up RAUC with a shared system.conf that uses the /dev symlinks which the rauc-udev package creates based on the Device Tree compatible. Also add a unit file that marks the booted partition as good after systemd startup has finished successfully. The key material for signing the RAUC bundles is provided by the ptx-code-signing provider used for development, which is a build dependency of RAUC. Since we can enable RAUC in the ptxconfig for all platforms, all platforms also need a code signing provider. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.barebox.org/20230825110310.2948272-3-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: enable loading kernel, dtb and initrd via fastbootJuergen Borleis2023-09-159-2/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | This change is similar to: 2732f93bcf4ee011cecca3518aec7e523c311d7a "v8a: barebox: enable loading kernel, dtb and initrd via fastboot" but for some of the v7a platforms. Due to the absence of a common environment it only can be added for the i.MX6 based systems for now. This change prepares all v7a platforms to load kernel, dtb and initrd as sparse images to RAM-files for rapid development. It exposes mmc{1,2,3} as 'fastboot' partitions and add init script to force barebox to detect these devices and have them available for 'fastboot'. It autostarts the USB gadget and network capability to use 'fastboot' out of the box. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Link: https://lore.barebox.org/20230825111056.32801-1-jbe@pengutronix.de Adapted bsp.ref for v7a, similar to v8a. Inspired-by: Roland Hieber <rhi@pengutronix.de> Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: silence reason-warning for barebox state dtb entryRobert Schwebel2023-08-164-6/+6
| | | | | | | | | | | | | As the 'reason' checker analyzes all <*>.dtb files in the imagedir and assumes they are all kernel dtbs, rename the barebox dtb from barebox-*.dtb to *.dtb-bb. This silences a warning that kernel devicetrees should not contain barebox,state nodes. For a similar fix, see commit d16f98c910e20ee5a29da6ca0636b0fbad14f1b2. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: update to OSELAS.Toolchain 2023.07Roland Hieber2023-08-152-7/+8
| | | | | | | | | Use the new toolchain release for v7a builds, and update the kernel config with default options. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.barebox.org/20230813192846.1210986-6-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: migrate 2023.07.1 -> 2023.08.0Roland Hieber2023-08-151-2/+2
| | | | | | | | Migrate to the new PTXdist release with default options. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.barebox.org/20230813192846.1210986-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: kernel: enable features necessary for RAUCRoland Hieber2023-08-151-4/+64
| | | | | | | | | | | | | | | Enable the following kernel features: * ARM SHA256 acceleration (CRYPTO_SHA256_ARM) * Device mapper support (MD, BLK_DEV_DM) * Verity target support (DM_VERITY), needed for the verity bundle format * squashfs file system (MISC_FILESYSTEMS, SQUASHFS*, XZ_DEC_*, LZ4_*), also having multiple compression algorithms enabled for squashfs makes it easy to change the compression of the RAUC bundle in the future * Network block device support (BLK_DEV_NBD), needed for HTTPS streaming Signed-off-by: Roland Hieber <rhi@pengutronix.de> Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: add RAUC support for riotboardRoland Hieber2023-08-1510-4/+45
| | | | | | | | | | | * Enable barebox bootchooser framework * Add a redundant root partition to the genimage config * Add appropriate variables to the barebox defaultenv so the bootchooser can decide into which partition to boot * Add a state backend to the device tree fragment * Map partitions in rauc-udev compatibility layer Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: add RAUC support for rpi3Roland Hieber2023-08-1510-4/+51
| | | | | | | | | | | | | * Enable barebox bootchooser framework * Add a redundant root partition to the genimage config. The state and environment partitions can live in the first 4 MiB of the SD card, so move the the boot partition by the same amount. * Add appropriate variables to the barebox defaultenv so the bootchooser can decide into which partition to boot * Add a state backend to the device tree fragment * Map partitions in rauc-udev compatibility layer Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: add RAUC support for beaglebone blackRoland Hieber2023-08-1510-3/+56
| | | | | | | | | | | * Enable barebox bootchooser framework * Add a redundant root partition to the genimage config * Add appropriate variables to the barebox defaultenv so the bootchooser can decide into which partition to boot * Add a state backend to the device tree fragment * Map partitions in rauc-udev compatibility layer Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: add RAUC support for qemu-vexpressRoland Hieber2023-08-159-3/+16
| | | | | | | | | | | | | * Enable barebox bootchooser framework * Add a redundant root partition to the genimage config. The current size of the rootfs is below 98 MiB, so we can add a second root partition to the image while keeping the overall image size the same. * Add appropriate variables to the barebox defaultenv so the bootchooser can decide into which partition to boot * Use the already existing bootstate in the upstream barebox Device Tree * Map partitions in rauc-udev compatibility layer Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: barebox: include generic bootstate node in device treeRoland Hieber2023-08-1514-13/+63
| | | | | | | | | Add a device tree fragment via CONFIG_EXTERNAL_DTS_FRAGMENTS in the barebox config, which is appended to each device tree built by barebox. Then add definitions for the state variables, which are the same on all boards; board-specific state backends will be added in the next patches. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* platforms: revert to default systemd loglevelRoland Hieber2023-08-157-7/+7
| | | | | | | | | | | | | | | | | | By decreasing the systemd loglevel to "warning", the journal no longer contains useful lines like which units were started and stopped and when, which is quite sparse information for debugging. Remove the systemd.log_level from the kernel command line so systemd defaults to loglevel "info" (same level as loglevel=5 for the kernel). Keep the systemd.show_status setting on "auto" so that systemd only produces actual console output when the boot takes a significant amount of time, or produces error messages; so this change only changes the verbosity of the journal, not the console, on normal boots. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.barebox.org/20230623124755.2292833-2-rhi@pengutronix.de [remove meanwile eliminated special environment for rock3a, see 8ed4f77e790a24bd8c0d4fb15f95731eb1490be6 for reference] Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: rpi2: Restore finding rpi-firmware when used as base layerAlexander Dahl2023-08-151-1/+1
| | | | | | | | | | | | | | | When DistroKit was used as a base layer, the firmware was not in '$(PTXDIST_WORKSPACE)/rpi-firmware' but in '$(PTXDIST_WORKSPACE)/base/rpi-firmware' or '$(PTXDIST_WORKSPACE)/base/base/rpi-firmware' … so we just need to look for it in all layers. Otherwise no firmware is put to the FAT partition of the SD card image and the device does not boot at all. Fixes: 4dbcbb498769 ("v7a: rpi2: move rpi-firmware directory to top-level workspace") Signed-off-by: Alexander Dahl <ada@thorsis.com> Reviewed-by: Michael Olbrich <m.olbrich@pengutronix.de> Link: https://lore.barebox.org/20230630120847.3271567-1-ada@thorsis.com Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.06.0 -> 2023.07.1Robert Schwebel2023-07-101-2/+3
| | | | | | We have an issue with ptxdist-2023.07.0, so we continue with .1. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.05.0 -> 2023.06.0Robert Schwebel2023-06-301-2/+2
| | | | | | A new ptxdist version is out, so we can update. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* kernel: version bump 6.3 -> 6.4DistroKit-2023.06.0Robert Schwebel2023-06-292-14/+35
| | | | | | | Enable CRYPTO_SHA256_ARM on ARM with NEON extensions (suggested by reason). Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* Toolchain: version bump 2022.10.0 -> 2022.10.1Robert Schwebel2023-06-292-3/+3
| | | | | | | With Debian Bookworm, OSELAS.Toolchain-2022.10.0 doesn't work any more, switch to 2022.10.1, which has the issues being fixed. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platforms: drop no longer needed blspec-rpi4Ahmad Fatoum2023-05-311-1/+0
| | | | | | | | | | | | Now that we have commits: - 552ea42fe7aa ("v8a: blspec: switch to default blspec entry") - b7a4fe185852 ("v7a: blspec: convert to ptxdist default entries") we don't need special dedicated blspec rules anymore for v7a/v8a, so drop the last one we had left. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* dtc: Version bump 1.6.0 -> 1.7.0Uwe Kleine-König2023-05-301-2/+2
| | | | | | | | | | | | | | | | | | | | | | This fixes a FTBFS with gcc 12 gcc -I libfdt -I . -DFDT_ASSUME_MASK=0 -DNO_VALGRIND -g -Os -fPIC -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls -Wshadow -DNO_YAML -o fdtoverlay.o -c fdtoverlay.c In file included from fdtdump.c:14: In function 'fdt_set_magic', inlined from 'main' at fdtdump.c:220:3: libfdt/libfdt.h:251:28: error: array subscript 'struct fdt_header[0]' is partly outside array bounds of 'unsigned char[4]' [-Werror=array-bounds] 251 | fdth->name = cpu_to_fdt32(val); \ | ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~ libfdt/libfdt.h:253:1: note: in expansion of macro 'fdt_set_hdr_' 253 | fdt_set_hdr_(magic); | ^~~~~~~~~~~~ fdtdump.c: In function 'main': fdtdump.c:216:31: note: object 'smagic' of size 4 216 | unsigned char smagic[FDT_MAGIC_SIZE]; | ^~~~~~ cc1: all warnings being treated as errors Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
* ptxdist: version bump 2023.04.0 -> 2023.05.0Michael Olbrich2023-05-081-2/+3
| | | | | | | | | - all changes in rules/at91bootstrap2.make and rules/host-qemu.make are now upstream. - update configs/platform-mipsel/rules/host-qemu.make to the latest version from upstream. It still has local changes for mips. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
* arch: bootloader: enable 'fastboot' support over USB and networkJuergen Borleis2023-05-0813-46/+68
| | | | | | | | | | | | | Enabling: - CONFIG_BOOTM_INITRD = y - CONFIG_USB_GADGET = y - CONFIG_USB_GADGET_FASTBOOT = y - CONFIG_NET_FASTBOOT = y - CONFIG_FASTBOOT_SPARSE = y - CONFIG_FASTBOOT_CMD_OEM = y Signed-off-by: Jürgen Borleis <jbe@pengutronix.de>
* linux: version bump 6.2 -> 6.3Robert Schwebel2023-04-242-35/+32
| | | | | | A new kernel is out, so we update. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: wifx-l1: drop fixed partitions node from kernel DTAhmad Fatoum2023-04-181-26/+0
| | | | | | | | | | Bootloader will fix up its own partition description into the kernel device tree, so the description in the kernel DT serves no purpose and is at worst confusing. Drop it. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230418121126.2124891-1-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: add Wifx L1 SD-Card imageAhmad Fatoum2023-04-183-0/+49
| | | | | | | | | | | | The Wifx L1 is a SAMA5D4-based LoRaWAN gateway. This commit adds first support for booting DistroKit on it from SD-Card. Default boot medium is NAND, but a bootable SD-Card always has precedence over NAND. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230417131141.908678-6-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: kernel: extend support to SAMA5D4-based Wifx L1Ahmad Fatoum2023-04-183-7/+424
| | | | | | | | | | | | | Let's import the barebox device tree into the BSP for use by Linux. This allows us to update it separately in the future. The kernel was so far configured for SAMA5D2 only, so enable whatever else is needed for the SAMA5D4. While we boot from SD for now, main boot medium is meant to be NAND. We thus enable the NAND driver and UBIFS. Driver support is there, but we have yet to integrate boot from NAND into the BSP. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230417131141.908678-5-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: extend support to SAMA5D4-based Wifx L1Ahmad Fatoum2023-04-183-12/+89
| | | | | | | | | Support for booting the Wifx L1 from SD-Card is upstream in barebox since v2023.02.0. We have 2023.02.1, so let's enable it. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230417131141.908678-4-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: at91bootstrap: configure v4.0.6-rc1 for Wifx L1Ahmad Fatoum2023-04-182-1/+305
| | | | | | | | | | | | We will use AT91Bootstrap as first stage bootloader for the Wifx L1 for now, so let's add a suitable config file. We import v4.0.6-rc1 as that's the first tag that contains commit 41cd6c4 ("crt0_gnu.S: always pass along r4 to next stage"), which is required for later boot firmware to determine what the initial boot medium was. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230417131141.908678-3-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.03.0 -> 2023.04.0Robert Schwebel2023-04-081-2/+2
| | | | Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.02.0 -> 2023.03.0Robert Schwebel2023-03-281-2/+2
| | | | | | A new ptxdist version is out, update the configs. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: version bump v2022.09.0 → v2023.02.1Ahmad Fatoum2023-03-2719-200/+90
| | | | | | | | | | | | | | | | Our patches for optionally working around flaky SD-Card detect are now upstream, so let's update to the newest release and drop them from our side. Config is what resulted from oldconfig with the exception of: - CONFIG_DRIVER_NET_BCMGENET, which is now enabled to give resulting barebox-raspberry-pi.img Ethernet support when running on the rpi 4-b. - CONFIG_CMD_FCB, which adds a useful fcb command for debugging boot from NAND on i.MX SoCs. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20230307114541.3179101-1-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: kernel: version bump 5.17 -> 6.2Robert Schwebel2023-02-202-154/+283
| | | | | | It has been a while but here is a version bump. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2022.12.0 -> 2023.02.0Robert Schwebel2023-02-161-2/+3
| | | | | | Some new ptxdist versions are out, so we bump to 2023.02.0. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: blspec: convert to ptxdist default entriesMarco Felsch2023-02-1149-770/+5
| | | | | | | | | | | | | | | | | | Adding new board support always included adding a special blspec package for this new board. Most of the blspec entries are the same except for the used devicetree blob. Since the blspec-entry package is able to the add the barebox 'linux-appendroot true' option as well can move to the buildin blspec-entry creation. This lowers the burden of adding new board support since ptxdist will create a blspec entry for devicetree each listed within the platformconfig. I added the 'rootwait rw' kernel command line options since most blspec entries used these options, albeit the 'rw' support should be reconsidered. Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.pengutronix.de/20230210193612.2143905-15-m.felsch@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: vexpress: remove console from blspec configMarco Felsch2023-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The console setup and linux command line passing is now done within barebox: | commit 319e387dbf72c7aea4b5159af9a43b5399c6431b | Author: Lucas Stach <dev@lynxeye.de> | Date: Sun Aug 16 23:42:40 2020 +0200 | | ARM: vexpress: set stdout path | | This ensures that the correct console gets activated independent | of the device probe order. | | Signed-off-by: Lucas Stach <dev@lynxeye.de> | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> The commit is part of mainline barebox since version v2020.09.0, so drop the console option. Drop the rootfstype as well while on it since the kernel will do an autodetection. Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.pengutronix.de/20230210193612.2143905-14-m.felsch@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: blspec: drop incomplete Gute Fee supportMarco Felsch2023-02-113-12/+0
| | | | | | | | | | The blspec support for the Gute Fee HW was incomplete since the actual makefile is missing as well as the devicetree, so drop the blspec boot support. Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.pengutronix.de/20230210193612.2143905-13-m.felsch@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: tf-a: version bump v2.7 -> 2.8/customers/pengutronix/distrokit/20230210-1Marco Felsch2023-02-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Do mainline version bump v2.7 -> v2.8 Drop upstreamed patch: - 0001-fix-stm32mp1-fdts-stm32mp1-align-DDR-regulators-with.patch Squash patches: - 0003-feat-build-add-support-for-new-binutils-versions.patch - 0004-makefile-link-with-z-noexecstack.patch Added patches: - i.MX8MQ PIE support - i.MX8MQ GCC-12 build fixes Finally make use of umpf [1] for the patchstack management. [1] https://github.com/pengutronix/umpf/pull/10 Signed-off-by: Marco Felsch <m.felsch@pengutronix.de> Link: https://lore.pengutronix.de/20230210193612.2143905-2-m.felsch@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* blspec-rpi4: move menu file to platforms/Michael Olbrich2023-01-061-5/+0
| | | | | | | | | | | | | | | | | The rule file is toplevel in rules/ so without this "ptxdist lint" reports for all other platforms: [...] Checking kconfig symbols in rule files ... Undefined symbol PTXCONF_BLSPEC_RPI4 used in 'DistroKit/rules/blspec-rpi4.make'. [...] Add some dependencies so it can only be selected on platforms where it makes sense and disable it on v8a for now. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Link: https://lore.pengutronix.de/20230106113946.1775158-1-m.olbrich@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2022.11.0 -> 2022.12.0Robert Schwebel2022-12-031-2/+2
| | | | | | A new ptxdist version is out, so we can migrate. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* toolchain: version bump 2020.08 -> 2022.10Robert Schwebel2022-11-282-10/+15
| | | | | | | Now that OSELAS.Toolchain-2022.10, with gcc-12.2.1 and glibc-2.36 is out, move to the new toolchain. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* tf-a: move patches out of platformRobert Schwebel2022-11-252-106/+0
| | | | | | | | | With new binutils, we need a non-platform specific patch for tf-a that handles executable stacks correctly. As platform specific patches in ptxdist should only be used for patches that break other platforms anyway, move the patches to the normal patches directory. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: stm32mp: enable serial and mass storage gadget driversJan Luebbe2022-11-232-4/+2
| | | | | | They are enabled in the common config and we don't want to disable them there. Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
* ptxdist: migrate to 2022.11.0Roland Hieber2022-11-231-3/+4
| | | | | | | | | Migrate all platforms to the new release with default options. util-linux-ng has been replaced by util-linux, and the options are sorted differently, but there is no change in enabled options. Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: barebox: enable of_diff commandAhmad Fatoum2022-10-0212-13/+12
| | | | | | | | | | The of_diff command shows a diff over the fixups barebox would do to the device tree when booting and is very useful to see at a glance, things like fixed up bootsource or memory size. Enable it for all v7a boards. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-11-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: rpi4: place DT into /boot for VideoCore consumptionAhmad Fatoum2022-10-021-0/+1
| | | | | | | | | | | | | | | | This is a somewhat ugly hack. The VideoCore will pass this device tree to barebox, which doesn't care much for it. As a side effect of the device tree passing, the VideoCore parses the device tree and will detect that the mini-uart is enabled and take care not to scale clock rate on the VideoCore, which the mini-uart is sourced from as that would upset the baudrate. There may be some config.txt entry we can use to avoid this, but for now, just place the device tree into the boot partition. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-10-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: rpi4: add boot loader spec supportAhmad Fatoum2022-10-022-0/+6
| | | | | | | | | | | We now build device trees and have a kernel capable of booting on the Raspberry Pi 4b, so generate bootloader spec entries as well. We add an entry for the Raspberry Pi 400 as well. This is untested, but isn't costly to enable. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-9-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: dts: build Raspberry Pi 4 device treesAhmad Fatoum2022-10-021-1/+1
| | | | | | | | | We'll want to be able to boot the v7a image on Raspberry Pi 4 in 32-bit mode as well, so enable the device trees. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-8-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: kernel: configure for 32-bit Raspberry Pi 4 supportAhmad Fatoum2022-10-021-8/+13
| | | | | | | | | | We already support the Raspberry Pi 3 with our v7a kernel configuration, flip a few more options to get the kernel running on a Raspberry Pi 4 in A32 mode as well. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-7-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* barebox: deploy new barebox-raspberry-pi.imgAhmad Fatoum2022-10-022-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | The generic barebox-dt-2nd.img mimics Linux and allows booting barebox with an external device tree as if it were a kernel. We employ this for using the same image for Rpi 2 and 3 by placing barebox device trees into the FAT boot partition and having the VideoCore pass the correct device tree to barebox. While this works, it means the VideoCore won't patch the kernel device tree, but many users depend on the VideoCore to apply overlays for kernel consumption. While this could be done in barebox instead, it doesn't have the familiar config.txt interface and it doesn't cover some of the more obscure magic the videocore does: e.g. when applying an overlay configuring the USBOTG, the VideCore will reconfigure clocks as a side effect of applying the overlay. For this reason, barebox now also has a barebox-raspberry-pi.img that behaves the same as barebox-dt-2nd.img with the difference that it has the multiple device trees built-in. It's already being generated since updating to the new release, so let's make use of this. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-6-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: rpi2: move rpi-firmware directory to top-level workspaceAhmad Fatoum2022-09-3012-37/+1
| | | | | | | | | | The Raspberry Pi 3 we already support can be operated in 64-bit mode as well as the not-yet-supported Raspberry Pi 4. Instead of duplicating the Raspberry Pi Firmware for both platforms, move it to a central location. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-4-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: switch to new broken-cd device parameterAhmad Fatoum2022-09-3023-124/+186
| | | | | | | | | | | The original patch didn't go upstream, because semantics were a bit odd, a Kconfig option changing behavior, but only for devices barebox probes. This imports v3 of the series into DistroKit. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20220930162159.814389-3-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-25 17:45:32 +0000