Skip to content

arm64: zynqmp: Cleanup defconfigs

Tom Rini u-boot 1 version New

Get series with b4
b4 am 20191210135639.GU9549@bill-the-cat

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] arm64: zynqmp: Cleanup defconfigs
Quoted 23 lines · Michal Simek

Hi Tom,

Quoted 7 lines · Michal Simek

Hi,

over years a lot of new Xilinx ZynqMP board have been added to U-Boot with corresponding defconfigs. Also a lot of drivers have been moved to DM that we can make one generic configuration with one defconfig.
Nand still needs to be validated that's why dc2/dc3 are not moved yet.

Quoted 7 lines

Boards can be build like this:
export DEVICE_TREE="avnet-ultra96-rev1"
make xilinx_zynqmp_virt_defconfig
make -j

Series depends on patches sent before that's why here is full tree:
https://github.com/michalsimek/u-boot/tree/20191209-mainline

This series will require some changes in CI loops because right now I didn't setup default device tree (CONFIG_DEFAULT_DEVICE_TREE) to "force" everybody to properly pass DEVICE_TREE via command line. I can't use OF_BOARD because then SPL is built without DT at all.

Quoted 7 lines

How do you think I should handle it for CI loops?
1. I can remove this configuration but it will be only one at the end that's why not a good solution.
2. Add generic option to run some commands before tests like export DEVICE_TREE above
3. provide different options for SPL/full u-boot how OF_SEPARATE/OF_BOARD is handled.

So, for CI are you wanting to test most device trees, or just one? Are we able to run one of these device trees via QEMU? If we can run the virt defconfig via qemu, we should just update/extend that stanza in the CI files to set DEVICE_TREE and exclude building it from the normal jobs. If we can't run via qemu then yes, something like option #2 and we set DEVICE_TREE in one job and export it if set in the build job.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191210/3a7a3ed6/attachment.sig>