Re: *TODO* Document the pseudo-ops (adr, ops)

[Paul Koning]

>>>>> "S" == S A McConnell <[EMAIL PROTECTED]> writes:

 >>  There are some tricky things to watch out for, such as the pc
 >> always being 8
 S> bytes
 >> ahead of the current instruction, and manipulating the caches and
 >> MMU, the details of which are left for the reader to discover :)

 S> I would love to see some documentation about the MMU setup for the
 S> ARM and how the tables are constructed. Since I started looking at
 S> the kernel in January I have been wondering why there is no
 S> documentation.

You can get a lot from the StrongARM data book and the ARM
architecture manual.  In fact, it's hard to see how you can do
meaningful work in the ARM-specific code without having those two
books on your desk...

      paul

unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for           ++
++                        kernel-related discussions.                      ++