Hi Everyone, I'm looking for wisdom/understanding about IMAP_ADDR on PPC 8xx platforms.
In particular, I have an MPC885ADS board running "U-Boot 1.1.3 (Apr 19 2005 - 13:39:58)". It will boot neither 2.6.15 nor 2.6.16.11. After U-Boot decompresses the kernel, I get no kernel output at all; it just hangs. After some debugging, I think things go awry when the code starts dereferencing IMAP_ADDR as a direct pointer. IMAP_ADDR is defined to be 0xFF000000, but the MPC885ADS documentation says that the internal memory map is supposed to at 0x22000000. In addition, when I look at the bd_t pointer from U-Boot, it's saying that 0x22000000 is the correct address. We have a 2.6.11.7 kernel that successfully boots on this board. The port was done by another engineer who has moved on to another job. His port includes a patch that replaces all references to IMAP_ADDR with a global pointer that is initialized using io_remap() of the internal map value from the U-Boot bd_t structure. Why is this a problem for us and apparently not for anyone else on this list? Is no one else using U-Boot? Or does everyone else's U-Boot use 0xFF000000 instead of 0x22000000? Or do I have a different problem entirely? :-) While reading through the archives, I see that using IMAP_ADDR the way it is currently used is somewhat frowned upon anyway. Is this one of those things that we (the PPC Linux community) should fix the "right way" once and for all? I'm happy to submit a patch once I understand what the "right way" is... :-) Thanks!!! Walt Wimer TimeSys Corporation
