summaryrefslogtreecommitdiffstats
path: root/configs/platform-v7a
Commit message (Collapse)AuthorAgeFilesLines
* tf-a: Change download URLHEADnextmasterAlexander Dahl44 hours1-2/+2
| | | | | | | | | | | Previous URL threw 401 errors. Experiments with other paths from the same server yield no stable tarballs. GitHub tarballs are stable, have a different checksum however. Tarball content was checked to be the same (at least compared to those unstable git snapshot tarballs from the previous URL). GitHub tarball has same checksum as the one downloaded by buildroot. Signed-off-by: Alexander Dahl <ada@thorsis.com>
* v7a: update to OSELAS.Toolchain 2023.07.1Ladislav Michl3 days2-3/+3
| | | | | | | | Use the bugfix toolchain release for v7a builds, and update the kernel config with default options. Signed-off-by: Ladislav Michl <ladis@linux-mips.org> Acked-by: Alexander Dahl <ada@thorsis.com>
* v7a: stm32mp: add image recipe for STM32MP135F-DKAhmad Fatoum4 days4-1/+110
| | | | | | | | | | | | Now, that we have TF-A, OP-TEE, barebox and kernel in-place, let's build an image that combines all of them that can be booted by writing to the SD-Card of the STM32MP135F-DK. Notably missing is Ethernet support as that's not mainline yet. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-13-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: kernel: enable STM32MP135F-DK supportAhmad Fatoum4 days2-2/+8
| | | | | | | | | | | | | | The STM32MP13 shared many kernel config options with the STM32MP15, but it requires some additional options to support SCMI-over-OP-TEE. Enable these options as well as support for OTP-over-OPTEE and rng-over-OPTEE. With the SCMI options enabled, it's possible to boot the STM32MP135F-DK, so enable build of its device tree for inclusion into the image in the follow-up commit. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-12-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: stm32mp: add TF-A recipe for STM32MP13Ahmad Fatoum4 days3-0/+123
| | | | | | | | | | | | | | | | | | | | | We have two ways of doing multi-image builds with TF-A: - STM32MP15-specific: Multiple device trees can be supplied and TF-A is built once and linked with each DT in turn. This was contributed to TF-A for DistroKit purposes, but ST broke the compatibility for STM32MP13, which requires to be built separately. - PTXdist-specific: The PTXdist rule can built multiple platforms in different build directories. This requires however that the options used are the same, except for platform. We unfortunately need to change the option between our two TF-A build though. Therefore, let's duplicate the upstream TF-A rule for the STM32MP13 and configure it for use with OP-TEE. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-11-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: build OP-TEE for STM32MP13Ahmad Fatoum4 days1-1/+6
| | | | | | | | | | | | For the STM32MP13, ST decided that everyone should be using OP-TEE as System Control and Management Interface (SCMI) provider and the kernel driver for the reset and clock control (RCC) peripheral will talk to the SCMI provider. Therefore let's enable OP-TEE, so we can make use of this. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-10-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: enable STM32MP135F-DK supportAhmad Fatoum4 days4-6/+46
| | | | | | | | | | | barebox has had support for the STM32MP135F-DK for a while, but only recently was it extended to support the full shtick of talking to OP-TEE to control clocks and resets. As the barebox version we have in DistroKit supports this, let's enable building support for the development kit. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-9-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: images: stm32mp: use barebox-environment partition type UUIDAhmad Fatoum4 days1-0/+1
| | | | | | | | | Starting with commit 9f868f78bc54 ("environment: use barebox environment from GPT partitions"), barebox can look up its environment by partition type UUID on GPT-partitioned media. To prepare making use of this in the future, ensure that our GPT barebox partition has the correct type UUID. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: barebox: rpi4: fix rpi4 bootstate definitionAhmad Fatoum4 days1-0/+4
| | | | | | | | | Unlike earlier Raspberry Pi variants, the SD-Card the Raspberry Pi 4 boots from isn't handled by the sdhost controller, but by the new emmc2 controller instead. Add an #ifdef to fix barebox state probe. Fixes: 2e0af7e3846c ("v7a: barebox: define state for all supported board variants") Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* v7a: bootstate: remove unused environment partitionsAhmad Fatoum4 days1-10/+2
| | | | | | | | | Both BeagleBone Black and Raspberry Pi boot from a FAT partition containing barebox. barebox will use same FAT partition for storage of its environment, so the specified raw partition remains unused and can be dropped. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
* platform-v7a: kernel: enable ARM optimized SHA1 implementationRobert Schwebel2024-03-181-3/+3
| | | | | | | On v7a with NEON, we want to have the NEON optimized SHA1 implementation. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: version bump v2024.01.0 → v2024.03.0Ahmad Fatoum2024-03-1717-156/+139
| | | | | | | | | | | | The latest barebox release incorporates the single patch we had on top of v2024.01.0, so let's drop it by updating. Config changes are those of olddefconfig with the exception of CONFIG_CMD_PARTED. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-8-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: update kernel from v6.6 → v6.8Ahmad Fatoum2024-03-172-39/+84
| | | | | | | | Like done for v8a, also update the v7a kernel to the latest release. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-7-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* tf-a: update from v2.8 → v2.10Ahmad Fatoum2024-03-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | This lets us git rid of a fair number of patches we have, but in return requires us to import three patches: - Fix link error for imx8mq-evk: The image got too big with addition of DRAM retention support, so this is now disabled by default: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/27277 - Support for automatic console base detection on i.MX8MQ. This was already in our patch stack, but wasn't submitted upstream, unlike the support for i.MX8MM, i.MX8MN and i.MXP. This has been rectified: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/27278 - STM32MP1 support with SP_min as BL31 instead of OP-TEE is broken since v2.10 was first released. This is due to PMU changes that were apparently only tested on ARMv8. Fixed here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/27162 Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-3-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: migrate 2024.02.0 → 2024.03.0Ahmad Fatoum2024-03-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | This lets us make use of the updated OP-TEE packages for the incoming STM32MP13 support. Support in OP-TEE 3.20 is incomplete and will lead to a crash on boot up: I/TC: Platform stm32mp1: flavor 135F_DK - DT stm32mp135f-dk.dts I/TC: Non-secure SYSRAM [0xddfff000 0xddffffff] I/TC: DTB enables console (non-secure) I/TC: Primary CPU switching to normal world boot E/TC:0 tzc_it_handler:26 TZC permission failure E/TC:0 dump_fail_filter:420 Permission violation on filter 0 E/TC:0 dump_fail_filter:425 Violation @0xfcff7fe0, non-secure privileged write, AXI ID 420 E/TC:0 Panic at core/arch/arm/plat-stm32mp1/plat_tzc400.c:30 <tzc_it_handler> E/TC:0 TEE load address @ 0xde000000 E/TC:0 Call stack: E/TC:0 0xde00316d E/TC:0 0xde011b37 E/TC:0 0xde005245 E/TC:0 0xde011201 E/TC:0 0xde037155 E/TC:0 0xde000350 Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240315211240.3016716-2-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: imx6: don't enable fastboot net by defaultAhmad Fatoum2024-03-111-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The idea behind enabling the USB gadget by default was to allow quick experimentation with only a USB connection by exposing both fastboot and a ACM serial gadget. However, Fastboot over UDP, isn't as useful: - the user first has to find out the IP address assigned to the board - getting a DHCP lease on every boot takes a bit of time - The shell is unusable until the DHCP request succeeds or times out. Ctrl+C can't be used as it's not called interactively Therefore, disable Fastboot over UDP and leave only USB enabled by default. User wishing to use Fastboot over UDP can just set nv.fastboot.net.autostart=1 manually to restore the old behavior. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240306184640.628394-1-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform: v7a: barebox: Enable FIT image supportAlexander Dahl2024-03-1113-20/+48
| | | | | | | | | Already enabled for v8a. Tested on Beaglebone Black and RIoTboard. Signed-off-by: Alexander Dahl <ada@thorsis.com> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240306092530.1448784-4-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform: v7a: barebox: Upgrade from 2023.12.0 to 2024.01.0Alexander Dahl2024-03-1117-23/+222
| | | | | | | | | | The latest and greatest. Has the nice support for 'noload' sub-images in FIT images conforming for spec. Signed-off-by: Alexander Dahl <ada@thorsis.com> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240306092530.1448784-2-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: migrate 2023.12.0 -> 2024.02.0Roland Hieber2024-03-111-12/+10
| | | | | | | | | | | | Update to the new PTXdist version with default options. Note that HOST_DTC, HOST_FLEX and HOST_M4 only vanish from the platformconfigs and are still enabled in ptxconfig. Remove our systemd patch, which is now included in systemd 255.2. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20240219121717.3507053-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: update barebox to v2023.09.0 -> v2023.12.0Ahmad Fatoum2024-01-2618-191/+172
| | | | | | | | | | | | | | | | | | | This lets us drop two patches that fixed issues with v2023.09.0. This update also enables some options that are useful for the hardware we support: - on STM32MP1, support for the NAND controller is enabled - on STM32MP1, we enable HWRNG and stack protector support The latter could be enabled universally for all platforms that are no size constrained, but it prints an ugly error message if there's no HWRNG as using the fixed fallback canary is insecure. We'll just postpone enabling stack protector on other platforms until we enable HWRNG support there. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20240112170529.1970537-5-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.10.0 -> 2023.12.0DistroKit-2023.12.0Robert Schwebel2023-12-131-2/+3
| | | | | | Let's update to the latest and greatest. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: images: stm32mp: generate eMMC boot partition image as wellAhmad Fatoum2023-12-131-0/+19
| | | | | | | | | | | The DistroKit image is capable of booting both from SD-Card and eMMC user area. For boot from eMMC boot partition, we can keep reusing the same image for the user area, but need to place the boot firmware into the boot partition as well. Add an extra image that does just that. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20231213165014.1279779-2-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: stm32mp: tf-a: enable boot from eMMC boot partitionAhmad Fatoum2023-12-131-1/+1
| | | | | | | | | | | By default, TF-A located on eMMC boot partition will only boot FIP from eMMC user area. Toggle STM32MP_EMMC_BOOT, so FIP image is first looked for at offset 256K on the eMMC boot partition, before booting from GPT partition in user area. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.pengutronix.de/20231213165014.1279779-1-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: define state for all supported board variantsAhmad Fatoum2023-12-131-4/+9
| | | | | | | | | | | Boot up is broken on some of the Raspberry Pi and STM32MP1 board we support, because boot method is changed to bootchooser, but state isn't defined. Fix this by extending state definition to the missed boards. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Reviewed-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231205095929.3469672-2-a.fatoum@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox-stm32mp1: pass root=PARTUUID=… to kernelRoland Hieber2023-12-132-1/+2
| | | | | | | | | | | | | | This partly reverts commit e0ca556db7983a99acc3330dc32cdae395e84003. As Ahmad reports, the kernel device tree of STM32MP157C-EV1 has no aliases at all, which is a precondition for enabling MMCBLKDEV_ROOTARG in barebox. Restore the old state which detects the PARTUUID of the root partition and passes it to the kernel. Link: https://lore.distrokit.org/distrokit/9afb1d8a-f90d-7d74-781d-c33f6b7a2efb@pengutronix.de Fixes: e0ca556db7983a99acc3 (2023-10-20, "v7a: barebox: pass root=mmcblkXpN instead of root=PARTUUID=… to kernel") Reported-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
* v7a: barebox: bootchooser: use GPT partition labelsRoland Hieber2023-12-138-8/+8
| | | | | | | | | | | | Now that every image is in GPT format, we can use the devnodes that include the partition label instead of the partition number to boot our rootfs. These names are more readable and also more robust against changing the order of the partitions. Make the change on all bareboxes that didn't have that yet. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-11-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* treewide: images: remove root-B and data partitionsRoland Hieber2023-12-139-49/+0
| | | | | | | | | | | These partitions are now generated on the first boot by systemd-repart. The second rootfs is not needed for booting, and overwritten by RAUC when a bundle is installed, so it can as well be empty. Remove the two partitions to save space in the generated images. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-9-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* treewide: images: increase size of all qemu images to 1 GiBRoland Hieber2023-11-061-1/+1
| | | | | | | | | | | | qemu sets the size of the emulated disk as the size of the underlying image file. We want to fit two rootfs partitions and one data partition of 200 MiB each in there, which will need at least 600 MiB of disk space. Round up to the next power of two, so qemu can work with it, which results in 1 GiB, which the other qemu images already have too. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-5-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* treewide: images: remove size specifications for root partitionsRoland Hieber2023-11-061-1/+0
| | | | | | | | | | | | With current rootfs sizes of below 200 MiB there is no need to have a 512 MiB root partition, which will be a lot larger than the file system it contains, and which will also all have to be written to the SD card. Let genimage determine the partition size based on the file system image it contains, thereby reducing the size of the generated disk images. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-4-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: image-stm32mp: set GPT Partition Type UUIDRoland Hieber2023-11-061-0/+1
| | | | | | | | | This was forgotten in commit 1022b05b735f6081cf1b. Fixes: 1022b05b735f6081cf1b (2023-10-20, "images: convert to GPT format") Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-3-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* treewide: images: unify partition labelsRoland Hieber2023-11-064-4/+4
| | | | | | | | | | | The partition label is written to the GPT, and systemd-repart can match on the partition label, which we'll use in a later commit. Set the name of the first root partitions to the same name ("root-A") to give the matching algorithm something to work with. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231103225253.1349209-2-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: build the RAUC update bundle tooRoland Hieber2023-11-021-1/+11
| | | | | | | | | | | | | RAUC support for a lot of v7a platforms has been available for some time now (see e.g. commits 559e482a643e to 8e204806f616, b869997d64ee5, 5f00115de864), but building the RAUC bundle that is actually needed to update the targets has somehow slipped through. Enable the image, and put something useful in the bundle description. Reported-by: Bastian Krause <bst@pengutronix.de> Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231102095229.3096032-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: kernel: version bump 6.5 -> 6.6Robert Schwebel2023-10-302-18/+39
| | | | Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: add upstream patches for stm32mpRobert Schwebel2023-10-213-0/+166
| | | | | | | | | | Currently we get this new error: ERROR: stm32-rproc 10000000.m4@10000000.of: failed to get tz syscfg Apply upstream patches from the mailing list. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a/v8a: kernel: enable hardlockup detectorRobert Schwebel2023-10-211-1/+6
| | | | | | | Enable the hard lockup detector and panic on trigger. An embedded system has probably nothing better to do than to reboot if the kernel locks up. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* platform-v7a: kernel: version bump 6.4 -> 6.5Robert Schwebel2023-10-214-14/+30
| | | | | | | The devicetrees in mainline have changed their location, adapt our devicetree paths and the includes accordingly. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* images: convert to GPT formatRoland Hieber2023-10-2010-31/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GUID Partition Table format has several advantages over the legacy MBR format. Especially when we want to make use of systemd-repart functionality later, the GPT format is a necessity. Therefore, migrate all images to the GPT format. For some platforms (Raspberry Pi, AM355x, AT91), we still need a legacy MBR partition table so that the ROM code can find a bootable partition (which contains our barebox image). For those cases, transform the image into a hybrid format containing an MBR at offset 0, which contains the VFAT boot partition for the ROM loader, and a protective GPT partition of partition type 0xEE after it to claim the remaining space on the storage medium for GPT purposes. Then a GPT header is added at the default GPT offset of 0x200, which defines the boot partition as well as the root partition, and which is read by Barebox and Linux to boot the system. For images that contain a raw barebox image at a fixed offset outside of a GPT partition, make sure that the GPT does not conflict with the barebox image, and write only the primary GPT header into the hole specified by the barebox image (offset 440 to 1K), but move the GPT partition array to an offset behind the barebox image. (genimage will then also offset the following partitions accordingly.) Remove any 'disk-signature' options, which are not compatible with GPT; genimage will generate a random Disk UUID instead. Also remove any 'partition-type' options, and set the respective partition type GUIDs specified by the Discoverable Partitions Specification [1], or let genimage default to the 'linux-generic' partition type. For the rpi1 image-hdimg, overwrite the upstream hd.config with a hardcoded genimage config file since it is not possible to build a hybrid MBR/GPT image with the image recipe from upstream PTXdist. For the v7a image-hdimg, enable GPT support in the platformconfig menu, and re-add the respective config lines from the upstream version of the config file in order to make GPT work. The images with fixed partition sizes for qemu need to stay below the size specified in the 'size' option, so decrease the size of the last partition further to make space for the secondary GPT header, which will reside in the last block of the image. Link: [1] https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-6-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* images: remove qemu size hackRoland Hieber2023-10-202-20/+7
| | | | | | | | | | | | | | | | | | | genimage knows about the 'size' option for images to fill the image to a certain size, and since genimage v14 it supports the 'fill' option to write all zeroes at the end of the image and not cut them off to optimise the image size. Use this to blow up the images that are used with qemu to the next power of two so qemu can work with them, and remove our invisible-partition-at-the-end hack. Since the first MiB (when using 1 MiB alignment) is occupied by the partition table, and the first partition only starts at offset 1 MiB, the data partition now no longer fits into the available space. Set it to 'autoresize' so that genimage computes the size to fill the remaining space in the image. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-5-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: enable GUID Partition Table supportRoland Hieber2023-10-2011-17/+26
| | | | | | | | | We want to be able to boot from devices formatted with GPT, enable this on the platforms that don't have it yet. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-4-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: pass root=mmcblkXpN instead of root=PARTUUID=… to kernelRoland Hieber2023-10-2013-13/+13
| | | | | | | | | | | | | | | | | | | | Kernels prior to v5.10-rc1 could not ensure deterministic ordering for MMC devices. For this reason, the default 'append-root' behaviour of barebox for MMC block devices is to append a 'root=PARTUUID=XYZ' option to the kernel command line. The PARTUUID is derived from the partition table and is expected to be unique system-wide. This is however susceptible to breakage if the exact same image is written to different boot media in the system, e.g. SD and eMMC, so the PARTUUID will no longer uniquely refer to a single partition. Newer kernel versions honor the numbering used for 'mmc' aliases, which makes 'root=mmcblkXpN' deterministic as long as barebox and kernel aliases are identical. Since we're using kernel 6.4, enable this option in barebox. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-3-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* images: use 'partition-table-type' option instead of 'partition-table'Roland Hieber2023-10-201-1/+1
| | | | | | | | | genimage v16 complains that 'partition-table = false' is deprecated in favour of 'partition-table-type = none'. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-2-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: image-stm32mp: use 'partition-table-type' option instead of 'gpt'Roland Hieber2023-10-201-1/+1
| | | | | | | | | The 'gpt' option in genimage has been deprecated in favour of 'partition-table-type = gpt'. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/20231020090519.3320460-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: version bump 2023.09.0 -> 2023.10.0Robert Schwebel2023-10-201-2/+2
| | | | | | A new ptxdist version is out, update. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* qemu-run: don't evaluate selected_platformconfigRoland Hieber2023-10-201-7/+2
| | | | | | | | | | | | | | Even when a selected_platformconfig symlink exists, ptxdist can still be used with the --platformconfig=... option to override the platformconfig during the build. In this case, running the qemu script will search in the wrong build folder for the images. Don't use the selected_platformconfig link to find out the platform, instead determine it from the path of the qemu script itself. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/distrokit/20231010091028.3444582-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: add RAUC support for lxa-mc1Roland Hieber2023-10-206-2/+32
| | | | | | | | | | | | * 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> Link: https://lore.pengutronix.de/distrokit/20230926092713.3680509-5-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox-common: enable bootchooserRoland Hieber2023-10-2010-17/+13
| | | | | | | | | Bootchooser will choose the correct redundant A/B partition for booting. Enable it in the common barebox so it is available on all v7a boards. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/distrokit/20230926092713.3680509-4-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: enable of_compatible and of_fixup commandsRoland Hieber2023-10-2013-20/+20
| | | | | | | | Enable two useful commands for debugging. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/distrokit/20230926092713.3680509-3-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: barebox: version bump 2023.02.1 -> 2023.09.0Roland Hieber2023-10-2015-227/+356
| | | | | | | | | | | | Update to v2023.09.0, which includes auto-detection for barebox-state partitions in GPT, which will come in handy for the LXA MC-1 board. For AM335X, selecting OMAP_MULTI is now necessary, otherwise do an oldconfig with default options. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/distrokit/20230926092713.3680509-2-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* ptxdist: migrate 2023.08.0 -> 2023.09.0Roland Hieber2023-10-201-2/+2
| | | | | | | | The usual version bump with default settings. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.pengutronix.de/distrokit/20230915150707.3977805-1-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
* v7a: run: start with barebox by defaultDistroKit-2023.09.0Roland Hieber2023-09-151-1/+1
| | | | | | | | | | | | | | Booting via 9p results in a machine that feeld very differently than any other boards in platform-v7a, mainly because there is no data partition, no barebox-state, and therefore no RAUC support. All of this is possible by booting from the emulated SD card image through barebox. Default to barebox so that qemu-vexpress feels as much as possible like booting from other boards. Signed-off-by: Roland Hieber <rhi@pengutronix.de> Link: https://lore.barebox.org/20230825110310.2948272-8-rhi@pengutronix.de Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-26 09:24:33 +0000