From: Jean-Hugues Deschenes <jean-hugues.deschenes@octasic.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] NAND_CMD_COPYBACKPRG1 commands problematic?
Date: Thu, 07 Jan 2010 16:38:29 -0500 [thread overview]
Message-ID: <4B465455.1060703@octasic.com> (raw)
Hi,
Has anyone used NAND_CMD_COPYBACKPRG1 commands? Those seem
problematic, as it seems s->iolen is not updated when the emulated page
buffer is written to, such that blk_write fails to write the updated
data to the block device... Is it a misunderstanding on my part of the
command sequence to send? ( I send a NAND_CMD_READ0 - NAND_CMD_LPREAD2
and a nand_getio to load the page buffer, follwoed by a
NAND_CMD_PAGEPROGRAM1 [offset 0 within the page] to set the device to
wrtie mode, followed by a NAND_CMD_COPYBACKPRG1 [offset 2048 within the
page], followed by 64 bytes of data and finally, a NAND_CMD_PAGEPROGRAM2)...
Thanks!
jh
reply other threads:[~2010-01-07 21:38 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=4B465455.1060703@octasic.com \
--to=jean-hugues.deschenes@octasic.com \
--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).