From: David Woodhouse <dwmw2@infradead.org>
To: "Richard A. Smith" <rsmith@bitworks.com>
Cc: "Ronald G Minnich" <rminnich@lanl.gov>,
"linuxbios@lanl.gov" <linuxbios@lanl.gov>,
linux-mtd@lists.infradead.org
Subject: Re: Re[2]: linux boot time
Date: Fri, 17 May 2002 16:44:43 +0100 [thread overview]
Message-ID: <9295.1021650283@redhat.com> (raw)
In-Reply-To: <MDAEMON-F200205171026.AA261579MD57584@bitworks.com>
rsmith@bitworks.com said:
> I think I posted some info about my experiences a while back.... that
> may have been on the embedded list though...
> David, how many other reports besides mine to you have of the CF's
> developing a problem? We use both SanDisk and SST CF's in a couple of
> projects and most of our failures are during the development cycle.
> Go figure...
There was Vipin Malik's writeup at http://www.embeddedlinuxworks.com/ but
that doesn't seem to be there any more. He was actually doing powerfail
testing on JFFS/JFFS2 and making me fix it when it broke, but he also did
some on CF, and obviously could do nothing when it broke. Software is _so_
much nicer.
Charles Manning's rants about bog-roll technology¹ are too vehement to have
been born from anything but personal experience as well, AFAICT :)
--
dwmw2
¹ http://mhonarc.axis.se/jffs-dev/msg01267.html
next parent reply other threads:[~2002-05-17 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MDAEMON-F200205171026.AA261579MD57584@bitworks.com>
2002-05-17 15:44 ` David Woodhouse [this message]
2002-05-17 15:57 ` Getting big flash onto motherboards. Will CF work? what will? Ronald G Minnich
2002-05-17 15:59 ` David Woodhouse
2002-05-17 16:05 ` Ronald G Minnich
2002-05-17 16:17 ` David Woodhouse
2002-05-17 16:20 ` Ronald G Minnich
2002-05-17 17:08 ` Russ Dill
2002-05-18 7:06 ` David Woodhouse
2002-05-17 19:48 ` Richard A. Smith
2002-05-17 18:52 ` Re[2]: linux boot time Richard A. Smith
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=9295.1021650283@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxbios@lanl.gov \
--cc=rminnich@lanl.gov \
--cc=rsmith@bitworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.