From: ebiederman@lnxi.com (Eric W. Biederman)
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: <linuxbios@lanl.gov>, <linux-mtd@lists.infradead.org>
Subject: Re: PIIX flashing woes with SST29EE010
Date: 03 Apr 2002 18:11:38 -0700 [thread overview]
Message-ID: <m33cycnu7p.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: <00fd01c1db72$f225c200$7e0aa8c0@bridge>
"Jeremy Jackson" <jerj@coplanar.net> writes:
> (crossposted)
> FYI,
>
> A problem I was having that *appeared* to be a problem with
> getting writes to the flash chip, wasn't
>
> It turns out that SST's datasheet for SST29EE010 is incorrect.
> It turns out that the part I have *doesn't* respond to "new" style
> ID mode entry sequence, as indicated in the manual.
> It only responds to the "old" AA 55 80 AA 55 60 sequence.
>
> I should have a generic PIIX map driver for MTD soon now.
So does jedec_probe work for you or do you need to patch it?
Eric
next prev parent reply other threads:[~2002-04-04 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 0:52 PIIX flashing woes with SST29EE010 Jeremy Jackson
2002-04-04 1:11 ` Eric W. Biederman [this message]
2002-04-04 1:23 ` Jeremy Jackson
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=m33cycnu7p.fsf@DLT.linuxnetworx.com \
--to=ebiederman@lnxi.com \
--cc=jerj@coplanar.net \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxbios@lanl.gov \
/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