Talk:RISC OS
From Wikipedia, the free encyclopedia
Contents |
[edit] Early discussions
"...since a minor 24-bit ARM CPU..." - should that be 26-bit? Not fixed as I don't know. -- S
- Yes, it should be 26-bit. But should it say the function was removed in the XScale or simply changed/made to a 32-bit function? I don't know enough about ARM internals myself to give an answer. Crusadeonilliteracy 13:51, 4 Nov 2003 (UTC)
-
- Originally there was only 26bit addressing (24 bits for address in PC, but ARM instructions are always aligned to 4 bytes), then with ARM6 they introduced a 2nd mode, 32bit addressing. Later they invented Thumb mode, which is mutually exclusive to 26bit mode. StrongARM had 26bit, XScale doesn't. mavhc
Two similar projects, Impulse and Eidos's Phoenix, both stalled.
- What is this Eidos Phoenix? The only mention I can find of it is of a game by Eidos (what has this to do with RISC OS?) Crusadeonilliteracy 04:32, 22 Mar 2004 (UTC)
Eidos was originally a company specialising in Acorn-based video editing solutions. Only later did they become famous as a non-Acorn games publisher! Yes, it is the same Eidos that published Tomb Raider.
- The only RISC OS thing called Impulse I know of is Computer Concepts' pre RISC OS OS, which then became part of their applications mavhc
The article says RISC OS had no memory protection. It didn't have `full' memory protection, but AFAICR there was a limited degree of protection - all 'normal' applications appeared to be running at the same addresses in memory, so it took special actions to read or write to another application's memory. This didn't protect against a malicious application, but I think it did mean a buggy application couldn't corrupt the memory of another one under normal circumstances. I could well be wrong, hence putting this in talk rather than the article. --Zorn 08:38, 23 Jul 2004 (UTC)
- I've added some info, what do people think? mavhc
[edit] Screenshot, anyone?
Anyone got a screenshot? I think it'd add to the article. Lupin 08:56, 23 Jul 2004 (UTC)
[edit] Clean Up
Can the user who added the clean up tag, or anyone else please specify what they see as needing to be done. Andrewduffell 18:30, 30 November 2005 (UTC)
[edit] Closed source
I realised that it was closed-source and that the opening process was not an opening process but a person developing the same system api...but it was corrected before I corrected it...lol 213.189.165.28 16:20, 22 March 2006 (UTC)
[edit] Further talk
I have moved the Talk into chronological order - please add new talk sequentially at the bottom of this page - bottom posting in true RISC OS tradition :-)TerriersFan 07:29, 16 June 2006 (UTC)
[edit] ROLF
Is this worth to add to article? --Yonkie 10:49, 2 October 2007 (UTC)
[edit] Fair use rationale for Image:AcornArthur110desktopsmall.png
Image:AcornArthur110desktopsmall.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
