Hi,
On Fri, 24 Sep 1999 [EMAIL PROTECTED] wrote:
>
> No, and you don't need to. The idea is:
>
> 1. Kernel is loaded (without caches or MMU)
> 2. Kernel head-armv.S code sets up enough to get the kernel C code
> running.
> 3. paging_init() and friends set up all the mappings required for
> the architecture. At this point, the machine_is_xxx() macros
> are workable.
>
> This seems to be a re-occuring problem. head-arm?.S is not supposed to
> contain all the setup code, and MUST NOT be used for that purpose!
>
> You will need to register architecture numbers to use the machine_is_xxx()
> stuff - read the stuff in Documentation/arm.
>
I realize this, and I plan on registering architecture numbers soon.
But what I am referring to when I talk about the memory maps is the
#define of MAPPING in the variosu arch/arm/mm/mm-*.c files, specifically
the Footbridge case where you have host mode and add-in mode. In our
hardware, we have a board with 5 SA-110's on it, one with an ethernet
chip, the other 4 communicating with themselves and the 'host' SA-110
via PCI. Now, each one has a slightly different memory map. Instead of
having to know at compile time what MAPPING is defined as, I changed
things around so at runtime it can figure out this information.
I agree with everythign else you mention above, however. The
head-armv.S stuff should be generic, and I'm moving a lot of my changes
from there into firmware.
--
Kyle Mestery | StorageTek's Storage Networking Group
[EMAIL PROTECTED] | http://www.freebsd.org/
[EMAIL PROTECTED] | http://www.netwinder.org/
Protect your right to privacy: www.freecrypto.org
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
