From: Paul B. Henson <henson@acm.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] freescale imx bootlets vs u-boot for i.MX28
Date: Mon, 18 Mar 2013 17:59:19 -0700 [thread overview]
Message-ID: <5147B867.5000704@acm.org> (raw)
I'm working on a fairly simple project that needs to boot linux from
NAND on a freescale i.MX28 platform, and there's a lack of consensus on
how to handle the boot loader.
One option would be to simply use the stock freescale imx bootlets to
load the linux kernel, the other to leverage u-boot.
Clearly u-boot has a lot more functionality and feature set than the
basic bootlets, but for this project there's really nothing more needed
from the bootloader then to load the kernel from nand and pass control
to it, and one faction thinks it would be more efficient just to use the
bootlets rather than adding u-boot to the mix.
Assuming a scenario where the boot loader is expected to just load a
linux kernel and nothing else, what advantages would u-boot provide over
the basic bootlets? I know that on some platforms the IPL isn't very
good at handling bad blocks or other issues, and having it load a very
small u-boot which would then be used to load the larger kernel is
beneficial, but I'm not sure if that's the case for the bootlets.
I'd appreciate any opinions or reasoning I could take back to the team
to help make a decision, thanks?
next reply other threads:[~2013-03-19 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 0:59 Paul B. Henson [this message]
2013-03-20 14:47 ` [U-Boot] freescale imx bootlets vs u-boot for i.MX28 Wolfgang Denk
2013-03-20 23:16 ` Paul B. Henson
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=5147B867.5000704@acm.org \
--to=henson@acm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.