From: "Richard A. Smith" <richard@laptop.org>
To: mikus@bga.com
Cc: devel@lists.laptop.org, linux-mmc@vger.kernel.org
Subject: Re: Memory replacement
Date: Mon, 14 Mar 2011 10:17:34 -0400 [thread overview]
Message-ID: <4D7E237E.1040409@laptop.org> (raw)
In-Reply-To: <4D7D4670.1050009@bga.com>
On 03/13/2011 06:34 PM, Mikus Grinbergs wrote:
>> The tests have also helped expose other issues with things like sudden
>> power off. In one case a SPO during a write would corrupt the card so
>> badly it became useless. You could only recover them via a super secret
>> tool from the manufacturer.
>
> Is there any "sledgehammer" process available to users without a super
> secret tool ?
Wasn't just secret to users. They would not give us the info on how to
do it either. It was vendor specific so not really worth the effort of
trying to reverse engineer.
--
Richard A. Smith <richard@laptop.org>
One Laptop per Child
next prev parent reply other threads:[~2011-03-14 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikQOVa8qfU-R6uqQXKhAVxqeAmxKONjPmmqLCr8@mail.gmail.com>
[not found] ` <201103111135.01394.arnd@arndb.de>
[not found] ` <320717C0-7117-462E-9227-7966EE6941D7@laptop.org>
2011-03-12 22:51 ` Memory replacement Arnd Bergmann
2011-03-13 1:01 ` C. Scott Ananian
2011-03-13 12:57 ` Andrei Warkentin
2011-03-13 17:00 ` C. Scott Ananian
2011-03-13 17:06 ` C. Scott Ananian
2011-03-13 17:21 ` Arnd Bergmann
2011-03-13 21:31 ` Richard A. Smith
2011-03-13 22:34 ` Mikus Grinbergs
2011-03-14 14:01 ` Arnd Bergmann
2011-03-14 14:17 ` Richard A. Smith [this message]
2011-03-14 18:50 ` John Watlington
2011-03-14 19:18 ` Arnd Bergmann
2011-03-15 0:29 ` John Watlington
2011-03-15 8:42 ` Arnd Bergmann
2011-03-14 17:32 ` Arnd Bergmann
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=4D7E237E.1040409@laptop.org \
--to=richard@laptop.org \
--cc=devel@lists.laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mikus@bga.com \
/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