From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: <linuxbios@lanl.gov>, <linux-mtd@lists.infradead.org>
Subject: Re: PIIX flashing woes with SST29EE010
Date: Wed, 3 Apr 2002 17:23:46 -0800 [thread overview]
Message-ID: <010d01c1db77$6062e690$7e0aa8c0@bridge> (raw)
In-Reply-To: m33cycnu7p.fsf@DLT.linuxnetworx.com
No I will need to patch it.
I have been reading through
the source code of a DOS based flash utility, Uniflash (Pascal)
and it's probe routine appears to use both methods.
(it tries old method first BTW)
It works well (under DOS/FreeDOS) and supports a
surprising variety of chips and southbridges.
That's where I got the idea to try the old method.
I was just using an homemade one to try and figure out
what the problem was. I'm looking at integrating it right
now.
Jeremy
----- Original Message -----
From: "Eric W. Biederman" <ebiederman@lnxi.com>
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: <linuxbios@lanl.gov>; <linux-mtd@lists.infradead.org>
Sent: Wednesday, April 03, 2002 5:11 PM
Subject: Re: PIIX flashing woes with SST29EE010
> "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
>
prev parent reply other threads:[~2002-04-04 1:24 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
2002-04-04 1:23 ` Jeremy Jackson [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='010d01c1db77$6062e690$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--cc=ebiederman@lnxi.com \
--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