Magnus Lilja wrote:
Hi
2008/9/14 dirk.behme@googlemail.com:
From: Dirk Behme dirk.behme@gmail.com
Add assembly startup and sys_info common files
Signed-off-by: Dirk Behme dirk.behme@gmail.com
cpu/omap3/Makefile | 44 +++ cpu/omap3/config.mk | 36 +++ cpu/omap3/lowlevel_init.S | 360 +++++++++++++++++++++++++++++++ cpu/omap3/start.S | 522 ++++++++++++++++++++++++++++++++++++++++++++++ cpu/omap3/sys_info.c | 314 +++++++++++++++++++++++++++
Is omap3 is a cpu? Isn't OMAP3 a SoC-family containing ARM Cortex-A8 CPUs and the directory therefore should be something like cpu/arm_cortexa8/omap3 or cpu/cortexa8/omap3?
Yes, from strict technical point of view you are correct. Cortex A8 is the 'CPU' and OMAP3 is the SoC.
But what do we win adding an additional directory layer cpu/arm_cortexa8/omap3? Let's assume we will see an additional Cortex-A8 core xxx in the future. Then we would have
a)
cpu/omap3/ cpu/xxx/
*or*
b)
cpu/arm_cortexa8/omap3 cpu/arm_cortexa8/xxx
What's better?
Anyway, I will do what is wanted here :)
If U-Boot maintainers want cpu/arm_cortexa8/xxx, I wonder if we could do this using git to move the files once the patches are applied? It seems easier to move the files to an other directory using git instead of flooding this list with new patches just to change directories. Any proposals?
Thanks
Dirk