[U-Boot-Users] Using tools/mkimage
wd at denx.de
Tue Aug 5 19:37:42 CEST 2003
In message <20030805163732.GA7011 at buici.com> you wrote:
> > I think it is the kernel you care about right? So run the same
> > kernel, once by wrapping it with a bootstrap loader into a zImage
> > file, and once by wrapping it with mkimape into an uImage file.
> Thought that is so, the value of using the same exact file in all
> instances superceedes technical superiority. Should this change for
> us, I'm certain that we'll embrace the u-boot way.
You _are_ using the same file, just wrapped differently.
> > What you are doing is bogus. "bootm" is meant to start images which
> > have the expected kernel interface. If you load a zImage file (let's
> > ignore for a moment that this makes no sense :-) you should use the
> > "go" command toi start it as this provides the interfqce for the
> > zImage bootstrap loader (i. e. none).
> Hmm. I'm not sure what you mean by 'the expected kernel interface'.
> According to the ARM source, the zImage bootstrap expects the same
> thing that the kernel expects r1 to contain an architecture ID and
Which actual board are we talking about?
> Yes. Of course. As I've stated above, the call interface appears to
> be OK. The parameters block differs only in that u-boot passes an
> initrd tag that is newer than the kernel understands. I have no
Which kernel version are you using?
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
There are some things worth dying for.
-- Kirk, "Errand of Mercy", stardate 3201.7
More information about the U-Boot