RISC OS Machines

For information purposes – had anyone written a procedure or module that gives information of the machine running RISC OS?
ie SYS “Machine” TO Ans$

Arcimedes- A7000+ – RPC600 – RPC SA – Iyonix – A9 – Beagle – Panda – VPC – RPCEmu
etc

Well, IIRC there’s been previous discussion here about the machine types as recorded in ARM Linux docs, but no specific program. ISTR that some of the more recent hardware was being lumped in together. But I can’t find that thread now, the nearest I’ve turned up being board type & revision. I think I was looking for OMAP3 – How to deal with different hardware configurations for different boards?.

Thanks for that – I was looking into:-

SYS OS_PlatformFeatures,0 TO A%

Iyonix gives %1000000011111111001
SA RPC gives %11011

What does the Beagle/Panda/A9 give?

Sorry – can’t check now. How much scope (or need) is there to cater for further differentiation within OS_PlatformFeatures 0, w.r.t. the HALs?

Using !LIRC on the Iyonix – it reckons it’s running on a SA RPC – so I looking for a way of updating it.
It would be nice to add the A9 – Armini – beagle – panda etc

A BeagleBoard xM gives 2041 or %11111111001 with RISC OS 5.19.

Thanks
I wonder what the 1<<18 indicates in the Iyonix.
11-31 Reserved for future expansion.

HALDeviceComms_GPIO tells you which Beagle, Devkit or Panda you are running on.
If you run the GPIO module I have added a star command “GPIOMachine” that prints it out.
Not for pre Beagle machines though.

Fundamentally the original idea was that OS development would be single forked and QA controlled so that it would be, as far as possible, backward compatible. Thus an application would simply RMEnsure the earliest version of any modules it needed that provided sufficient functionality (assuming that leter versions would continue to support this).

It would therefore not need to know what hardware it was running on.

OK we have ARM7 instructions, 32 bit processors, a RISC OS Limited fork with really nice rounded edges on the windows and version inflation so that 6.00 might or might not be ‘greater then’ 5.19 depending on your view.

What is the new paradigm please?

1 wonder what the 1<<18 indicates

For flags defined after RISC OS 3.70, see here