Hi Tom, On Tue, 15 Aug 2023 at 08:46, Tom Rini <[email protected]> wrote: > > On Tue, Aug 15, 2023 at 08:44:18AM -0600, Simon Glass wrote: > > Hi Tom, > > > > On Sun, 13 Aug 2023 at 08:43, Tom Rini <[email protected]> wrote: > > > > > > On Sun, Aug 13, 2023 at 07:36:45AM -0600, Simon Glass wrote: > [snip] > > > > I see what you are saying, but from my side I am trying to enumerate > > > > the boards, since generally I (like) build things without explicitly > > > > specifying each board defconfig. > > > > > > Yes, but that's not possible in this case I think. And I'm really just > > > trying to figure out how we can make CI a little easier. But maybe we > > > can't / don't bother in this case and keep fixing up the sandbox > > > defconfig files as needed. > > > > Maybe...it sounds like you are really just wanting a way for buildman > > to manually build a single board with some config added, rather than > > having it detect and build everything that is in-tree? > > What I'm trying to do really, is since you didn't seem to see the value > in config fragments before, showcase how it would be beneficial to > sandbox (and CI) if we used them there.
Yes, don't worry, I am past that stage and I see their value. But I think for this to be more broadly useful we need a way to enumerate the combinations permissible for a board and give them names. Things like qconfig and buildman need to know what is going on and cannot infer it from the filesystem...? Regards, Simon
