From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Regression due to: arm: Add Prep subcommand support to bootm
Date: Fri, 13 Apr 2012 08:07:33 -0700 [thread overview]
Message-ID: <20120413150733.GA9043@bill-the-cat> (raw)
In-Reply-To: <4F87085B.1090400@wwwdotorg.org>
On Thu, Apr 12, 2012 at 10:52:43AM -0600, Stephen Warren wrote:
> I just tried the latest u-boot/master, at commit:
>
> 3f0675d Merge branch 'marek.vasut at gmail.com' of
> git://git.denx.de/u-boot-staging
>
> This fails to boot a Linux kernel on my ARM Tegra board; the boot log is:
>
> ====================
> ## Booting kernel from Legacy Image at 00408000 ...
> Image Name: Linux-3.4.0-rc1-next-20120405-00
> Image Type: ARM Linux Kernel Image (no loading done) (uncompressed)
> Data Size: 2756424 Bytes = 2.6 MiB
> Load Address: 00000000
> Entry Point: 00000000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 01000000
> Booting using the fdt blob at 0x01000000
> XIP Kernel Image (no loading done) ... OK
> OK
> Loading Device Tree to 010fa000, end 010ff726 ... OK
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> Warning: Neither atags nor dtb found
> ====================
>
> If I revert commit 0a672d4 "arm: Add Prep subcommand support to bootm",
> then everything works fine again.
I don't see this on beagleboard so we'll need some more tracking down of
just how this broke tegra from you :( Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120413/dc274747/attachment.pgp>
next prev parent reply other threads:[~2012-04-13 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 16:52 [U-Boot] Regression due to: arm: Add Prep subcommand support to bootm Stephen Warren
2012-04-13 15:07 ` Tom Rini [this message]
2012-04-13 20:19 ` Stephen Warren
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=20120413150733.GA9043@bill-the-cat \
--to=trini@ti.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