-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controlling a strategy at runtime #1374
Comments
States of a strategy can already be requested with the |
This is not actually about the state of a strategy. It is about the states that it should go through and what exactly they should do. I have been experimenting with these for UBootStrategy:
Note that 'start' is useful since it avoid suppressing the start-up message, and shows the output even if the board fails to boot to a prompt. The 'bootstrap' state is selected if do-bootstrap is true., otherwise it is bypassed. The bootstrap state can be told to build U-Boot, or just to use the existing build |
Yes, this is true for the |
Are you open to enhancements to UBootStrategy? The -s command allows one state to be selected, but in this case I want to bring up the console and control which states are used to get there. This avoids having to run labgrid-client multiple times to get to the console. |
I would like to be able to tell the U-Boot strategy what to do at runtime, e.g.:
At the moment I have implemented this with a new --variable (-V) argument to labgrid-client, with these variables available for use by strategies.
By far the most common use case I have is to build, write and start U-Boot on a board (case 3). This is:
To just write the already-built U-Boot (case 2):
To just start with whatever the board has (case 1):
Does this seems like a reasonable feature? Is there an existing mechanism to control strategies from the cmdline?
The text was updated successfully, but these errors were encountered: