On 11/24/21 1:38 PM, Jan Kiszka wrote:
On 24.11.21 13:07, Gylstorff Quirin wrote:
On 11/24/21 12:45 PM, Jan Kiszka wrote:
On 24.11.21 12:44, Jan Kiszka wrote:Only dm-verity introduces the new target.
On 24.11.21 12:12, Q. Gylstorff wrote:...or is that only the case with your dm-verity series? Let me check.
From: Quirin Gylstorff <quirin.gylstorff@...>Definitely an improvement! But the fact that secure boot comes with a
Fix booting of secure-boot image
Parse .config.yaml for ease of use and reduced commandline clutter
Quirin Gylstorff (3):
start-qemu.sh: set bootindex for SECURE_BOOT
start-qemu.sh: parse .config.yaml for ease of use
start-qemu.sh: Simplify qemu call
start-qemu.sh | 33 ++++++++++++++++++++++++---------
1 file changed, 24 insertions(+), 9 deletions(-)
different target image is not reflected yet.
Will take all three if you could also update the documentation (on-top),
stating that building via "menu" will initialize the start-qemu vars
with fitting defaults.
I will send a v2. Did miss cip-core-image-security.