v7-M support using MULTIPLATFORM
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 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 v1 yet.
Cover letter [PATCH 0/3] v7-M support using MULTIPLATFORM
Hi Russell,
Quoted 21 lines · Russell King - ARM Linux
Quoted 11 lines · Uwe Kleine-K?nig
Quoted 10 lines · Russell King - ARM Linux
Quoted 4 lines · Uwe Kleine-K?nig
Hello,
this series makes it possible to benefit from the MULTIPLATFORM stuff also for my v7-M machine (that is not yet supported in mainline).
The big problem I have with this is that the single zImage project is forcing itself onto stuff like the small embedded stuff where it's not appropriate for it to be.
Quoted 8 lines
Quoted 3 lines
Much of the multiplatform infrastructure relies on the ability to do tricks with the MMU - placing various peripherals at known virtual addresses. Such tricks don't work on no-MMU platforms.
Actually it's not for the multi-platform ability itself I selected it for, but to benefit from other stuff that is currently only available for it, i.e. I don't need a Makefile.boot, I don't need some mach/ headers.
Quoted 6 lines
The only include file which MULTIPLATFORM itself hides is
mach/timex.h- the others are all optional wrt their individualNEED_xxx_Hconfigs. We should probably convertmach/timex.hto theNEED_xxx_Hstyle as well.As for not needing Makefile.boot, I guess we should allow the 'Image' target to work if there's no Makefile.boot but disable the rest.
Both suggestions sound fine for me.
Quoted 11 lines
Quoted 10 lines
Quoted 6 lines
NoMMU platforms are inherently much more restricted and specialised, and having multiplatform on them just doesn't make sense. Yes, it may give you the ability to increase compilation coverage, but will the resulting image even work on the platform you're trying to target, or will one of the other multi-platforms take over some settings and screw it for you - like the link address.
Well, the way things are suggested in my patches you can only select other v7m machines alongside the efm32 platform. The bets are much better there not to screw it for me. But of course I cannot proof this as there is only one Cortex-M3 type supported in my tree.
Quoted 5 lines
Hmm. So, is it possible to build for the EFM32 platform and a SAM3N in the same kernel? The SAM3N devices are Cortex-M3 CPUs, with major regions defined as flash in the bottom .5G, SRAM, external SRAM at
0x60000000, private peripherals at0xe0000000, which is where the system control block, system timer, nvic and so forth are located.
The block at 0xe0000000 is architecturally defined. Also flash at the bottom is quite usual I think. All M3 and M4 use the nvic as irq controller at a fixed address. So multi-arch on v7-M isn't as hard as it could be.
Quoted 10 lines
Quoted 4 lines
Right, but do we agree that it should be possible to create an XIP image for i.MX6? If so: You currently cannot, because i.MX6 isn't configurable without MULTIPLATFORM. Also in the times before MULTIPLATFORM XIP was special.
That's one of the consequences of pushing to multiplatform support - XIP has fallen by the way side as a result of this effort (it was discussed previously) and we had decided that almost no one uses it anymore and it would not be part of the multiplatform stuff. It was only really used by very few SA11x0 and PXA platforms anyway.
I assume that new machines using efm32 (or any other M3) that are targeted to run Linux will have bigger RAMs and so the XIP part will matter less here.
Quoted 5 lines
Quoted 4 lines
Already back than you could create a kernel for 2 (or more) different machines (sharing the same SoC family) with XIP enabled. That didn't necessarily made it work on both machines, maybe only one of them had NOR flash.
Quoted 8 lines
That's quite a different issue from enabling MULTIPLATFORM and then having a whole raft of completely different SoCs be configurable. For any one SoC, it will work if you program the kernel into memory starting at
XIP_PHYS_ADDR. The majority of platforms in any one SoC group will have memory available at a fixed location. For example, on SA11x0, you can almost guarantee that there's some kind of flash memory in flash bank 0, because that's how the system boots. Same for PXA.
In my eyes that's a poor excuse to drop XIP. Yes, it doesn't make sense in all configurations, but in some it does. So IMHO better allow it in all configurations than in none.
Quoted 12 lines
Quoted 12 lines
Quoted 11 lines
None of that is provided by the majority of multiplatform.
So, enabling the multiplatform
Kconfigon such specialist platforms is just opening up a huge can of worms. Why anyone thinks this is a good idea is way beyond me.Also think about the argument you're making. You need XIP kernel because you have limited RAM, but you're willing to enable multiplatform support which will allow you to build a kernel much larger than is necessary for your platform by including other platforms in it. Sorry, that's just stupid.
Quoted 5 lines
Quoted 2 lines
Right, it will allow me to build a much bigger kernel (but I don't need to). And it allows me a few more things (yes please).
"a few more things" - I count two things which you've mentioned so far, both of which can be sorted out. Anything else?
Nothing I'm aware at the moment. I will address your two suggestions soon. Still I wonder if going the multi-arch route is the right thing to do now that it is (still) easy. And if it's only because it matches what the MMU machines are doing and so uses more better tested stuff.
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |