| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
Let's update to the latest and greatest.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
A new ptxdist version is out, update.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
We have an issue with ptxdist-2023.07.0, so we continue with .1.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
| |
A new ptxdist version is out, so we can update.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
| |
Enable CRYPTO_SHA256_ARM on ARM with NEON extensions (suggested by
reason).
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
- 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>
|
|
|
|
|
|
| |
A new kernel is out, so we update.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
| |
A new ptxdist version is out, update the configs.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
It has been a while but here is a version bump.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
| |
Some new ptxdist versions are out, so we bump to 2023.02.0.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
A new ptxdist version is out, so we can migrate.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|