> >into the arch/arm/kernel source pretty heavily. In my
> pursuit, I ran across
> >the 'adr' opcode several times. Being unfamiliar with the
> opcode, I looked
> >through the 'info' page only to discover the following message:
> >
> >*TODO* Document the pseudo-ops (adr, ops)
>
> "adr rN, label" loads the (run-time) address of `label' into rN. It
> actually translates to "add rN, pc, #(label - . - 8)" or
> something similar.
>
> p.
nop is another favourite. There is no ARM processor instruction for no
operation. My assembler translates "nop" into
"mov r0, r0" which essentially does nothing (the whole purpose of nop).
The more you work with the ARM processor, the more you will like it. There
are some tricky things to watch out for, such as the pc always being 8 bytes
ahead of the current instruction, and manipulating the caches and MMU, the
details of which are left for the reader to discover :)
//Jeff
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
