On Fri, 2019-03-22 at 14:24 -0700, Waldek Kozaczuk wrote: > I would be interested except I have literally zero experience with > ARM (except I know how to spell it ;-))
:) > The only ARM machine I have access to is Raspberry PI 3 ( > https://www.raspberrypi.org/products/raspberry-pi-3-model-b/). It > might be fun to get OSv either directly boot on it. I think it might > be even possible to run Linux with KVM on Raspberry PI. So I'm not actually using hardware for now. I'm using qemu-system- aarch64 as shown on the wiki page: qemu-system-aarch64 -S -s -nographic -machine virt -kernel build/release.aarch64/loader.img -cpu cortex-a57 -m 1024M -append " --nomount /tools/uush.so" The problem I'm having is that the assignment of the pl011 serial driver to the early console port isn't working, and thus we end up with no method for console::arch_early_console.write. I made this quick hack: diff --git a/arch/aarch64/arch-setup.cc b/arch/aarch64/arch-setup.cc index 4f4be836..24a4e6a8 100644 --- a/arch/aarch64/arch-setup.cc +++ b/arch/aarch64/arch-setup.cc @@ -185,7 +185,9 @@ void arch_init_early_console() } new (&console::aarch64_console.pl011) console::PL011_Console(); + console::aarch64_console.pl011.write("a", 1); console::arch_early_console = console::aarch64_console.pl011; + console::arch_early_console.write("b", 1); int irqid; u64 addr = dtb_get_uart(&irqid); if (!addr) { and I get 'a' printed, but the call to console::arch_early_console.write fails. Why can't we assign there? Rick -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
