From: Ulf Samuelsson <ulfs@dof.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Adding multiple MIPS based SoCs?
Date: Tue, 22 Aug 2006 16:58:16 +0200 [thread overview]
Message-ID: <00a201c6c5fc$13e4a5a0$104765d5@atmel.com> (raw)
In-Reply-To: 20060822144812.991A3353A61@atlas.denx.de
>> 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 at dof.se,
since it will be routed to my GSM phone.
My email address is ulf at atmel.com
Best Regards
Ulf Samuelsson ulf at 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 at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com
Best AVR link: www.avrfreaks.net
next prev parent reply other threads:[~2006-08-22 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 14:24 [U-Boot-Users] Adding multiple MIPS based SoCs? Hans Zuidam
2006-08-22 14:48 ` Wolfgang Denk
2006-08-22 14:58 ` Ulf Samuelsson [this message]
2006-08-22 15:42 ` Wolfgang Denk
2006-08-22 15:25 ` [U-Boot-Users] tools for NIOS/Microblaze/ Ulf Samuelsson
2006-08-23 7:45 ` [U-Boot-Users] Adding multiple MIPS based SoCs? Hans Zuidam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00a201c6c5fc$13e4a5a0$104765d5@atmel.com' \
--to=ulfs@dof.se \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox