From: Josh Boyer <jdub@us.ibm.com>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: Tue, 13 Jul 2004 11:17:35 -0500 [thread overview]
Message-ID: <1089735455.29112.14.camel@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <m3658sj5ex.fsf@maxwell.lnxi.com>
On Tue, 2004-07-13 at 10:25, Eric W. Biederman wrote:
> Ok recording what the reason for this that I got on irc.
>
> cfi_cmdset_0020 is just a variant on cfi_cmdset_0001 that shares most of
> the code.
Thinking about this more, I wouldn't worry too much about
cfi_cmdset_0020.c. It's old, fairly unmaintained, and only has a single
user as far as I know.
If your changes break it, then it'll give someone and excuse to update
the code. Eventually it should be merged with cfi_cmdset_0001.c anyway,
since M58LW128A reports command set 01, but really needs the
functionality of command set 20. The exception list you talked about in
IRC might help with that.
But don't let me stop you from making it work if you want to :).
> A data sheet for the M58LW128A ( which erroneously reports cmdset 01 instead of 0x20)
> is at:
> http://www.st.com/stonline/books/pdf/docs/9229.pdf
>
> cmdset 020 was written for the M58LW064A and I doesn't currently have a datasheet reference
> for on ST site.
Probably because it isn't that common of a part, and newer versions of
that chip have been made available.
josh
next prev parent reply other threads:[~2004-07-13 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 3:13 [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe Eric W. Biederman
2004-07-13 6:25 ` David Woodhouse
2004-07-13 7:05 ` Eric W. Biederman
2004-07-13 8:02 ` David Woodhouse
2004-07-13 14:23 ` Eric W. Biederman
2004-07-13 14:45 ` Thayne Harbaugh
2004-07-13 15:04 ` Eric W. Biederman
2004-07-13 15:21 ` Thayne Harbaugh
2004-07-13 15:40 ` Eric W. Biederman
2004-07-13 16:00 ` Eric W. Biederman
2004-07-14 5:44 ` Eric W. Biederman
2004-08-12 7:39 ` Eric W. Biederman
2004-07-13 15:25 ` Eric W. Biederman
2004-07-13 16:17 ` Josh Boyer [this message]
2004-08-12 7:13 ` Eric W. Biederman
2004-08-16 14:13 ` Josh Boyer
2004-07-13 16:36 ` Dan Post
2004-07-13 16:52 ` Nicolas Pitre
2004-07-13 17:33 ` Dan Post
2004-07-13 18:17 ` Nicolas Pitre
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=1089735455.29112.14.camel@weaponx.rchland.ibm.com \
--to=jdub@us.ibm.com \
--cc=dwmw2@infradead.org \
--cc=ebiederman@lnxi.com \
--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 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.