On Thu, Jan 26, 2023 at 05:47:27PM +0100, Michael Nazzareno Trimarchi wrote: > Hi > > On Thu, Jan 26, 2023 at 5:46 PM Jagan Teki <[email protected]> wrote: > > > > On Thu, 26 Jan 2023 at 22:14, Mark Kettenis <[email protected]> wrote: > > > > > > > From: Jagan Teki <[email protected]> > > > > Date: Thu, 26 Jan 2023 21:57:57 +0530 > > > > > > > > Hi, > > > > > > > > The master branch seems broken with recent changes on binman, I found > > > > that u-boot.itb is not creating for evb-rk3568 boards. > > > > > > > > HEAD > > > > commit 17e8e58fe62c019b2cc26af221b6defc3368229f > > > > Merge: 4e1ab2065e cd108f2795 > > > > Author: Tom Rini <[email protected]> > > > > Date: Tue Jan 24 21:07:01 2023 -0500 > > > > > > > > Any insight? > > > > > > Well, here is my insight: > > > > > > As long as the only board supported board in mainline is an evaluation > > > board that nobody in the community has, it won't be tested. Can we > > > somehow make progress in getting some of the more popular RK356x > > > boards (like the quartz64, nanopi r5s, raxda rock 3) in the tree? > > > > fyi: radxa-cm3 is part of Mailing list. > > Maybe we should setup some embedded lab, with boards. We are working > to create some new testing boards to > be use remotely for CI and developers. Do we have a way to make this > setup for u-boot?
I would really like to see someone leverage the lab management used by kernelci and then monitor U-Boot trees and leverage https://source.denx.de/u-boot/u-boot-test-hooks for the flash / etc portion required to run our current test suite. Currently we just have some ad-hoc labs that do this. -- Tom
signature.asc
Description: PGP signature
