[EMAIL PROTECTED] writes:
> Have you changed it to do what I mentioned above, that is, figure out
> it's memory map at runtime vs. compile time? The reason I need this is
> because we have 10 different types of memory maps depending on what
> processor we are running on, and compilign 10 different kernels is a
> pain. Letting the kernel pick this at runtime is nicer in our case.
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.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
