Main Page

From ARMwiki
(Difference between revisions)
Jump to: navigation, search
(Edited top notice.)
(Added Raspberry Pi note. Formatting sucks for entry page, I probably ought to make a 'news' page for this sort of stuff.)
Line 34: Line 34:
  
 
<tr><td colspan=2>
 
<tr><td colspan=2>
 +
== Assembler programming on the RaspberryPi ==
 +
Don't hold your breath.<br>
 +
I'm not being rude. The first batch of RPis sold out in seconds, and I think it was Farnell whose site fell over for a while, and when back up, registered something like 300 requests for pre-order or info ''per second''. Like... wow.<br>
 +
I mean, people dream of coming up with a product that makes such an impact. Few achieve it. Practically nobody achieves it with a product as nerdy as a cheap processor board. But, there ya go, it happened. Not the USB-stick thing that may or may not have been vapourware a year or so back, but a long hard slog with some insanity and genuis along the way to bring something to all who wanted a Beagle but couldn't justify the price.
 +
 +
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!
 +
 +
 
== Cookies! ==
 
== Cookies! ==
 
[[image:Cookies.jpeg|right]]With reference to the recent European Directive on the use of cookies, please be aware that ''ARMwiki'' may use cookies to uniquely identify you. This is necessary as registered users log in, have preferences, and the ability to edit pages. Cookies will be required to manage these activities.
 
[[image:Cookies.jpeg|right]]With reference to the recent European Directive on the use of cookies, please be aware that ''ARMwiki'' may use cookies to uniquely identify you. This is necessary as registered users log in, have preferences, and the ability to edit pages. Cookies will be required to manage these activities.
Line 39: Line 49:
 
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.'''
 
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. [[CheckForCookies|Check what cookies are being stored 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. [[CheckForCookies|Check what cookies are being stored on your computer]] (this is a how-to, not some sort of script).
  
 
Feel free to wipe off the cookies at any time, or to configure your browser to retain cookies from this site on a session-by-session basis. It will not hurt anything, all you'll need to do is log in again.
 
Feel free to wipe off the cookies at any time, or to configure your browser to retain cookies from this site on a session-by-session basis. It will not hurt anything, all you'll need to do is log in again.

Revision as of 06:48, 7 March 2012

ARMwiki - ARM processor wiki
articles and information relating to the ARM processor


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! ☺

Contents

IntroductionAn introduction to the ARM, and ARMwiki.
The ARM familyARM processor types/families.
Instruction setThe ARM instruction set.
Using RISC OSARM programming under RISC OS.
Using Linux & WindowsARM programming under Linux and Windows.
TutorialsStep by step tutorials.
Example codeExample code (currently predominantly RISC OS).
Related sitesOther ARM-related sites and resources.

Content wanted!

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'm not being rude. The first batch of RPis sold out in seconds, and I think it was Farnell whose site fell over for a while, and when back up, registered something like 300 requests for pre-order or info per second. Like... wow.
I mean, people dream of coming up with a product that makes such an impact. Few achieve it. Practically nobody achieves it with a product as nerdy as a cheap processor board. But, there ya go, it happened. Not the USB-stick thing that may or may not have been vapourware a year or so back, but a long hard slog with some insanity and genuis along the way to bring something to all who wanted a Beagle but couldn't justify the price.

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!


Cookies!

Cookies.jpeg
With reference to the recent European Directive on the use of cookies, please be aware that ARMwiki may use cookies to uniquely identify you. This is necessary as registered users log in, have preferences, and the ability to edit pages. Cookies will be required to manage these activities.

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).

Feel free to wipe off the cookies at any time, or to configure your browser to retain cookies from this site on a session-by-session basis. It will not hurt anything, all you'll need to do is log in again.

Alternatively, you may block cookies from ARMwiki (exactly how depends upon your browser), but please be aware that your ability to interact with this site may be somewhat diminished without the use of cookies.

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:
    http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2009:337:0011:0036:En:PDF

Request for Content Removal

Encryption

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).

Personal tools
Namespaces

Variants
Actions
Navigation
Contents
Toolbox