7 ms·
Modernising RISC OS in 2020: is there hope for the ancient ARM OS?
- lowbloodsugar 6y ago"A software emulation of 32-bit ARM would be needed, with perhaps a 10x performance drop." Well, my Archimedes was 8Mhz, and my Pi is 1500Mhz, so we have some room there perhaps?
- LeoPanthera 6y agoWhich is fine, but the things we do with our home computers today are not the same things we did in the late 80s.
- 082349872349872 6y agoIf the things we do with with our home computers are crunching in kernel space instead of in userland, someone's done something wrong.
- wk_end 6y agoThe article's talking about running 32-bit applications in emulation, with a 64-bit native kernel. > Then a rewrite of RISC OS for 64-bit ARM chips would require a 32-bit emulation layer for old apps to run -- and very slowly at that, when ARM chips no longer execute 32-bit code directly. A software emulation of 32-bit ARM would be needed, with perhaps a 10x performance drop.
- Teongot 6y agoThe cost of simulating 32-bit ARM on 64-bit ARM is nothing like 10x if you try hard enough https://www.research.manchester.ac.uk/portal/files/56078084/pldi_16.pdf https://www.research.manchester.ac.uk/portal/files/56078084/...
- lproven 6y agoSo I have been informed, in some detail, over on Lobste.rs. I am glad to hear it. I like this little OS and I want to see it survive!
- wk_end 6y agoMaybe so, but I'd imagine most of the legacy 32-bit apps you'd be running in emulation here on your 64-bit RISC OS system are from the late 80s (or maybe the early-to-mid-90s), doing those late 80s things.
- pjmlp 6y agoPlenty of them actually are. A rusty Amiga 2000, with Internet connection could handle like 80% of the stuff I use my 2009 laptop for.
- ilaksh 6y agoI saw some YouTube videos of RISC OS running on Pi.
- lproven 6y ago[Author here] I have RISC OS running on a Pi, and it's not the first one I've had, either. https://twitter.com/lproven/status/1310304554395860996 https://twitter.com/lproven/status/1310304554395860996 http://blog.tynemouthsoftware.co.uk/2015/12/day-8-zx-spectrum-lmt-68fx2-case-with.html http://blog.tynemouthsoftware.co.uk/2015/12/day-8-zx-spectru... I don't just make this stuff up, you know. :-) I still have my A305, too, and an A5000 as well.
- marktangotango 6y agoGameboy advance emulators emulate 32bit arm, plenty of those around.
- qwerty456127 6y agoDon't forger the fact 187.5 times the frequency is not the only improvement. Today you also have 4x the cores, 8x the bits and hardware 4Kp60 HEVC en/de-coding. There probably are more things (like AES encryption, linear algebra and FPU) hardware-accelerated, I don't really know. This way your emulated Archimedes can probably do much much more than it was supposed to.
- lsllc 6y agoRISC OS is written mostly in ARM assembly, but it's a pretty complete (if dated) OS. I think it would be interesting to convert the sources to LLVM-IR and then abstract the hardware specific parts giving you a cross platform version of RISC-OS. Yeah, it'd be a lot of work ... but I think it'd be very cool. Why? 25 years ago there were dozens of OS's: AIX, Ultrix/OSF-1/Tru64, HP/UX, DG/UX, SCO (yuck), MS-DOS, Dynix/PTX, Solaris/SunOS, Windows, MSDOS, Mac, VMS, RISC-OS, Amiga, BeOS etc. etc. Now we're down to a handful of OSs with a large amount of computing now converging on Intel/Linux -- FWIW, I have nothing against Linux, I've used it since the early Slackware / pre 1.0 kernel days. But I do believe competition is a good thing and the current trend for OS (and processor) convergence is worrying to me. I'd like to see more innovation and diversity in this space.
- makapuf 6y agoListing some I know of: linux windows macos freebsd redox fuchsia ios android(sharing the kernel but sufficiently different from linux) chromeos plus many more experimental but available os
- saagarjha 6y agoChrome OS is Linux too.
- pjmlp 6y agoChromeOS uses Linux kernel, userspace has nothing to do with Linux. Even Crostini and ARC++ execute inside their own VM alongside their own kernel flavour. With Google turning the Web into ChromeOS, it matters even less, given how many OSes Chrome runs on.
- lproven 6y ago• linux <- an xNix (DEC PDP-7/PDP-11 OS) • windows <- modernised VMS (DEC VAX OS, the 32-bit PDP-11) • macos <- xNix • freebsd <- xNix • redox <- experimental, unfinished, no apps, xNix-like • fuchsia <- xNix in Go • ios <- basically macOS, an xNix • android <- a weird Linux • chromeos <- Linux That's 2 so far. 2.5 if I'm being generous. Do keep going, would you?
- ilaksh 6y agoWhenever I see RISC OS I always assume it's something for RISC V. I know this is not about that actually, just makes me think about it. But obviously it's for original RISC i.e. ARM. But anyway I still wonder if something like RISC OS could work on RISC V. I saw a youtube demo of someone running RISC OS on Raspberry Pi and it was very snappy. Something older like that has had less time to acquire features (that can slow it down or just be bloat). Besides eliminating bloat, I feel like RISC V is an opportunity to start with some new assumptions. So I am interested to hear how operating systems and software evolve for it. Linux is great but I believe that there is always room for a fresh approach after a few decades. So I wonder if things like Fuchsia or MirageOS or new Rust things etc. will be targeted to RISC V.
- ithkuil 6y ago> But obviously it's for original RISC i.e. ARM. Not sure if you actually mean that, but to me it sounds like you're implying that ARM is the "original RISC". The first RISC processor was called RISC-I and came out of Berkeley research in 1981. Around the same time came out the MIPS cpu, from Standford university, by a group who shortly after founded a company that by 1985 commercialized the first RISC CPU, the R2000. ARM, SPARC and PA-RISC came out just about the same time. The ideas were brewing for some time, but I think it's safe to say historically that the name "RISC" was not invented by ARM and that the R in ARM references a pre-existing term that has been developed at Berkeley.
- ncmncm 6y agoThe original RISC was the IBM 801, in ~1975, or arguably even the CDC 6600 in 1965. It is hard to identify anything that originated in the RISC-1.
- ithkuil 6y agoDidn't register windows originate at Berkeley? Sure, the IBM 801, the CDC 6600 and others were forerunners, but it was the Berkeley research project that popularized the acronym IIRC.
- 6y ago
- robin_reala 6y agoThanks to Castle's mysterious one big customer it has survived into its fourth decade. I’d previously missed this piece of lore. Anyone got any more info on it? I’m trying to picture what critical system built on RISC OS would have required ongoing maintenance and am coming up blank.
- rbirkby 6y agoGot to wonder whether it’s something like ncipher/Thales due to the van someren/aleph1 connection.
- ajb 6y agoDon't know, but there was a mysterious entity that nearly bought the rump of Acorn IIRC to keep producing RiscPCs. Due to some fumble the deal fell through. I vaguely remember it being some kind of media-tech company. Probably the same mysterious entity.
- bobince 6y agoI'm guessing Eidos's Optima video editing system? That was the last of the major RISC OS users as I remember it.
- zozbot234 6y ago> It's too late for virtual memory, and we don't really need it any more -- but the programming methods that allow virtual memory, letting programs spill over onto disk if the OS runs low on memory, are the same as those that enforce the protection of each program's RAM from all other programs. Strictly speaking, I don't think this is true - virtual memory and process-based memory protection are separate issues. One could have a single-address-space OS where physical memory is identically mapped in each process' address space, while still preserving memory protection. A privileged process in such an OS might effectively be exempt from memory protection altogether, which would provide compatibility for legacy apps.
- AlexanderDhoore 6y agoThat's the difference between an MMU and MPU. The first (MMU) adds virtual memory to the story, while the second (MPU) simply protects certain areas of memory. https://www.geeksforgeeks.org/whats-difference-between-mmu-and-mpu/ https://www.geeksforgeeks.org/whats-difference-between-mmu-a...
- lproven 6y ago[Author here] OK, I will give you that one. :-) But they are at least related concepts, no?
- asveikau 6y agoIt was weird to me that you said nobody needs virtual memory. On Unix, any time you mmap() or fork(). And loading code from disk looks very similar to the former.
- lproven 6y agoIt's an implementation detail of one type of OS. I am interested in the bigger picture. See my FOSDEM talk for more: https://liam-on-linux.livejournal.com/69099.html https://liam-on-linux.livejournal.com/69099.html
- adrianmsmith 6y ago> No memory protection or hardware-assisted memory management This isn’t true. There are many modern features missing from RISC OS but memory protection isn’t one of them. Each process sees its memory at the same logical address, it doesn’t have any way of accessing other process’ memory. The process’ memory starts at the address 0x8000. http://www.riscos.com/support/developers/riscos6/memory/logicalmemorymap.html http://www.riscos.com/support/developers/riscos6/memory/logi...
- mattbee 6y agoFrom - err - memory, the OS used some of the memory protection in hardware, but it didn't use it with security in mind. I'm pretty sure an application could rewrite important kernel tables below &8000. And if you were using any shared libraries, these were all implemented as kernel modules, with no guard rails. So it was kinda safe against some accidental access errors, but not at all a secure environment, and definitely possible to blow up the whole machine.
- icedchai 6y agoStill better than the Amiga, where their was no memory protection at all. Basically the entire OS was built on sharing memory between processes through message passing...
- timthorn 6y agoPaul Fellows, mentioned by reference in the article as giving the talk on writing RISCOS, presented again at Virtual ABug earlier in the Summer. The talk is online here: http://abug.org.uk/index.php/2020/07/04/paul-fellows/ http://abug.org.uk/index.php/2020/07/04/paul-fellows/
- ngcc_hk 6y agoWhat is the point of this discussion for others not in the ecology?
- lproven 6y ago[Author here] "Progress, far from consisting in change, depends on retentiveness. When change is absolute there remains no being to improve and no direction is set for possible improvement: and when experience is not retained, as among savages, infancy is perpetual. Those who cannot remember the past are condemned to repeat it." -- George Santayana (The Life of Reason: The Phases of Human Progress)
- qz2 6y agoRISC OS is quite frankly dead in its current incarnation. And I say that as a somewhat prolific Acorn customer in the 80s and 90s. It was after all a quick hack because they weren’t going to deliver ARX. Some of the impedance mismatches between the OS and everything else in the universe are glaringly irritating today such as paths and file type metadata. But a lot of the better ideas from the operating system should be carried forwards into something else. I’m not talking about sticking something on top of Linux but something completely different. Perhaps a resurrection of ARX and the UI concepts from RISC OS would be interesting.
- mattbee 6y agoI did the fun part of a RISC OS emulator 20 years ago - http://riscose.sourceforge.net/ http://riscose.sourceforge.net/ - i.e. WINE but for RISC OS applications. It got as far as being able to run the RISC OS C compiler, compile and run its own output for a few command line applications. But then we got to the stage of needing a test suite. Then my friend & collaborator on the project (Chris Rutter) died at the age of 19, then I finished college, had to find work and lost most of my RISC OS connections & nostalgia. There was definitely a rich seam of RISC OS software in 2000 that Linux desktop could have used - great text editors and word processors and Sibelius. But Linux got most of that pretty fast. Also I don't think RISC OS would have escaped the trap of most desktop OSes - that a desktop OS with native applications became a niche, expensive taste. By 2010 most desktop computer users were looking for a host for a web browser, and RISC OS itself is still spectaularly unsuited to that - hostile code, multithreading, support for proprietary blobs (at least in 2000) etc. etc. That doesn't stop me missing it though!
- blippage 6y agoI see RISC OS has having one particular advantage: cooperative multitasking. You can basically turn it into a gigantic MCU with proper interrupts and timing. It doesn't seem like it's a niche others are interested in, though. Get a git client and GCC working with it and you have a pretty nifty real-time development platform.