[Oberon] Oberon V4 on the Raspberry Pi?

[Joerg]

ETHOberon is written in Oberon-2, as LinzOberon.

Jörg

> Am 11.01.2021 um 23:34 schrieb Liam Proven <lproven at gmail.com>:
> 
> 
> On Mon, 11 Jan 2021 at 21:09, Chris Burrows <chris at cfbsoftware.com> wrote:
> >
> > This is potentially confusing now that 'emulators' for Project Oberon exist.
> > They are different beasts altogether. Further to Paul's comments, at the
> > risk of being picky I would rephrase what you said as:
> >
> > "Native Oberon is one platform of what was originally called Oberon System 3
> > (S3 - it was never called V3) and was later renamed to ETH-Oberon. There are
> > others hosted on Windows, MacOS and Linux and revived by Peter Matthias as
> > the Oberon Linux Revival (OLR) ...
> >
> > Oberon V4, aka Linz Oberon only runs on bare hardware on the ETH Ceres
> > computer (which uses the National Semiconductor NS32xxx CPU) but is also
> > hosted on MS-Windows, Solaris (68K and Sparc), HP-UX, Irix, Amiga, OS2 ..."
> >
> > My main point is that none of these systems are 'emulated'. In every case
> > instructions generated by the Oberon compiler are natively executed by the
> > CPU on the target platform.
> >
> > On the other hand, AFAIK, currently all versions of Project Oberon running
> > on Windows, MacOS, Linux etc. ARE emulated. In this case, the compiler
> > generates RISC5 instructions that are then 'interpreted' by a software
> > emulation of the RISC5 CPU. Each RISC5 instruction results in tens
> > (hundreds?) of Intel (or whatever CPU is being used to run the OS) CPU
> > instructions being executed.
> >
> > Note that Project Oberon running on FPGA hardware is not emulated. Every
> > RISC5 instruction generated by the compiler is executed directly by the
> > RISC5 CPU implemented in configurable hardware.
> >
> > It's as clear as mud ... ;-)
> 
> Useful clarification -- thank you!
> 
> I must admit, I don't feel so bad about getting it wrong now! 😊  
> 
> I also note that various people have done a lot more work on the Wikipedia article about Oberon, and that it's a whole year since I last worked on it. I feel a bit guilty about that. There's a version history table in there now, but IMHO it still needs a bit more info.
>   
> I think I now understand the relationship, more or less, between:
> 
> • Oberon System 3, AKA ETH Oberon – on x86 (Native Oberon) & hosted on x86
> • Oberon V4, AKA Linz Oberon – implemented in Oberon 2 – on Ceres & hosted on x86
> • AOS, AKA Bluebottle, AKA A2 – implemented in Active Oberon – on x86, ARM and hosted
> • Project Oberon, AKA Oberon V5 – implemented in Oberon-07 – on RISC5 & emulators
> 
> Is that right?
> 
> What is ETH Oberon written in? Original Oberon, what we might call Oberon 1?
> 
> -- 
> Liam Proven – Profile: https://about.me/liamproven
> Email: lproven at cix.co.uk – gMail/gTalk/gHangouts: lproven at gmail.com
> Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
> UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20210112/10f2e15e/attachment.html>