From: Ian Molton <spyro@f2s.com>
To: linux-mtd@lists.infradead.org
Subject: Re: supporting stupid chips part IV
Date: Mon, 23 Aug 2004 00:43:04 +0100 [thread overview]
Message-ID: <20040823004304.0befb1b3.spyro@f2s.com> (raw)
In-Reply-To: <20040823003835.712122c3.spyro@f2s.com>
On Mon, 23 Aug 2004 00:38:35 +0100
Ian Molton <spyro@f2s.com> wrote:
Hit ctrl-enter, oops... try again...
> This gets worse...
>
> So, now we have the chip reading OK with soft ECC, albeit using a
> *bizarre* layout for the ECC data.
>
> but it appears the hardware ECC doesnt work! the little bugger.
looking at winCE code more closely, I now see that winCE only uses hw
ECC when *writing*, although it actually seems to reset and enable hw
ECC when reading - just discards the results, bah!
oh well. I guess its back ot soft ECC for now... I'll send an email to
toshiba and see if they have anything to say...
prev parent reply other threads:[~2004-08-22 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 12:23 supporting stupid chips Ian Molton
2004-08-20 23:26 ` supporting stupid chips part II Ian Molton
2004-08-22 13:10 ` supporting stupid chips part III Ian Molton
2004-08-22 23:38 ` supporting stupid chips part IV Ian Molton
2004-08-22 23:43 ` Ian Molton [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=20040823004304.0befb1b3.spyro@f2s.com \
--to=spyro@f2s.com \
--cc=linux-mtd@lists.infradead.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