> > 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 :) I would love to see some documentation about the MMU setup for the ARM and how the tables are constructed. Since I started looking at the kernel in January I have been wondering why there is no documentation. Does anyone have some written notes that they are willing to share? I asked a question back in January on this subject and did not get a response. Scott McConnell unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED] ++ Please use [EMAIL PROTECTED] for ++ ++ kernel-related discussions. ++
- *TODO* Document the pseudo-ops (adr, ops) Zach Welch
- Re: *TODO* Document the pseudo-ops (ad... Philip Blundell
- Re: *TODO* Document the pseudo-ops (ad... Nicolas Pitre
- Re: *TODO* Document the pseudo-ops (ad... Russell King - ARM Linux Admin
- RE: *TODO* Document the pseudo-ops (ad... Jeff Sutherland
- Re: *TODO* Document the pseudo-ops... S A McConnell
- Re: *TODO* Document the pseudo... Paul Koning
- Re: *TODO* Document the pseudo... Russell King - ARM Linux Admin
- Self-documenting code (ha!... Zach Welch
- Re: Self-documenting ... Russell King - ARM Linux Admin
- Re: Self-document... Zach Welch
- Re: Self-docu... Russell King - ARM Linux Admin
- Re: Self-docu... Paul Koning
- Re: Self-docu... S A McConnell
- Re: Self-docu... Wookey
- Re: Self-docu... Russell King - ARM Linux Admin
