From: Armin <akuster@kama-aina.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] pflash usage question
Date: Mon, 26 Nov 2007 05:55:44 -1000 [thread overview]
Message-ID: <474AEC80.2090906@kama-aina.net> (raw)
Hello all,
I have two questions regarding how to use pflash.
1) I have two 64MiB flash devices, so do I use one "-pflash" on the
command line that has an image that is the total size of both flashes or
use two "-pflash" on the command line.
2) The parameters for the pflash register are a bit confusing. The
block size for my device is 64 but that does not work, I currently have
tested it with 128. Also, the sector value, I could not find that
reference in the datasheet for my flash. How should I use it? I used
128 * 1024 and that worked too.
With the values I mentions above, I can mount the flash and us it as a
root file system. I do get messages when I erase but I know that is not
supported at the moment.
If someone can set me straight on #1 and #2 then I will have be
submitting flash support for the Mainstone shortly.
TIA,
Armin
reply other threads:[~2007-11-26 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=474AEC80.2090906@kama-aina.net \
--to=akuster@kama-aina.net \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).