From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question regarding NAND emulation.
Date: Sat, 22 Nov 2008 21:36:15 +0100 [thread overview]
Message-ID: <fb249edb0811221236o9f4f631x427826a3b62c5321@mail.gmail.com> (raw)
In-Reply-To: <gg89a3$li8$1@ger.gmane.org>
2008/11/22 Dmitry Baryshkov <dbaryshkov@gmail.com>:
> Hi,
>
> I have a question regarding NAND emulation. While simple NAND emulation
> is easy, ECC stuff left me in uncertain state. In hw/spitz.c I saw some
> balck magic regarding ecc.lp with shifts, ors etc. So, the question is:
> if I'd like to implement HW ECC emulation for my NAND device, how should
> I return ECC line and col parity bytes?
It depends totally on the nand controller you emulate, but it can be
deduced from a linux driver for it. Basically lp holds line parity
bits and cp the column parity, you'll see different black magic
applied in spitz.c and in onenand.c and in omap2.c and in
https://svn.openmoko.org/trunk/src/host/qemu-neo1973/hw/s3c2410.c
Cheers
prev parent reply other threads:[~2008-11-22 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 6:36 [Qemu-devel] Question regarding NAND emulation Dmitry Baryshkov
2008-11-22 20:36 ` andrzej zaborowski [this message]
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=fb249edb0811221236o9f4f631x427826a3b62c5321@mail.gmail.com \
--to=balrogg@gmail.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).