Walter Lozano authored 4 weeks ago and Dylan Aïssi committed 2 weeks ago

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Walter Lozano authored 4 weeks ago and Dylan Aïssi committed 2 weeks ago

Due to the big amount of contributors in the project, the copyright holder's
list is around 1000 lines causing our scanning tools to hang. To workaround
this issue until a proper fix is found point to an URL to get the full list.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Dylan Aïssi <dylan.aissi@collabora.com>

Martyn Welch authored 6 months ago and Dylan Aïssi committed 6 months ago

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 6 months ago and Dylan Aïssi committed 6 months ago

The RPi support has shifted to bootstd and using a text env, however we
need the older distroboot for our rollback strategy. Revert the config
changes as far as possible that changed the boot methods. The
environment variables that would normally be added to the u-Boot env
when distroboot is enabled won't be as that process requires the env to
be in the include files (rather than stored as a text file). We don't
want to revert all the changes from moving to the text env, so add the
environment variables that were previously added in the defines to the
relevant text env file.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

We are seeing the following issue booting when moving to the v6.8.x
kernel releases:

   Moving Image from 0x80000 to 0x200000, end=2600000
   ## Flattened Device Tree blob at 02600000
      Booting using the fdt blob at 0x2600000
   ERROR: FDT image overlaps OS image (OS=0x200000..0x2600000)

ARM and Aarch64 have different restrictions and trying to accommodate
larger kernels like the ones used in distros can be challenging. For this
reason, separate the layout and rearrange the map for Aarch64 to support
kernels larger than 36 MB.

The current approach is to reserve 128 MB for the kernel to allow boards
with 512 MB to have enough free space for other artifacts, such as
ramdisk.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

When using bootflow, the fallback device tree is being constructed from
the `soc` (`k3`) and `board` (`am62x`) environment variables:

   Retrieving file: /dtbs/6.8.1+/k3-am62x.dtb

This file doesn't exist.

The environment variables `default_device_tree` and
`default_device_tree_arch` are set in the config and will result in
`fdtfile` being set to `ti/k3-am625-sk` when the `findfdt` script is
run, which isn't the case at the moment.

Calling this script results in the correct device tree being retrieved:

   Retrieving file: /dtbs/6.8.1+/ti/k3-am625-sk.dtb

Many boards are calling this script as part of their boot command. The
am62x currently isn't. Rectify this so that booting works correctly.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: mtt2hi <thomas.mittelstaedt@de.bosch.com>

Thomas Mittelstädt authored 1 year ago and Thomas Mittelstädt committed 1 year ago

Packages are created as architecture dependent packages:
amd64: For arm64 and armhf
arm64: For arm64
armhf: For armhf

Signed-off-by: mtt2hi <thomas.mittelstaedt@de.bosch.com>

Base addresses to load kernel and ramdisk image conflict with Optee setup.
So these addresses are moved to a higher address range.

Signed-off-by: mtt2hi <thomas.mittelstaedt@de.bosch.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

The Raspberry Pi environment appears to now be being automatically
escaped, however we are already manually escaping in places that results
in unexpected double escaping and breakage during macro expansion:

[ 1979s] include/generated/environment.h:1:296: error: expected ‘}’ before ‘extlinux’
[ 1979s]     1 | #define CONFIG_EXTRA_ENV_TEXT ...   ...boot_syslinux_conf \\"extlinux/extlinux...
[ 1979s]       |                                                              ^~~~~~~~

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Merge remote-tracking branch 'origin/apertis/v2025dev1' into proposed-updates/debian/trixie/c62abb52

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>