I owe you some explanation
regarding AROS. What I would like to achieve with AROS is to push forward the native AROS version for RaspberryPi. Why? AROS for ARM was a little bit abandoned last months or years so it needs a little bit of a fresh air. Why Raspberry? This platform is already pretty mature and offers you a very affordable hardware to play with. You can find the machines almost everywhere if you just look around you. I myself have some of them on my desk or under my desk at home, some on my desk at work, some of them are running time-critical stuff in our lab. Is RasPi not powerful enough for you? Well, sorry, maybe next version will be :)

So, what are my short- and mid-term goals? The new raspi port of AROS shall work in BigEndian mode, the mode in which original AmigaOS was working. With gcc compiler which can switch endianess on the fly and with Raspberry's CPU which is able to run in BE mode it should be feasible. Of course, there will be some issues to fix but hey, low-level development shall be an adventure! Once AROS will reach the state where it can boot on Raspberry in BE mode it will be time to upgrade/complete the drivers. You know, current port is not really complete, e.g. it lacks the USB support completely. So, completing the drivers, the mid-term goal.

And then? There are some things worth trying. Imagine having a source code compatible AROS on a 32-bit big endian machine. Wait... Same endianess, 32-bit... Could a seamless integration of m68k be made? I don't know now for sure, but maybe it could...

Tier Benefits
Recent Posts