u-boot.git/tools/docker, branch v2025.10

Docker, CI: Update to latest Ubuntu and Dockerfile

2025-07-25T19:03:01+00:00

- Update to Ubuntu "Jammy" 20250714 tag
- Update to current Dockerfile which brings us QEMU 10.0.2 and newer
  coreboot and pulls in lz4 via the non-legacy package name.

Signed-off-by: Tom Rini

CI: Update to coreboot 25.03

2025-07-25T16:55:40+00:00

At this point there's problems rebuilding coreboot-24.08 without manual
intervention. Let us upgrade to a newer version.

Signed-off-by: Tom Rini

Dockerfile: Update to QEMU 10.0.2

2025-07-25T16:55:40+00:00

As QEMU 10.0.2 is the current release, update to that so that we can
update other features within CI.

Signed-off-by: Tom Rini

Dockerfile: use lz4 instead of lz4-tools

2025-05-09T21:08:09+00:00

Since Ubuntu Jammy lz4-tools is only a virtual package which pulls in
lz4 as dependency.

Update documentation too.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Tom Rini

Docker, CI: Add vexpress_fvp / vexpress_fvp_bloblist support

2025-04-29T17:40:40+00:00

This adds the vexpress_fvp and vexpress_fvp_bloblist platforms to the
list of platforms we test via emulator in CI. In order to do this we
need to first have our container runtime have TF-A builds for the
vexpress_fvp platform, both with and without transfer list support as
well as installing "telnet" so that we can access console. In the CI
files we check for the existence of /opt/tf-a/${TEST_PY_BD} and if
found, copy bl1.bin and fip.bin to /tmp and set the variables so that we
can later run FVP to run.

Note that we currently disable the hostfs (semihosting) tests as they
trigger a bug in FVP. This has been reported upstream, and can be
enabled when fixed.

Reviewed-by: Harrison Mutai 
Acked-by: Ilias Apalodimas 
Signed-off-by: Tom Rini

python: Use and refer to the venv module rather than virtualenv

2025-04-24T21:37:27+00:00

Using some form of sandbox with Python modules is a long standing best
practice with the language. There are a number of ways to have a Python
sandbox be created. At this point in time, it seems the Python community
is moving towards using the "venv" module provided with Python rather
than a separate tool. To match that we make the following changes:

- Refer to a "Python sandbox" rather than virtualenv in comments, etc.
- Install the python3-venv module in our container and not virtualenv.
- In our CI files, invoke "python -m venv" rather than "virtualenv".
- In documentation, tell users to install python3-venv and not
  virtualenv.

Signed-off-by: Tom Rini

CI: Move to latest container images

2025-04-10T17:06:50+00:00

- Bump up "Jammy" tag to jammy-20250404
- Include most recent changes to the Dockerfile itself

Signed-off-by: Tom Rini

Dockerfile: Add fdisk

2025-04-10T17:06:50+00:00

We had previously gotten this package through a chain of dependencies
with guestfs-tools. Now that we no longer install that package, install
fdisk (for sfdisk) directly.

Fixes: eb1b90ec57a4 ("Dockerfile: Update to drop virt-make-fs packages")
Signed-off-by: Tom Rini

Dockerfile: Download the Arm FVP and extract it

2025-04-10T14:20:09+00:00

There are some reference platforms from Arm which are not found in QEMU
but instead in the FVP tool. As we can make use of this in CI later on,
download and extract it in our Dockerfile today.

Signed-off-by: Tom Rini

Dockerfile: Update to a more current TF-A release tag

2025-04-10T14:20:09+00:00

In preparation for using TF-A more in our CI loops, switch to the
current release tag for TF-A.

Signed-off-by: Tom Rini