Closed paulwratt closed 6 years ago
This is a future blue sky goal for me too ...and the reason I named the project pTOS and not piTOS ;)
I try to follow the following naming conventions when adding files:
The split is not as clear cut as the convention above, but future changes should split and change that. A future change would be to rename some of the raspi* files to bcm283[567]* as required, as the PI isn't the only board that uses this family of chipsets.
So if you want to add support for a board, by all means do, but I do think it's best to concentrate on a single family as a start.
Ok, I understand, I will try to also adhere to the way you are doing thing (qudos on the pTOS thing :).
unfortunately I dont have anything to try a port with, and I dont feel like bricking my Chromebook quite yet, but I am seriously interested in that Gemini PDA palmtop (just not atm)
(I think this should be asked (demanded?) sooner rather than later.)
Is it possible to (quickly?) rework the new RPi additions to EmuTOS, seperating RPi and ARM v6 and v7 stuff as well. So it can easily be modified for another device, specifically (but not limited too) other arm devices like Banana, Orange, etc (or the Gemini Palmtop PDA: http://www.planetcom.co.uk/) where usually only the video initialization need to be different for different platforms .. and other non-arm SBC's could use it too, also allowing pTOS to be safely integraded back into EmuTOS (in the future) if need be.it would also mean Iyonix (armv5) owners could (theoretically) use it as well (not that I have one to test on mind you).
.. thereby making pTOS into
portableTOS
instead of justpiTOS