From: ebiederman@lnxi.com (Eric W. Biederman)
To: tharbaugh@lnxi.com
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] refactoring MTD cmdset ops, jedec_probe, and cfi_probe
Date: 13 Jul 2004 09:40:48 -0600 [thread overview]
Message-ID: <m3n0237w5b.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <1089732108.8696.127.camel@tubarao>
Thayne Harbaugh <tharbaugh@lnxi.com> writes:
> > Thayne this problem I am not familiar with. Could I have some details?
>
> Errrr . . . the problem of the unlock address or of the harry, ugly
> code?
>
> The unlock story is that there was *no* unlock code in cfi_cmdset_0002.
> One of the newer SST chips requires unlocking of the blocks. Unlike
> other chips that need unlocking, the addresses for unlocking this
> particular chip is not at the block address but below the address of the
> entire chip.
Ah. yes. Sorry the way you phrased it I was thinking of the unlock_addr address
prefix that needs to be applied to commands. The magic Firmware hub addresses
that are used for locking/unlocking block I am familiar with.
Eric
next prev parent reply other threads:[~2004-07-13 15:40 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 [this message]
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
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=m3n0237w5b.fsf@maxwell.lnxi.com \
--to=ebiederman@lnxi.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tharbaugh@lnxi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox