From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data
Date: Mon, 4 Jan 2010 19:40:31 -0500 [thread overview]
Message-ID: <201001041940.32282.vapier@gentoo.org> (raw)
In-Reply-To: <20100103195153.558C4EF5FF5@gemini.denx.de>
On Sunday 03 January 2010 14:51:53 Wolfgang Denk wrote:
> If I try to see trends in the development of U-Boot I notice a
> growing number of systems that boot from NAND flash, DataFlash or
> that come with on-chip ROM code to load images from SDCard and other
> storage media. Such systems cannot make real benefit from the
> original design of U-Boot, as here U-Boot is inherently a
> second-stage boot loader which gets loaded by some other means. Even
> for NAND booting systems where we have the NAND boot code included
> within the U-Boot source tree we often cannot share much of the code
> between the primary and the secondary loader stages as there are
> usually tight restrictions on the maximum size for the primary loader
> image. Here a sharper separation of "primary" and "secondary" boot
> code within U-Boot would be benefical.
>
> I feel (but this is really just a feeling, and I definitely would like
> to hear what others think about this!) your PIC changes would be (or
> have been) useful for the former usage mode, but they come at a pretty
> heavy cost as they are really invasive to the code. For the second
> usage mode they are not usable, or at least not useful. This makes me
> wonder if we really should continue to work in this direction.
the Blackfin processors are going the direction of an on-chip ROM handles
loading from some storage (nor/nand/spi/usb/uart/sd/whatever) into RAM. there
really isnt any usage model of executing in NOR for some time before running
out of RAM. so generally, all this additional support is seen largely as
overhead on Blackfin parts since there isnt any need/desire for them.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100104/f8e4df11/attachment.pgp
next prev parent reply other threads:[~2010-01-05 0:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 15:08 [U-Boot] [PATCH 0/4] Make u-boot true PIC for ppc Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 1/4] ppc: Add const void *link_off(const void *addr) Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 3/4] Use LINK_OFF in enviroment too Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 4/4] ppc: Make mpc83xx start.S relative Joakim Tjernlund
2009-12-31 18:44 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Mike Frysinger
2010-01-01 1:39 ` Joakim Tjernlund
2010-01-01 6:18 ` Mike Frysinger
2010-01-01 16:29 ` Joakim Tjernlund
2010-01-02 3:14 ` Mike Frysinger
2010-01-02 18:17 ` Wolfgang Denk
2010-01-03 10:48 ` Joakim Tjernlund
2010-01-02 18:13 ` Wolfgang Denk
2010-01-03 10:33 ` Joakim Tjernlund
2010-01-03 19:51 ` Wolfgang Denk
2010-01-03 20:06 ` Albert ARIBAUD
2010-01-03 20:17 ` Wolfgang Denk
2010-01-03 20:41 ` Albert ARIBAUD
2010-01-03 21:07 ` Wolfgang Denk
2010-01-04 6:54 ` Albert ARIBAUD
2010-01-03 22:29 ` Graeme Russ
2010-01-05 20:20 ` Scott Wood
2010-01-05 22:11 ` Joakim Tjernlund
2010-01-06 21:02 ` Scott Wood
2010-01-04 1:08 ` Joakim Tjernlund
2010-01-05 0:40 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 18:01 [U-Boot] [PATCH 0/4] Make u-boot true PIC for ppc Joakim Tjernlund
2009-11-02 18:01 ` [U-Boot] [PATCH 1/4] ppc: Add const void *link_off(const void *addr) Joakim Tjernlund
2009-11-02 18:01 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Joakim Tjernlund
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=201001041940.32282.vapier@gentoo.org \
--to=vapier@gentoo.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