On 4/8/22 22:37, Daniel Palmer wrote: > Hi Rob, > > On Sat, 9 Apr 2022 at 09:20, Rob Landley <rob@xxxxxxxxxxx> wrote: > >> I've been booting Linux on qemu-system-m68k -M q800 for a couple years now? (The >> CROSS=m68k target of mkroot in toybox?) >> >> # cat /proc/cpuinfo >> CPU: 68040 >> MMU: 68040 >> FPU: 68040 >> Clocking: 1261.9MHz >> BogoMips: 841.31 >> Calibration: 4206592 loops >> >> It certainly THINKS it's got m68000... > > I couldn't work out how to define a mc68000 machine on the command line alone. > There might be a way but it didn't seem like it. By adding "-cpu m68000" to the qemu command line? The problem is you need a working _system_. If you wget http://landley.net/toybox/downloads/binaries/mkroot/latest/m68k.tgz and extract it and run ./qemu-m68k.sh it boots to a shell prompt. If you "./qemu-m68k.sh -cpu m68000" it doesn't boot because the kernel is built for 68040. >> (I'd love to get an m68k nommu system working but never sat down and worked out >> a kernel .config qemu agreed to run, plus compiler and libc. Musl added m68k >> support but I dunno if that includes coldfire?) > > Once I get QEMU to emulate a simple mc68000 system my plan is to get > u-boot going (I managed to get it to build for plain mc68000 but I > didn't get far enough with the QEMU bit to try booting it yet) then > put together the buildroot configs to build qemu, u-boot, a kernel and > rootfs that just work. Then I can hook it into CI and have it build > and boot test automatically and it won't bit rot anymore. I don't bother with buildroot much, I wrote a 300 line bash script that builds a bootable Linux system instead: https://github.com/landley/toybox/blob/master/scripts/mkroot.sh As for adding coldfire support, let's see... google for "qemu coldfire" first hit is https://qemu.readthedocs.io/en/latest/system/target-m68k.html which says the default board in qemu-system-m68k is coldfire and has run uclinux. There's a defconfig for it (arch/m68k/configs/m5208evb_defconfig) so: $ make ARCH=m68k m5208evb_defconfig ... $ CROSS_COMPILE=m68k-linux-musl- make ARCH-m68k ... $ qemu-system-m68k -nographic -kernel vmlinux Hey, console output on serial using my existing m68k toolchain. Good sign. Ok, let's see, can I get a userspace... No, I can't. The coldfire kernel only supports BINFLT, which is an a.out derivative. All the nommu targets I'm supporting are either FDPIC or (where gcc hasn't merged fdpic support yet) I'm building static pie and using the FDPIC loader in the kernel, which can load normal ELF: FDPIC makes the 4 bss/data/text/rodata sections independently relocatable and static PIE has those 4 glued together into one contiguous lump but at least that lump is relocatable, so it's a lot worse about fragmentation but does at least RUN... If I can't wire up the fdpic loader for coldfire, I can't build ELF format binaries for it, and I just don't mess with a.out anymore. >> >> It looked like 68328serial.c was removed because someone tried to >> >> clean it up and it was decided that no one was using it and it was >> >> best to delete it. >> >> My plan was to at some point send a series to fix up the issues with >> >> the Dragonball support, revert removing the serial driver and adding >> >> the patch that cleaned it up. >> > >> > Nice. I will leave all the 68000/68328 code alone for now then. >> >> The q800 config uses CONFIG_SERIAL_PMACZILOG. Seems to work fine? > > Dragonball uses a weird UART that doesn't seem to be compatible with > any of the common ones so it needs its own driver. Indeed. That said, the 5208 is using CONFIG_SERIAL_MCF and I got serial output from the kernel I just built. Pity it hasn't got FDPIC support... > Cheers, > > Daniel Rob
