We are in the process of adding our internal U-Boot changes to the latest public U-Boot. One "problem" we face is that we have multiple SoCs each with a (slightly) different MIPS core variant. Adding them all under cpu/mips and #ifdef-ing start.S does not seem appealing. Our preference is to have a separate cpu directory for each SoC, more or less as is done for the MPCs. Any ideas, suggestions? Thanks in advance.
There is no general answer so such a vague question. If there are inded only slight differences, separate directories would probably contain mostly duplicated code, which is unacceptable. Then rather have a few (I really mean *few*) #ifdef's, or call some private init function which can be implemented in a board / SoC specific way.
Have been thinking of similar problems:
The README file says that the board directory needs to have a board*.c u-boot.lds flash.c
Since the flash.c is in many cases identical, does it not make more sense to have it in the drivers directory, and then call it something more specific like:
at45dbxxx.c at49bvxxx.c
Then anyone can use these files for their board, instead of duplicating the file.
Best regards,
Wolfgang Denk
Please do not send mails or "reply" to ulfs@dof.se, since it will be routed to my GSM phone. My email address is ulf@atmel.com
Best Regards Ulf Samuelsson ulf@atmel.com Atmel Nordic AB Mail: Box 2033, 174 02 Sundbyberg, Sweden Visit: Kavallerivägen 24, 174 58 Sundbyberg, Sweden Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29 GSM +46 (706) 22 44 57
Technical support when I am not available: AT89 C51 Applications Group: mailto:micro.hotline@nto.atmel.com AT90 AVR Applications Group: mailto:avr@atmel.com AT91 ARM Applications Group: mailto:at91support@atmel.com FPSLIC Application Group: mailto:fpslic@atmel.com Best AVR link: www.avrfreaks.net