Re: [Qemu-devel] Poking at m68k gitorious branch.

[Laurent Vivier]

Hi Rob,

 

you need to do a fresh clone because I rebase the branch frequently on the qemu/master instead of merging it. It is easier to manage for me.

 

BTW, qemu-system-m68k is not working currently. I'm working on it on the branch q800 to emulate a macintosh quadra 800. I'm able to boot until the first process (1), then I have some issues with the MMU. The serial line is working (ttyS0 is in fact the second port, use "-serial none -serial stdio" to see it), the framebuffer too. The ADB emulation needs some more work to be correctly attached to m68k VIA instead of PPC CUDA. For the SCSI, we can use ESP, but the pseudo-dma mode used by q800 is not implemented.

To compile my m68k kernel I use a chroot and the m68k linux-user qemu mode, that seems to work well... perhaps you can test your tools inside this.

 

Regards,

Laurent

Le 19 avril 2012 à 01:24, Rob Landley <address@hidden> a écrit :

> My aboriginal linux project has bootable system images for a bunch of
> targets (see http://landley.net/aboriginal/bin) and I want to add m68k.
> For years it's been building a stub m68k system image, but the
> run-emulator.sh script that should theoretically launch it is just a stub.
>
> A user once got my m68k root filesystem running under the Aranym
> emulator, so I know my cross compiler and root filesystem work. But I
> haven't got an m68k kernel qemu can boot, or a qemu that can boot it.
>
> A year or so back I poked at the m68k gitorious branch:
>
>   git://gitorious.org/qemu-m68k/qemu-m68k
>
> But it wasn't finished and I got distracted.
>
> I just did a fresh clone of the branch (for some reason pull said I'd
> diverged by ~100 commits and there was a conflict?  I'm guessing the
> patch series that got posted here, maybe?), built a kernel with the
> attached .config and the cross-compiler-m68k from the above aboriginal
> binary directory url, and took a wild guess at qemu/kernel command line
> arguments, currently just trying to get boot messages on the serial console:
>
>   qemu-system-m68k -nographic -no-reboot -kernel vmlinux \
>     -append "console=ttyS0 panic=1"
>
> The result was:
>
> QEMU 1.0,1 monitor - type 'help' for more information
> (qemu) QEMU 1.0,1 monitor - type 'help' for more information
> (qemu) qemu: fatal: Illegal instruction: 7f45 @ 00000000
> D0 = 00000808   A0 = 0021e744   F0 = 7fff ffffffffffffffff
> D1 = c4653600   A1 = 0021e6ae   F1 = 7fff ffffffffffffffff
> D2 = 27000021   A2 = 00001000   F2 = 7fff ffffffffffffffff
> D3 = e768002c   A3 = 00233000   F3 = 7fff ffffffffffffffff
> D4 = 00000000   A4 = 00000000   F4 = 7fff ffffffffffffffff
> D5 = 00000000   A5 = 00000000   F5 = 7fff ffffffffffffffff
> D6 = 00000000   A6 = 00000ff8   F6 = 7fff ffffffffffffffff
> D7 = 0022db50   A7 = 00000ff0   F7 = 7fff ffffffffffffffff
> PC = 00000000   SR = 2700 ----- Aborted
>
> Which is a bit of a dead end. I'd guess that "vmlinux" isn't the right
> binary, except there isn't an arch/m68k/boot directory...
>
> Laurent: do you have any hints for me?
>
> Thanks,
>
> Rob
> --
> GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
> Either it's "mere aggregation", or a license violation.  Pick one.