On Tue, Dec 10, 2019 at 01:40:42PM +0100, Michal Simek wrote: > Hi Tom, > > On 09. 12. 19 16:19, Michal Simek wrote: > > 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. > > > > 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. > > 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. -- Tom
signature.asc
Description: PGP signature
