[u-boot-test-hooks PATCH v4 3/3] Provide some basic scripts for Labgrid integration

[Tom Rini]

On Wed, Aug 28, 2024 at 03:25:00PM -0600, Simon Glass wrote:
> Hi Tom,
> 
> On Wed, 28 Aug 2024 at 14:19, Tom Rini <trini at 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 <sjg at 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.

Right, but this gets back to what I'm most confused about (and need to
talk with Kevin Hillman about maybe, but I missed my last meeting where
he was as well), you have a bunch of logic for integration of buildman
too, and I have a few wrappers around exiting labgrid-client commands.
And I don't know what direction upstream is going to want to take.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20240828/8f869c51/attachment.sig>