Re: [PATCH 0/4] Runtime constants: define (some) OMAP address bases at runtime rather than compile time for multiboot

[Dirk Behme <dirk.behme@googlemail.com>]

Paul Walmsley wrote:
> The OMAP2/3 kernel builds define several preprocessor macros for
> module base virtual addresses (e.g., OMAP2_CTRL_BASE).  These macros
> are substituted with virtual addresses at compile-time, depending on
> what OMAP architecture the kernel is built for.  This technique is
> simple and works well for single-OMAP kernels, but cannot be used to
> build a multi-OMAP kernel.
> 
> So, convert the users of these defines to use runtime-computed global
> variables where possible.  Where not possible (e.g., in static initializers), 
> use chip-specific preprocessor macros.  The global variables are set up
> early in the board-*.c files in the map_io() code, before almost everything 
> else.
> 
> This series must be applied after the SRAM patcher series posted earlier
> this week, since it relies on that code to set up register addresses in
> the assembly-language code at runtime.
> 
> This series converts SDRC, SMS, and System Control Module accesses.  
> Forthcoming patch series will convert PRCM and 32K sync timer register
> access.
> 
> Boot-tested on N800 and 3430SDP.  If someone out there could test on 2430SDP,
> that would be much appreciated.  Some day I'll get my hands on a  2430SDP :-) 
> 
> Comments welcome,

Patch 1/4 and 3/4 of this series still apply, but 2/4 and 4/4 have 
rejects. Could you check?

Many thanks

Dirk