Merge lp:~liuyq0307/lava-dispatcher/test-bootloader into lp:lava-dispatcher
Proposed by
Yongqin Liu
Status: | Merged |
---|---|
Merged at revision: | 473 |
Proposed branch: | lp:~liuyq0307/lava-dispatcher/test-bootloader |
Merge into: | lp:lava-dispatcher |
Diff against target: |
212 lines (+114/-11) 4 files modified
lava_dispatcher/client/base.py (+3/-0) lava_dispatcher/client/master.py (+82/-11) lava_dispatcher/default-config/lava-dispatcher/device-defaults.conf (+21/-0) lava_dispatcher/default-config/lava-dispatcher/device-types/panda.conf (+8/-0) |
To merge this branch: | bzr merge lp:~liuyq0307/lava-dispatcher/test-bootloader |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Linaro Validation Team | Pending | ||
Review via email: mp+123225@code.launchpad.net |
Description of the change
This modification will support to use the boot loader of the test images when we can load the test boot loader from the master boot loader
And by this mechanism, we can resolve the problem of booting omapzoom and aosp panda build in lava
have tested with the panda-stable build from https:/
and aosp build from my local on my local lava instance
To post a comment you must log in.
This approach makes me a bit nervous. We are basically chain-loading boot loaders. Its really cool, but I don't know if its safe and worth the additional cost of code maintenence. If we really can't get around boot loaders, maybe we should put some specific u-boot version on some boards in the lab and tag them, so certain builds can use them?