From: Jim Thomas <jimthomasembedded@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] Persistent U-Boot environment variables under QEMU
Date: Sat, 13 Feb 2010 13:51:26 -0800 (PST) [thread overview]
Message-ID: <727912.43003.qm@web44816.mail.sp1.yahoo.com> (raw)
I am experimenting with Buildroot under QEMU, using buildroot-2009.11 and buildroot-2010.02-rc1.
So far, so good. I can boot a Linux kernel and RFS built by Buildroot under QEMU (versatilepb) where the RFS is exported via NFS.
QEMU includes a boot loader, so U-Boot is not needed. But I use U-Boot with real ARM hardware, so I would like to experiment with U-Boot under QEMU, adding DHCP and TFTP to the mix.
With real hardware, the U-Boot environment variables are persistent in flash memory.
Is there a way to simulate this with QEMU? I would not go to the trouble to manually enter the U-Boot environment variables each time I boot under QEMU, but if there is a persistence mechanism available then including U-Boot might be practical.
Thanks.
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100213/f1ccaebb/attachment-0001.htm>
next reply other threads:[~2010-02-13 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 21:51 Jim Thomas [this message]
2010-02-14 10:39 ` [Buildroot] Persistent U-Boot environment variables under QEMU Thomas Petazzoni
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=727912.43003.qm@web44816.mail.sp1.yahoo.com \
--to=jimthomasembedded@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox