Helping on m68k
As the m68k port is getting shape, maybe some of you want to give a hand, so here is how to set up the environment. After explaining the choice of the target platform we’ll start with the build system, then the emulator to debug on the chosen platform.
Why not Macs? I want it on my Amiga! I have a NeXT to give away!(I wish ;)) The choice of the target platform was actually directed by the available emulators for various m68k machines. QEMU has a m68k target, but it’s still only ColdFire, not the real thing. And it doesn’t emulate an existing machine. Most operating systems for the 68k machines from this era had to support cpus ranging from the bare 68000 to 68030. This means most didn’t actually use the MMU available on the 030 and later CPU. Actually, many machines were using Low Cost versions like the 68EC030 which lacked either the FPU or the MMU. This was the case of most Amiga models, of course one could add CPU boards with a 040 or 060 to them. But we do need an mmu for Haiku. While I own a Mac LC III which has a full 030, Basilisk II doesn’t emulate the MMU as far as I know, because since most Macs didn’t have one, MacOS didn’t use it anyway, except for swapping when enabled in some versions. I don’t know of any NeXT emulator, but just shout if you do. Early SUN workstations were also using 68k chips, but with a custom MMU so let’s not talk about them. The Amiga has a well known emulator, UAE, but it doesn’t have MMU support either. I heard recent WinUAE does, but I just don’t use Windows for real work. But it will probably make a good second candidate for later on. It seems there is even an attempt at creating a new 68K-based Amiga. There are some other 68k platforms around, like X68000, which a 030 model existed, but they are quite rare. The only common platform left is the Atari Falcon, for which the emulator ARAnyM (for Atari Running on Any Machine) actually provides full 040 emulation, including the MMU. The platform is also much more standardized and documented than Macs, due to the low number of models and being a gaming platform forced Atari to stay hardware compatible with the plain ST, whereas Macs used the ROM and the OS to abstract the hardware which radically changed from one model to the next.
Making a buildIt’s not much different from a regular x86 build, the only difference being the target architecture. To get the required tools, just follow the Linux guide, then when comes the time of configuring, instead we’ll do a
./configure –build-cross-tools-gcc4 m68k ../buildtools/This should build the cross compiler and set everything up. Then just go forward with a
jam -q haiku-imageThe kernel isn’t fully working yet, but everything should build just fine.
Now we’ll also need a bootloader that can be used by the emulator. For now we only target the Atari Falcon. Theoretically, the Falcon should be able to just go ahead and use the BFS boot sector, but at least the emulator doesn’t do it, mostly because on most Atari machines harddrive support needs to load drivers first. To make things easier also, the bootloader can be built as a .prg file that can be loaded directly by the emulator. It should be possible to also build a bootable floppy, but it’s not yet working, so let’s use a .prg, which can also be used on real machines, when put in the AUTO folder.
jam -q haiku.prg
Testing itNow we’ll need something to test this image, and don’t expect your laptop to boot it. First, we’ll need a recent ARAnyM, as I fixed an issue with Transparent Translation Register handling, so release version won’t work. We’ll just use the CVS version:
cvs -d:pserver:firstname.lastname@example.org:/var/repos login cvs -z3 -d:pserver:email@example.com:/var/repos co aranym cd aranym ./configure –enable-fullmmu –enable-fullhistory makeOptionally we can install it, as root:
su make installBut it can also be run from there with the full path.
We’ll also need a ROM to boot. Luckily, Some people reimplemented the full Atari ROM as Free Software, it’s named AFROS. Go download it from here, just follow the link to sourceforge. Unzip it somewhere. We’ll now copy the default configuration file to tweak it, and create a symlink to the haiku.prg we generated earlier.
cd afros-0.9.5 cp config haiku ln -s /path/to/haiku/trunk/generated/objects/haiku/m68k/release/system/boot/platform/atari_m68k/haiku.prg system/Now, edit the file named haiku, and changes matching lines to:
Bootstrap = system/haiku.prg RedirConsole = YesAnd in the [IDE0] section:
Present = Yes ByteSwap = Yes Path = /path/to/haiku/trunk/generated/haiku.image
Now you should be set. To start the emulator, let’s try:
/path/to/aranym -c ~/afros-0.9.5/haiku
After a lot of messages, it should present you the familiar boot menu, where you can select the partition to use, and continue booting. Then it will load the kernel. I’m still working on getting the kernel on shape, so it won’t go far, but feel free to help out.
- GSOC 2019 Final Report
- Haiku Activity Report: Performance Edition
- new PVS studio scan
- Coding week 4,5,6
- [GSoc 2019] Weeks #4, #5 and #6 progress report
- Haiku monthly activity report - 06/2019
- Coding week no 2 and 3
- [GSoC 2019] Weeks #1, #2 and #3 progress reports
- Haiku monthly activity report, May 2019
- Coding week #1