From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot
Date: Wed, 23 Apr 2008 20:05:20 +0200 [thread overview]
Message-ID: <87skxcfnvj.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <010801c8a560$21c744d0$020514ac@atmel.com> (Ulf Samuelsson's message of "Wed\, 23 Apr 2008 18\:09\:48 +0200")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>> Author: jacmet
>> Date: 2008-04-23 06:03:53 -0700 (Wed, 23 Apr 2008)
>> New Revision: 21809
>>
>> Log:
>> u-boot: tools in target (mkimage, fw_printenv and fw_setenv)
>>
>>
Ulf> Why install mkimage in the target???
To create images and more importantly, to see the version info of
images in the flash (mkimage -l).
Ulf> It is used to create the linux kernel image so that U-Boot can load it.
Ulf> If you download a new image, I would expect it is already created
Ulf> using mkimage on the host.
Sure, but uImages are not just for kernels, E.G. the board I'm working
on has firmware for 2 fpgas in seperate uImages. It's handy to be able
to check the version info of the installed images under Linux, similar
to the imls u-boot command.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-04-23 18:05 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 13:03 [Buildroot] svn commit: trunk/buildroot/target/u-boot jacmet at uclibc.org
2008-04-23 16:09 ` Ulf Samuelsson
2008-04-23 18:05 ` Peter Korsgaard [this message]
2008-04-23 18:35 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-07 6:57 jacmet at uclibc.org
2009-02-04 23:15 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:04 jacmet at uclibc.org
2009-01-26 11:46 ulf at uclibc.org
2009-01-22 18:46 ulf at uclibc.org
2009-01-22 10:15 jacmet at uclibc.org
2009-01-21 15:49 jacmet at uclibc.org
2009-01-20 8:11 ulf at uclibc.org
2009-01-11 21:39 ulf at uclibc.org
2009-01-24 8:21 ` Peter Korsgaard
2009-01-24 10:55 ` Ulf Samuelsson
2009-01-24 11:43 ` Peter Korsgaard
2009-01-24 15:27 ` Dan Lyke
2009-01-08 14:58 jacmet at uclibc.org
2009-01-08 14:58 jacmet at uclibc.org
2009-01-06 14:16 ulf at uclibc.org
2009-01-06 14:26 ` Peter Korsgaard
2009-01-06 16:06 ` Ulf Samuelsson
2009-01-05 16:16 jacmet at uclibc.org
2009-01-05 16:12 jacmet at uclibc.org
2009-01-05 18:12 ` Ulf Samuelsson
2009-01-05 18:16 ` Ulf Samuelsson
2009-01-05 20:14 ` Peter Korsgaard
2009-01-05 20:12 ` Peter Korsgaard
2009-01-06 12:50 ` Ulf Samuelsson
2009-01-06 12:59 ` Peter Korsgaard
2009-01-05 15:52 jacmet at uclibc.org
2009-01-03 15:03 nkukard at uclibc.org
2009-01-03 0:02 ulf at uclibc.org
2009-01-03 20:46 ` Peter Korsgaard
2009-01-03 20:18 ` Ulf Samuelsson
2009-01-03 0:00 ulf at uclibc.org
2009-01-03 20:28 ` Peter Korsgaard
2009-01-03 20:37 ` Ulf Samuelsson
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-07-08 10:53 jacmet at uclibc.org
2008-07-04 22:18 ulf at uclibc.org
2008-07-07 13:27 ` Peter Korsgaard
2008-06-17 8:04 jacmet at uclibc.org
2008-06-13 13:46 jacmet at uclibc.org
2008-06-12 7:27 jacmet at uclibc.org
2008-06-11 13:07 jacmet at uclibc.org
2008-06-12 5:14 ` Hamish Moffatt
2008-06-12 7:28 ` Peter Korsgaard
2008-04-23 14:52 jacmet at uclibc.org
2008-04-23 14:59 ` Thiago A. Corrêa
2008-04-23 15:20 ` Peter Korsgaard
2008-04-23 16:22 ` Ulf Samuelsson
2008-04-23 17:35 ` Bernhard Fischer
2008-04-23 17:39 ` Ulf Samuelsson
2008-04-23 18:37 ` Bernhard Fischer
2008-04-23 18:29 ` Peter Korsgaard
2008-04-23 14:52 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 10:30 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
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=87skxcfnvj.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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.