From: David Woodhouse <dwmw2@infradead.org>
To: David Byron <dbyron@coactive.com>
Cc: mtd@infradead.org
Subject: Re: AMD Flash flaming
Date: Thu, 15 Feb 2001 09:34:08 +0000 [thread overview]
Message-ID: <14036.982229648@redhat.com> (raw)
In-Reply-To: <7118259C3044D311942700508B2CA5BB61AB17@balance.coactive.com>
dbyron@coactive.com said:
> I just subscribed to the list a few days ago and caught some
> discussion on annoying characteristics of some AMD flash devices.
> Turns out we're in the middle of selecting a flash device for a new
> platform and one of the choices being considered is the AMD
> Am29LV033C. Sorry if this is covered elsewhere, but is this one of
> the annoying/busted chips?
They're not busted, just annoying. I happen to think the designers were on
crack, but the chips are still usable, even though their CFI tables are
crap. Even if we have to hard-code a table of chip ID vs. erase block
layout, they're usable - unless they've really gone mad and shipped chips
with the _same_ JEDEC ID but different layouts.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
prev parent reply other threads:[~2001-02-15 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 22:58 AMD Flash flaming David Byron
2001-02-15 9:34 ` David Woodhouse [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=14036.982229648@redhat.com \
--to=dwmw2@infradead.org \
--cc=dbyron@coactive.com \
--cc=mtd@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 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.