Hi Peter,
On Wed, 28 Aug 2024 at 12:14, Peter Robinson pbrobinson@gmail.com wrote:
Hi Simon,
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.
What's ellesmere?
It is a lake but also the name of a computer.
Signed-off-by: Simon Glass sjg@chromium.org
Changes in v4:
- Support pytest fully with dual-build boards like Beagleplay
Changes in v3:
- Update scripts for latest version of Labgrid integration
- Add poweroff.none and poweron.none
- Provide -n flag when querying board info
- Target the grpc version of Labgrid which is now in -master
- Update README to cover the changes
Changes in v2:
- Make use of the common script (only) to set bin_dir
README.md | 50 ++++++++++++++++++++++++++++++++++++
Maybe that should be in a separate labsgrid readme?
My hope is that Labgrid becomes the normal way of running these tests, so having it in the main place (and perhaps eventually removing the old way) is my goal.
bin/console.labgrid | 42 ++++++++++++++++++++++++++++++ bin/ellesmere/common-labgrid | 46 +++++++++++++++++++++++++++++++++ bin/ellesmere/conf.all | 24 +++++++++++++++++ bin/getrole.labgrid | 25 ++++++++++++++++++ bin/release.labgrid | 22 ++++++++++++++++ bin/release.none | 22 ++++++++++++++++ bin/u-boot-test-getrole | 38 +++++++++++++++++++++++++++ bin/u-boot-test-release | 26 +++++++++++++++++++ 9 files changed, 295 insertions(+) create mode 100644 bin/console.labgrid create mode 100755 bin/ellesmere/common-labgrid create mode 100644 bin/ellesmere/conf.all create mode 100644 bin/getrole.labgrid create mode 100644 bin/release.labgrid create mode 100644 bin/release.none create mode 100755 bin/u-boot-test-getrole create mode 100755 bin/u-boot-test-release
[..]
Regards, Simon