Separate generic header usage from ARCH_MULTIPLATFORM
Get series with b4
b4 am 27974883.ZkGYubVYBp@wuerfelVersions newest first · linked by author and title
- v3 Latest posting 3/30 of 3 patches 0 repliesNew
- v3 posting 2/30 of 3 patches 0 repliesSuperseded
- v3 posting 1/30 of 3 patches 0 repliesSuperseded
Patches in v3 posting 3/3 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/3] Separate generic header usage from ARCH_MULTIPLATFORM
Quoted 4 lines · On Friday 07 June 2013 17:51:07 Jonathan Austin wrote:
Thanks for the expansion. I like that as an aim :). We should remember it'll still only make sense for platforms where PHYS_OFFSET/DRAM_BASE is the same - not sure how many that will be.
Yes, this is much less about the practical value of actually running a kernel that is built for multiple NOMMU machines than it is about doing things in a consistent way throughout the kernel.
Quoted 21 lines
I've had a play with keeping !MMU and
ARCH_MULTIPLATFORMselectable together, and of the fixes in your diff, only the following is required to get R7 booting on top of Vexpress:-----8<-------
arch/arm/Kconfig +1
-3@@ -289,8 +289,7 @@ choice config ARCH_MULTIPLATFORM bool "Allow multiple platforms to be selected" - depends on MMU - select ARM_PATCH_PHYS_VIRT + select ARM_PATCH_PHYS_VIRT if MMU select AUTO_ZRELADDR select COMMON_CLK select MULTI_IRQ_HANDLER ----->8--------
Quoted 1 line
It's nice too, because we don't need to add back Makefile.boot for vexpress.
Ok, excellent. We can probably mark that for -stable backports so we also get it in 3.8.x and 3.9.x.
Quoted 4 lines
The R7 support, nommu-fixes and MPU patches I sent before and which I hope to have merged for 3.11 (pull request for rmk coming shortly) can all work fine using this instead of the
NEED_NO_MACH_HEADERSseries (IE this series)....
Ok.
Quoted 5 lines
It would be cool, then, to have the small patch above in for 3.11 too if we're not too late and if nobody is against going down this route?
Arnd: would you like to send it as a patch to the list for consideration, or shall I take this on?
Please send a patch with a correct description.
Arnd