From: Philip Balister <philip@balister.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Starting a patch for TI Davinci support
Date: Thu, 05 Jul 2007 10:27:38 -0400 [thread overview]
Message-ID: <468CFFDA.7050809@balister.org> (raw)
In-Reply-To: <000001c7b80a$9986a3b0$821ba8c0@Emea.Arm.com>
Peter Pearse wrote:
> Philip
>
> Have you checked the previous DaVinci patches
> - see http://blog.gmane.org/gmane.comp.boot-loaders.u-boot
Sorry for the delay replying, I have been on vacation.
I have looked at the one one from koi8. While I there is a lot of good
content there, I have trouble with the configuration method. Basically,
he supports three boards by #fidef'ing based on a #define of a board
type. The ifdef'ing logic gets fairly involved and I am concerned this
method will not scale to a large number of different boards based on the
Davinci processor.
I guess the first issue we need to resolve for Davinci support is what
it the proper way to support a collection of boards that use the same
underlying hardware, but have different memory architectures (ie NAND
versus NOR), different PHY interfacesm but also have some shared code
also. The ARM processor in the Davinci is an ARM926ejs, which is also
shared by some of the OMAP line also.
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070705/5fbf005c/attachment.bin
prev parent reply other threads:[~2007-07-05 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 14:23 [U-Boot-Users] Starting a patch for TI Davinci support Philip Balister
2007-06-26 15:56 ` Peter Pearse
2007-07-05 14:27 ` Philip Balister [this message]
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=468CFFDA.7050809@balister.org \
--to=philip@balister.org \
--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