When a patch is co-developed with an AI assistant, the Co-developed-by
tag typically uses a noreply email address. Since Signed-off-by requires
a real person with a valid email address, skip the name/email mismatch
warning when the Co-developed-by email contains "noreply@".
Cover-letter:
checkpatch: Sync with Linux v6.18
This series syncs checkpatch.pl with Linux v6.18 and adds several
U-Boot-specific improvements:
- Fix patman's checkpatch message parsing for consecutive messages
- Allow test macros (UNIT_TEST, etc.) immediately after function close
- Allow AI Co-developed-by tags without requiring matching Signed-off-by
END
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <simon.glass@canonical.com>
U-Boot test declarations (e.g., FS_TEST, UNIT_TEST) should immediately
follow the closing brace of the test function with no blank line.
Add an exception to the blank-line-after-declaration check for *TEST
macros, and add a new check that warns if there IS a blank line before
a test declaration macro.
Update the patman test to handle duplicate warnings now that message
parsing correctly separates consecutive checkpatch messages.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <simon.glass@canonical.com>
When linker-inserted padding breaks list integrity, pointer arithmetic
like (end - start) / sizeof(struct) produces garbage. GCC optimizes
division by constants using multiplicative inverses, which only works
when the dividend is an exact multiple. With padding, outputs like
"Running -858993444 bloblist tests" appear instead of the correct count.
Enhance the linker list checking script to detect these problems by
adding symbol size tracking using nm -S. This enables:
1. Padding detection: Compare symbol sizes to gaps. If gap > size,
padding was inserted, breaking contiguous array assumptions.
2. Pointer arithmetic bugs: Check if (end - start) marker span is a
multiple of struct size.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <simon.glass@canonical.com>
Add a Python script for TKey-based full disk encryption key generation
and disk encryption operations:
- Generate hardware-backed encryption keys using TKey's Ed25519
signature and SHA-256 hashing
- Encrypt disk images with LUKS using the derived keys
- Open LUKS encrypted disks using the derived keys
- Support for both interactive password input and file/stdin input
- Automatic TKey device detection via USB enumeration
The script derives deterministic encryption keys from a password and
the TKey's unique device identifier, suitable for unlocking encrypted
root filesystems at boot time.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <simon.glass@canonical.com>
Update both build-efi and build-scripts to allow a -c option to provide
custom firmware. This makes the scripts more generally useful.
Drop the existing -c for --spice since it conflicts and is also is bit
hard to remember.
Signed-off-by: Simon Glass <simon.glass@canonical.com>
Provide a way to include a directory of files in the firmware image
created by build-efi
This is useful for including a U-Boot environment, for example.
Signed-off-by: Simon Glass <simon.glass@canonical.com>
The conditional filter checking for "drivers/video/images" in $(obj)
fails for out-of-tree builds where $(obj) contains the full build path.
Fix the wildcard pattern (%drivers/video/images) so files are matched
correctly.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
When running U-Boot as an EFI application under EDK2/OVMF, U-Boot doesn't
have direct access to QEMU's fw_cfg interface. To support the --bootcmd
option, write a uboot.env file to the EFI partition containing the boot
command.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Add -b as a short alias for --bootcmd to build_helper so it is available
in both build-qemu and build-efi
Move the fw_cfg bootcmd logic to build_helper as well.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Provide a -T/--tkey option to enable access to a USB-attached Tillitis
TKey.
Series-to: concept
Series-cc: heinrich
Series-links: 1:54
Series-version: 2
Cover-letter:
Bootstage and script enhancements
This series collects together a few improvements to the bootstage
subsystem, principally some new tests.
It also adds support for ACPI FPDT which is a way of passing timing
information to the OS.
A bug fix is provided for mouse clicks with expo.
Finally the series includes some new options for the build-efi script
for networking, spice, etc.
END
Signed-off-by: Simon Glass <sjg@chromium.org>
Complete writing of any output before running QEMU, since otherwise it
does not always appear until QEMU exits (e.g. with 'tee')
Signed-off-by: Simon Glass <sjg@chromium.org>
The USB mouse seems to have an absolute-pointer driver which can be
enabled in OVMF. Switch to this for x86.
Signed-off-by: Simon Glass <sjg@chromium.org>
Add a --bootcmd option to the build-qemu script that allows passing a
boot command to QEMU via fw_cfg. The bootcmd is written to the
"opt/u-boot/bootcmd" fw_cfg entry, which can be read by U-Boot's
EVT_BOOTCMD handler.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Move the BGRT image to use the same video_image linker-list approach
as the other embedded image. Move it into the drivers/video/images
directory and rename it to 'bgrt.bmp' since we know it is an image.
Drop the old bgrt Makefile rule as it is no-longer needed.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
It is inconvenient to have to access graphical images as independent
symbols. Create a new rule which handles any file mentioned in
drivers/video/images/Makefile
For each graphical image, embed in the image and create a linker-list
entry for it.
Series-changes: 2
- Use Canonical copyright
Series-changes: 3
- Rename it to video_defs.h since we will use it elsewhere
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
Since the U-Boot app now requests 512MB (to fit the ramdisk, etc.) and
Tianocore uses some as well, the current 512MB is not enough. Double it.
Signed-off-by: Simon Glass <sjg@chromium.org>
The pager can interfere with tests and there is a lab test which uses
the build-efi script. Add an option to disable the pager so that the
labgrid test can request that.
Signed-off-by: Simon Glass <sjg@chromium.org>
Fix line continuation in generate_schedule() that caused Sphinx to fail
with "Bullet list ends without a blank line; unexpected unindent" error.
Add tests to validate RST formatting of generated documentation.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
The ifeq/else/endif conditional for capsule_esl_file generation was
incorrectly placed inside the recipe, causing malformed Makefile syntax
that prevented proper dependency resolution. This resulted in build
failures when CONFIG_EFI_CAPSULE_AUTHENTICATE was enabled because the
capsule_esl_file target could not be created from the certificate file.
Move the conditional to properly wrap the rule definitions, allowing
Make to correctly parse and execute the capsule ESL generation rules.
Signed-off-by: Simon Glass <sjg@chromium.org>
Co-developed-by: Claude <noreply@anthropic.com>
This is around the wrong way. It should start with rc1 and progress up
from there. Fix this.
Also ensure that releases only happen every second Monday.
Signed-off-by: Simon Glass <sjg@chromium.org>
Add a Python script to replace shell-based release version calculations
with proper datetime handling:
Features:
- Calculates release versions based on U-Boot's bimonthly schedule
- RC numbering counts backwards from final release (rc1=2wks, rc2=4wks,
rc3=6wks)
- Dead-period detection for dates too early in release cycle
- Automatic Makefile version updates
- Release documentation generation and updates
- Multiple output formats (shell variables, JSON, version string)
Testing:
- 39 comprehensive test cases covering all scenarios
- 93% test coverage including edge cases and error handling
- Tests for cross-year boundaries, dead periods, and file operations
The script provides robust release automation for the GitLab CI pipeline
with proper error handling and extensive validation.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org)
The input file is used to process the dtsi, so add a dependency. This
bug was previously masked by a FORCE which was removed in
7738c4c2d7 Makefile: Avoid FORCE with ESL
Signed-off-by: Simon Glass <sjg@chromium.org>
We don't need to force building of the ESL dtsi or capsule file if they
already exist. Drop the FORCE dependencies.
Signed-off-by: Simon Glass <sjg@chromium.org>
A few of the steps are longer than the 7 characters allowed. Shorten
them so that the build output looks better:
Signed-off-by: Simon Glass <sjg@chromium.org>
When U-Boot is used as a library with other programs, some U-Boot
function names may conflict with the program, or with standard-library
functions. For example, printf() is defined by U-Boot but is typically
used by the program as well.
The easiest solution is to rename symbols in the object file, so that
they appear with a 'ub_' prefix when linked with the program.
Add a new build_api.py script which can:
- rename symbols based on a rename.syms file
- generate a header file (with the renamed symbols) for use by the
program
This makes use of the 'objcopy --redefine-sym' feature.
The tool has 100% test coverage.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
When CONFIG_CHID is enabled, U-Boot must have access to a set of CHIDs
which it can use to identfy the hardware it is running on.
Add support for reading a hwids/compatible.hwidmap file in the board
directory and including the information in the board's devicetree.
This works by running the hwids_to_dtsi.py.py script and putting the
result in the dtsi_include_list variable.
Signed-off-by: Simon Glass <sjg@chromium.org>
Add a Python script to convert Hardware ID files (as produced by
'fwupd hwids') into a devicetree format suitable for use within U-Boot.
Provide a simple test as well.
Co-developed-by: Claude <noreply@anthropic.com>
Signed-off-by: Simon Glass <sjg@chromium.org>
When running in CI it is better to specify the build directory rather
than provide a device. Add a --build-dir option.
Signed-off-by: Simon Glass <sjg@chromium.org>
The helper deals with whether we are actually running or not. We want it
to show the arguments even if not. So always call it.
Signed-off-by: Simon Glass <sjg@chromium.org>
Put this in the helper so that we can (later) have it show the correct
error when the virtiofs daemon fails.
Signed-off-by: Simon Glass <sjg@chromium.org>
At present the OS disk conflicts with the boot disk used to hold the
app (or payload). Number the OS disk after that.
Signed-off-by: Simon Glass <sjg@chromium.org>
At present the root disk conflicts with the boot disk used to hold the
app (or payload). Use virtio for this disk and number the others after
that.
Signed-off-by: Simon Glass <sjg@chromium.org>
