Dear Aneesh V,
In message 4DFA0759.2060606@ti.com you wrote:
Can you please extend this to show the SoC/board directories etc. I guess they will go under spl/ and not under each media.
Correct, i. e. please add for example:
spl/board/freescale/mx31pdk/ spl/board/freescale/mx31pdk/Makefile ...
I thought we were going to have cpu directory SoC directory etc in this directory structure.
If needed, yes. This example showed a board directory.
Can we not use the objects that get normally built, with the existing Makefiles?
But where do you add the reference to SoC level and CPU level object files? Which library do you make them part of? I thought the board level Makefile was meant only to build the board specific library.
Sorry, I don;t understand your questions (because I don't understand which problem you see).
Yes, the board directories will contain only board specific stuff.
For example, let's say we have board 'a' and 'b' of same SoC(soc). Unless we have a SoC directory we may have to do something like this.
Why should we not have a SoC dir?
Also, at least some files will have to be built separately for SPL because they have conditional compilation with CONFIG_PRELOADER kind of flags.
Please let's check where this is needed, and how we can handle this. I'd really like to get rid of this symlinking.
One case is start.S. We need a simplified start.S for SPL(no relocation, no interrupt handling etc).
OK.
There are places where CONFIG_PRELOADER is used today. But maybe, these could be avoided it we try.
We should carefully check these.
Best regards,
Wolfgang Denk