We're almost ready!
The base instruction set is now described, and we're on our way!
Okay, a little slower than I'd have liked, but getting there! ☺
ARMwiki is always looking for user contributions. If you have anything to add, please do. To help spark your creative juices, please browse the list of pages that have not yet been written that are cited by existing pages. When writing pages, please follow the style guide.
Please note: You must be a registered user with email address confirmed in order to create or edit content.
Assembler programming on the RaspberryPi
Don't hold your breath.
I plan to get a Model B (that's the more-memory-plus-ethernet version), but I plan to do so when all the madness has calmed down. I do plan to talk about it here and on my blog, plus cut some code in assembler. I also plan to do this under RISC OS once the port is available. Remember, the cool thing about the RPi is that you can switch personality (Linux, RISC OS etc) simply by changing the image on the SD card. This, my friends, gives us the ability to do something quite unique - to create something to run directly on the RPi (as in, a mini-OS of sorts). This is one of many avenues I'd enjoy exploring and I hope you're willing to come along for the ride!
However, we're still in Crazy/Awesome time so I'm just going to back off from RPi related stuff for the moment. Once they're available reliably, then it's something we can play with!
There is no mechanism for you, the user, to explicitly "consent" to having cookies stored. However, if you have come here as an anonymous user, no cookies will have been placed on your machine. It is only when you create an account or login that the cookie is required. Therefore, it will be assumed that logging into ARMwiki is giving consent to having ARMwiki manipulate and store its own cookies on your computer.
Four cookies are stored, all beginning with irreleva_mysql followed by a bunch of numbers. This is a reference to the underlying database upon which ARMwiki is based. The cookies are Token, UserID, UserName, and session. Their function should be clear from the names. Check what cookies are being stored on your computer (this is a how-to, not some sort of script).
ARMwiki does not contain embedded advertising, therefore there are no issues with third-party cookies.
You may read the full (and rather boringly verbose) directive at:
If you wish to view and use ARMwiki securely, you can connect via https://www.heyrick.co.uk/armwiki/ - but please note that your browser will warn you of a security problem, and that you will need to set an exception (refer to your browser's documentation for instructions). This is because HeyRick uses a generic security certificate in order to provide encryption. It does not guarantee that I am who I say I am, or anything like that. As I am not selling anything or requesting loads of personal details, this is seen as a workable compromise in order to allow safe use of ARMwiki in places where eavedropping could be a potential issue (schools, public WiFi hotspots, etc).