From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap: spl: fix build break due to changes in FAT
Date: Tue, 4 Oct 2011 11:17:42 -0500 [thread overview]
Message-ID: <4E8B31A6.6080104@freescale.com> (raw)
In-Reply-To: <20111004153838.3CD0018E5B3A@gemini.denx.de>
On 10/04/2011 10:38 AM, Wolfgang Denk wrote:
> I think it is a bad idea to go this way.
>
> We should face the fact that SPL code is running before proper
> relocation to RAM, and thus there are certain limitations.
>
> Certain parts of the code, including file system code, has not been
> written with such limitations in mind. It makes use of functions that
> are not available in SPL code, or of features that are not available
> in SPL code (like a heap, or a virtually unlimited stack).
>
> You may be lucky here, and your test cases with the FFAT code may
> actually work. But I would not bet on it.
>
>
> U-Boot has not been designed to run complex code like file systemes
> before relocation, and SPL code _is_ before relocation.
SPL has its own relocation. If it were under the same restrictions as
normal pre-relocation U-Boot, where would it load an image to?
All SPL really is, is some makefile infrastructure to produce a second,
special-purpose U-Boot image. The degree to which it is stripped down
depends on the requirements of the particular target.
-Scott
prev parent reply other threads:[~2011-10-04 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 18:50 [U-Boot] Master branch broken for omap4_panda (SPL_BUILD) Aguirre, Sergio
2011-10-04 14:15 ` Aneesh V
2011-10-04 14:51 ` Wolfgang Denk
2011-10-04 15:37 ` Aneesh V
2011-10-04 18:05 ` Wolfgang Denk
2011-10-05 9:42 ` Aneesh V
2011-10-07 1:40 ` Tom Rini
2011-10-07 5:27 ` Wolfgang Denk
2011-10-04 15:11 ` [U-Boot] [PATCH] omap: spl: fix build break due to changes in FAT Aneesh V
2011-10-04 15:38 ` Wolfgang Denk
2011-10-04 16:00 ` Aneesh V
2011-10-04 16:17 ` Scott Wood [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=4E8B31A6.6080104@freescale.com \
--to=scottwood@freescale.com \
--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