Files
infix/board
Joachim Wiberg e3a0426154 board: mark developer U-Boot builds with -DEVEL
Developer builds report the bare upstream U-Boot version, e.g.
2025.01, and are easily mistaken for release builds.  Nothing stamps
a local version on non-release builds to tell them apart.

Write a .scmversion of -DEVEL from a pre-build hook when INFIX_RELEASE
is unset, so developer builds report 2025.01-DEVEL.  Release builds
are left untouched.

Closes #919

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
2026-07-06 05:28:09 +02:00
..

Board Support

The board support for an architecture always starts with Qemu support, this is what each linux_defconfig at the very least sets up. Then each $BR2_ARCH has additional BSPs, e.g., Banana Pi BPI-R3.

The board/ directory is matched with the configs/*_defconfigs and the only execption is board/common/, which holds all shared files for Infix builds.

Each board/$BR2_ARCH/ can then have vendor/product sub-directories for the BSPs which may contain "fixups" to the base kernel config and any additional device tree files that should be included as well.

To rebuild a board-specific package, e.g. NanoPi R2S:

make friendlyarm-nanopi-r2s-rebuild all