From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] Tegra: Medcom-Wide: Enable NAND and boot script support
Date: Thu, 14 Feb 2013 10:19:28 -0700 [thread overview]
Message-ID: <511D1CA0.5080100@wwwdotorg.org> (raw)
In-Reply-To: <1360828494-16207-2-git-send-email-thierry.reding@avionic-design.de>
On 02/14/2013 12:54 AM, Thierry Reding wrote:
> Boot script support brings Medcom-Wide in line with other Tegra boards.
> In order to enable booting a Linux kernel with initial ramdisk, also add
> support for the new FIT image type.
I don't care if you enable FIT on your boards, but I would like to point
out that there's no requirement to enable FIT just to support ramdisks.
bootz/bootm support separate files/locations/... for ramdisks if you
want, and I'm pretty sure I validated it worked once at least.
next prev parent reply other threads:[~2013-02-14 17:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 7:54 [U-Boot] [PATCH 1/4] Tegra: All Tamonten-derived boards use onboard NAND Thierry Reding
2013-02-14 7:54 ` [U-Boot] [PATCH 2/4] Tegra: Medcom-Wide: Enable NAND and boot script support Thierry Reding
2013-02-14 17:19 ` Stephen Warren [this message]
2013-02-14 19:23 ` Thierry Reding
2013-02-14 7:54 ` [U-Boot] [PATCH 3/4] Tegra: Plutux: " Thierry Reding
2013-02-14 7:54 ` [U-Boot] [PATCH 4/4] Tegra: TEC: Enable " Thierry Reding
2013-03-04 20:46 ` [U-Boot] [PATCH 1/4] Tegra: All Tamonten-derived boards use onboard NAND Tom Warren
2013-03-04 22:41 ` Thierry Reding
2013-03-04 23:26 ` Tom Warren
2013-03-04 23:39 ` Stephen Warren
2013-03-08 16:36 ` Tom Warren
2013-03-08 16:44 ` Tom Rini
2013-03-08 16:48 ` Tom Warren
2013-03-08 16:57 ` Tom Rini
2013-03-08 16:58 ` Tom Warren
2013-03-08 17:04 ` Tom Warren
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 14:52 Thierry Reding
2013-04-03 14:52 ` [U-Boot] [PATCH 2/4] Tegra: Medcom-Wide: Enable NAND and boot script support Thierry Reding
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=511D1CA0.5080100@wwwdotorg.org \
--to=swarren@wwwdotorg.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