[Bug binutils/26206] Add pei-aarch64 support for native EFI support
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 Steve McIntyre changed: What|Removed |Added CC||steve-sourceware at einval dot com --- Comment #5 from Steve McIntyre --- Adding myself to the CC list - as the person who wrote that text in the Debian shim package, I'd love to see this support added. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/26206] Add pei-aarch64 support for native EFI support
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #11 from Steve McIntyre --- Hi! Do you have an existing UEFI image (e.g. edk2 AAVMF) to use for testing with? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/26206] Add pei-aarch64 support for native EFI support
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #13 from Steve McIntyre --- Hmmm, OK. That UEFI image (when padded up to 64MiB) starts here and will let me start an OS or go into the shell OK. Are you getting any errors? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/26206] Add pei-aarch64 support for native EFI support
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #15 from Steve McIntyre --- Hmmm, OK. That UEFI image (when padded up to 64MiB) starts here and will let me start an OS or go into the shell OK. Are you getting any errors?(In reply to Tamar Christina from comment #14) > (In reply to Steve McIntyre from comment #13) > > Hmmm, OK. > > > > That UEFI image (when padded up to 64MiB) starts here and will let me start > > an OS or go into the shell OK. Are you getting any errors? > > No, QEMU just pretty much hangs, maybe a wrong parameter, I'm doing > > rm -f flash0.img flash1.img > dd if=QEMU_EFI.fd bs=1M of=flash0.img conv=notrunc > dd if=/dev/zero bs=1M count=64 of=flash1.img > dd if=/dev/zero bs=1M count=64 of=flash0.img > mkdir boot > cp hello.efi boot/ > env DISPLAY=:0 qemu-system-aarch64 -machine virt -monitor stdio -drive > file=fat:rw:boot/ -drive file=flash0.img,format=raw,if=pflash -drive > file=flash1.img,format=raw,if=pflash flash1.img Aha! Your command there will totally replace the content of flash0.img, not append to it. :-) Try: $ dd if=/dev/zero bs=1M count=62 >> flash0.img (there are probably other dd options to append, but that command is what I've used successfully) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/26206] Add pei-aarch64 support for native EFI support
https://sourceware.org/bugzilla/show_bug.cgi?id=26206 --- Comment #17 from Steve McIntyre --- (In reply to Tamar Christina from comment #16) > hmmm It looks like I'm dropped to a QEMU shell. > > (qemu) info status > VM status: running > > which says running, perhaps I can't do this over SSH and a window has popped > up on the desktop? If so I'll check it next week :) Cool, sounds good. You can tell qemu to run without graphics etc. too, that's what I tend to do on my arm64 boxes here so I get text display in the xterm: qemu-system-aarch64 -m 2048 --enable-kvm -vga none -nographic -machine virt,gic-version=host,kernel_irqchip=on -cpu host -pflash aarch64-OVMF.fd -pflash aarch64-storage.fd -- You are receiving this mail because: You are on the CC list for the bug.
