From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v3] Fix initrd length miscalculation in bootm command when using a dtu
Date: Fri, 04 May 2007 11:02:53 -0500 [thread overview]
Message-ID: <463B592D.4040600@freescale.com> (raw)
In-Reply-To: <463B4191.1000706@smiths-aerospace.com>
Jerry Van Baren wrote:
> but I don't understand how to build an image with all three pieces in it
> (I tried to use the ":" in the -d source parameter and mkimage just got
> confused, couldn't find the files). Am I expecting too much??? Should
> I just be wrapping the three pieces individually and loading them
> separately? What exactly are you doing to test this, Timur?
The 'len' bug only shows up if both of these conditions are met:
1) You're booting an OF-enabled kernel (i.e. there's an fdt)
2) The fdt is wrapped in a dtu image (type IH_TYPE_FLATDT)
I didn't test having the fdt merged in with other entities in a combined image. I just
made a dtu and told the bootm command to use it. So if you want to test this code, I
think just wrapping the three pieces individually should be sufficient.
Part of the problem is that the code looks for a dtu image. If you combine all three
chunks into one image, then I don't know what the code will do, because the image type
won't be IH_TYPE_FLATDT.
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-05-04 16:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 22:30 [U-Boot-Users] [PATCH v3] Fix initrd length miscalculation in bootm command when using a dtu Timur Tabi
2007-05-03 23:47 ` Wolfgang Denk
2007-05-04 1:13 ` Timur Tabi
2007-05-04 8:28 ` Wolfgang Denk
2007-05-04 13:25 ` Timur Tabi
2007-05-04 13:46 ` Stefan Roese
2007-05-04 14:22 ` Jerry Van Baren
2007-05-04 16:02 ` Timur Tabi [this message]
2007-05-04 16:07 ` Jerry Van Baren
2007-05-04 15:57 ` Timur Tabi
2007-05-04 16:27 ` Wolfgang Denk
2007-05-04 16:32 ` Timur Tabi
2007-05-04 19:28 ` Wolfgang Denk
2007-05-04 19:40 ` Timur Tabi
2007-05-04 21:58 ` Timur Tabi
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=463B592D.4040600@freescale.com \
--to=timur@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 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.