From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] MX5:MX53: add initial support for MX53EVK board
Date: Fri, 17 Dec 2010 11:20:55 +0100 [thread overview]
Message-ID: <4D0B3987.3090604@free.fr> (raw)
In-Reply-To: <AANLkTik9SB4EP2YLMeCa-TNb4c7Z-2CPphLtBqfx6J8B@mail.gmail.com>
Le 17/12/2010 04:05, Jason Liu a ?crit :
> There is pretty much different with I.MX51 ROM, we will not use DCD
> data file to config the
> DDR script since ROM has the DCD size limitation and use the advance
> feature of what we
> called plug-in, the plug-in code must be in the first 2K of MMC card
> from 0x400 offset, that's
> why we need put this code section before start.S.
This implication is simply not true, as far as I can tell. You do need
to have this "plug-in" (will you explain in the end what it is exactly?)
in the first 2K of MMC; but that does not mean it has to be put in
u-boot and u-boot stored at start of MMC. You could just as well put the
"plug-in" alone in the first 2K and u-boot from the second 2K onward,
for all I understand:
> The plug-in code
> will be called by boot ROM
> to do DDR init first and copy u-boot to DDR and jump to _start to run it.
If it has to copy u-boot to DDR, then it should ne be part of u-boot.
> Does anyone of expert like you and Albert and Wolfgang tell me how to
> do it? It's very important for FSL
> coming many SOCs support, since we will use plug-in feature of boot ROM.
The first thing, I think, would be to get back to gathering your exact
requirements, and only those, as per your SoC specs. From what you say
of these, the requirements are not "have u-boot start in the first 2K of
MMC with the "plug-in' coming first", but "have some routine in the
first 2K of MMC, said routine assumed to do DDR init and payload copy";
and then, start from these reqs *only*.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-12-17 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 10:17 [U-Boot] [PATCH 0/5] Add support for Freescale MX53 Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 1/5] MX5: Add initial support for MX53 Jason Liu
2010-12-16 12:27 ` Wolfgang Denk
2010-12-17 3:20 ` Jason Liu
2010-12-16 13:34 ` Stefano Babic
2010-12-17 3:18 ` Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 2/5] serial_mxc: add support for MX53 processor Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 3/5] fec_mxc: " Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 4/5] mxc_i2c: " Jason Liu
2010-12-16 10:37 ` Heiko Schocher
2010-12-17 3:28 ` Jason Liu
2010-12-16 10:17 ` [U-Boot] [PATCH 5/5] MX5:MX53: add initial support for MX53EVK board Jason Liu
2010-12-16 10:48 ` Albert ARIBAUD
2010-12-16 12:23 ` Wolfgang Denk
2010-12-16 13:19 ` Stefano Babic
2010-12-17 3:05 ` Jason Liu
2010-12-17 5:41 ` Wolfgang Denk
2010-12-17 10:20 ` Albert ARIBAUD [this message]
2010-12-17 13:05 ` Stefano Babic
2010-12-20 5:19 ` Jason Liu
2010-12-20 6:52 ` John Rigby
2010-12-22 13:40 ` Jason Liu
2010-12-27 10:03 ` Stefano Babic
2010-12-20 6:52 ` Albert ARIBAUD
2010-12-16 23:04 ` Wolfgang Denk
2010-12-17 3:04 ` Jason Liu
2010-12-17 5:36 ` Wolfgang Denk
2010-12-16 12:25 ` [U-Boot] [PATCH 0/5] Add support for Freescale MX53 Wolfgang Denk
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=4D0B3987.3090604@free.fr \
--to=albert.aribaud@free.fr \
--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