Hi Tom, On Wed, 28 Aug 2024 at 14:19, Tom Rini <tr...@konsulko.com> wrote: > > On Wed, Aug 28, 2024 at 10:45:23AM -0600, Simon Glass wrote: > > > With Labgrid we don't need to specify the various methods, except for > > the console, which simply calls labgrid-client. > > > > This allows supporting any boards in your lab, without adding per-board > > configuration to these hooks. > > > > Provide ellesmere files as an example. > > > > Signed-off-by: Simon Glass <s...@chromium.org> > > I think maybe we call this version "labgrid-buildman" and make sure the > documentation emphasizes using buildman to provide U-Boot. This will > make it easier for me to provide a follow-up of say "labgrid-external" > that requires the binary to be provided, similar to our other hooks.
It can be used in this way. The 'ub-pyt -B' does a bootstrap of the board without doing a build, if that helps to show the path through the code. If you don't pass --build to test.py then it won't do a build. If you like, you can pass --build-dir (and with the testb series --build-dir-extra) as you do now. The binary will be written to the board as is. > > My thinking is that while it would be good to be able to expose labs to > CI, and I would like to get mine showing up as well it's also important > that I be able to keep doing the type I do where I extend the normal > defconfig with additional features to test. Let me know if this doesn't work for you. It is certainly an important use case. Regards, Simon
