board/qemu/ppc64le-powernv8: fixup example
PATCH 1/1 board/qemu/ppc64le-powernv8: fixup example
Use full relative pathes for rootfs and kernel, like in other readme's.
--- board/qemu/ppc64le-powernv8/readme.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
board/qemu/ppc64le-powernv8/readme.txt +1 -1
@@ -1,5 +1,5 @@ Run the emulation with: -qemu-system-ppc64 -M powernv9 -kernel vmlinux -append "console=hvc0 rootwait root=/dev/nvme0n1" -device nvme,bus=pcie.3,addr=0x0,drive=drive0,serial=1234 -drive file=./rootfs.ext2,if=none,id=drive0,format=raw,cache=none -device e1000e,netdev=net0,mac=C0:FF:EE:00:01:03,bus=pcie.1,addr=0x0 -netdev user,id=net0 -serial mon:stdio -nographic # qemu_ppc64le_powernv8_defconfig +qemu-system-ppc64 -M powernv9 -kernel output/images/vmlinux -append "console=hvc0 rootwait root=/dev/nvme0n1" -device nvme,bus=pcie.3,addr=0x0,drive=drive0,serial=1234 -drive file=output/images/rootfs.ext2,if=none,id=drive0,format=raw,cache=none -device e1000e,netdev=net0,mac=C0:FF:EE:00:01:03,bus=pcie.1,addr=0x0 -netdev user,id=net0 -serial mon:stdio -nographic # qemu_ppc64le_powernv8_defconfig The login prompt will appear in the terminal window.
Signature · 6 lines
2.30.2 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 7 lines · On Sat, 12 Aug 2023 18:19:09 +0200 Waldemar Brodkorb <[email protected]> wrote:
Use full relative pathes for rootfs and kernel, like in other readme's.
Signed-off-by Waldemar Brodkorb <[email protected]>--- board/qemu/ppc64le-powernv8/readme.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks. I was initially a bit confused because all those readme.txt files for Qemu configurations are used in our Gitlab CI infra to automatically boot the resulting kernel/rootfs images in Qemu, and the build/test was working fine in our CI.
Turns out that board/qemu/post-image.sh strips output/images/, and then board/qemu/start-qemu.sh.in chdir into ${BINARIES_DIR}. So indeed, it makes sense that both this incorrect readme.txt, and all the other ones for Qemu defconfigs, that had output/images, worked.
Thomas
Signature · 7 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Quoted 18 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni via buildroot <[email protected]> writes:
Quoted 7 lines · On Sat, 12 Aug 2023 18:19:09 +0200 Waldemar Brodkorb <[email protected]> wrote:
Use full relative pathes for rootfs and kernel, like in other readme's.
Signed-off-by Waldemar Brodkorb <[email protected]>---
board/qemu/ppc64le-powernv8/readme.txt| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)Applied to master, thanks. I was initially a bit confused because all those readme.txt files for Qemu configurations are used in our Gitlab CI infra to automatically boot the resulting kernel/rootfs images in Qemu, and the build/test was working fine in our CI.
Quoted 4 lines
Turns out that
board/qemu/post-image.shstrips output/images/, and then board/qemu/start-qemu.sh.in chdir into ${BINARIES_DIR}. So indeed, it makes sense that both this incorrect readme.txt, and all the other ones for Qemu defconfigs, that had output/images, worked.
Committed to 2023.02.x and 2023.05.x, thanks.
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot