From: David Updegraff <dave@cray.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: patch for AMD am29dl800b
Date: Fri, 02 Apr 2004 07:30:27 -0600 [thread overview]
Message-ID: <406D6AF3.9010808@cray.com> (raw)
In-Reply-To: <1080885452.17863.39.camel@imladris.demon.co.uk>
> Please don't reply to unrelated threads. This isn't about bad blocks and
> doesn't live with the message to which you replied.
Whoops.. me aculpa.
>
> On Thu, 2004-04-01 at 18:01 -0600, David Updegraff wrote:
>
>>Hi.
>>
>>I have a gadget with this amd chip on it. Whose id and layout dfn. is
>>not in the jedec_probe tables. Unfortuanately, they have _SIX_ (6)
>>erase regions. Anyone know of a reason expanding the regions[] array to
>>6 is a bad idea? Or why dealing with this chip in general is a bad idea?
>
>
> Hmmm. And this chip really doesn't do CFI?
My attempts at that failed; and their PDF only says 'JEDEC compatible'.
> I wonder how much space we take up with this table, and if we should put
> the regions outside the table rather than inline ("ulong *regions").
.. or invent a command-line syntax; since in embedded situations one
usually knows what one is looking for.. or has that alredy been
discussed and discarded?
-dbu.
next prev parent reply other threads:[~2004-04-02 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:06 Bad blocks Kalev Lember
2004-04-01 14:36 ` David Woodhouse
2004-04-02 0:01 ` patch for AMD am29dl800b David Updegraff
2004-04-02 5:57 ` David Woodhouse
2004-04-02 13:30 ` David Updegraff [this message]
2004-04-02 13:39 ` David Woodhouse
2004-04-02 0:14 ` Bad blocks Greg Ungerer
2004-04-04 11:16 ` Kalev Lember
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=406D6AF3.9010808@cray.com \
--to=dave@cray.com \
--cc=dwmw2@infradead.org \
--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