On Sun, Mar 24, 2019 at 5:30 PM Rick Payne <[email protected]> wrote:
> Hi Nadav,
>
> On Sun, 2019-03-24 at 12:11 +0200, Nadav Har'El wrote:
> >
> > Why the "-S"? It causes the machine not really to start.
>
> Oh sorry, I was using the debugger as it just crashes everytime, so no
> point not using it.
>
> > OSv v0.53.0-3-g8cd7d8aa
>
> So thats interesting, you're getting passed the point I can't. That
> makes me wonder if its a compiler version issue. Which version of the
> arm compiler are you using - I assume you're cross compiling?
>
Yes, I am cross-compiling (I don't have any ARM machine...). Just did "make
arch=aarch64".
$ aarch64-linux-gnu-gcc --version
aarch64-linux-gnu-gcc (GCC) 8.1.1 20180626 (Red Hat Cross 8.1.1-3)
> > Which is a different problem than you reported.
>
> Indeed, most odd...
>
> > I don't know anything about "pl011", but maybe qemu doesn't emulate
> > it,
> > or our driver doesn't know how to recognize qemu's version of it?
> > (just a wild guess).
>
> Nope on both cases. qemu supports pl011 and we detect it.
>
> > + console::aarch64_console.pl011.write("a", 1);
>
> This line succeeds, I get an 'a' on the console.
>
> > > console::arch_early_console = console::aarch64_console.pl011;
> > > + console::arch_early_console.write("b", 1);
>
> We crash at this point as the assignment didn't happen and there is no
> write method.
>
> Cheers,
> 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.
