From: sl@gateway.fireplug.net (Stuart Lynne)
To: mtd@infradead.org
Subject: Re: [Fwd: power down]
Date: 20 Dec 1999 04:03:08 GMT [thread overview]
Message-ID: <83k9ps$7k9$1@nero.fireplug.net> (raw)
In-Reply-To: 384D2C2D.6A6F4CE6@go2fax.com
In article <384D2C2D.6A6F4CE6@go2fax.com>, Bob Canup <rcanup@go2fax.com> wrote:
>Vipin Malik wrote:
>
>> Bob Canup wrote:
>> >
>
>I don't think that you understand what we're trying to tell you. There is a
>difference in philosophy.
>
>If you are running a flash as a normal read - write imitation of a disk there
>are severe time limitations as to how long the flash is going to work because
>of the limit on write cycles which flash technology has. As has been pointed
>out in an earlier post - one write a second will ruin a flash chip in a few
>weeks - which is not a very long for an embedded system to work.
Assuming load levelling across a 4mb flash drive, if you average 4kb per
write and write once per second continously you will write each sector a
about 40 times per day.
AMD specs a minimum program/erase cycles of 100,000 per sector (flash
sector) and 1,000,000 per device. To reach 100,000 writes at 50 per day
would take over 5 years.
>Because of this limitation most of the people in this group who do design
>with flash use it in a Write Rarely Read Mostly manner. The only time the
>flash is written to is when there is a firmware upgrade. This is also the
>manner in which flash chips are used on conventional PC motherboards - if you
>lose power during a firmware upgrade - you are in trouble - nor do I see any
>practical method of handling that problem.
Well if you have control over your design simply ensure that you have two
banks and can boot from either of them. Upgrading involves booting from
one to upgrade the other and then selecting the new bank as the default
boot.
--
Stuart Lynne <sl@fireplug.net> __O
<http://www.thinlinux.org> _-\<,_ 604-461-7532
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~1999-12-20 3:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 23:41 [Fwd: power down] Vipin Malik
1999-12-07 15:47 ` Bob Canup
1999-12-20 4:03 ` Stuart Lynne [this message]
1999-12-07 20:36 ` Jon Burford
1999-12-13 14:49 ` Adi Linden
1999-12-13 19:07 ` Jon Burford
1999-12-08 15:10 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
1999-12-07 16:36 Oron Ogdan
1999-12-08 20:42 [Fwd: Power Down] Vipin Malik
1999-12-08 20:48 Vipin Malik
1999-12-08 21:32 Vipin Malik
1999-12-09 11:10 ` David Woodhouse
1999-12-08 21:36 Vipin Malik
1999-12-08 23:02 ` Bob Canup
1999-12-09 11:02 ` David Woodhouse
1999-12-09 14:56 ` Bob Canup
1999-12-20 4:22 ` Stuart Lynne
1999-12-08 21:39 Vipin Malik
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='83k9ps$7k9$1@nero.fireplug.net' \
--to=sl@gateway.fireplug.net \
--cc=mtd@infradead.org \
--cc=sl@fireplug.net \
/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