From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Eric W. Biederman" <ebiederman@lnxi.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: JEDEC programming command spec
Date: Sat, 6 Apr 2002 17:34:30 -0800 [thread overview]
Message-ID: <001901c1ddd5$841955f0$7e0aa8c0@bridge> (raw)
In-Reply-To: m34rio308a.fsf@DLT.linuxnetworx.com
Got it. 3.5.x actually.
Thanks,
Jeremy
----- Original Message -----
From: "Eric W. Biederman" <ebiederman@lnxi.com>
To: "Jeremy Jackson" <jerj@coplanar.net>
Cc: <linux-mtd@lists.infradead.org>
Sent: Saturday, April 06, 2002 2:56 PM
Subject: Re: JEDEC programming command spec
> "Jeremy Jackson" <jerj@coplanar.net> writes:
>
> > I read everywhere about the JEDEC std. commands...
> > but www.jedec.org only has CFI command set info.
> >
> > Can anyone point me to this info? Seems every vendor
> > has some variation, but without the original to compare with,
> > it seems impossible to know what is "standard" and what isn't.
>
> JESD21-C section 3.3.1 I think.
>
> Eric
>
prev parent reply other threads:[~2002-04-07 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 20:46 JEDEC programming command spec Jeremy Jackson
2002-04-06 22:56 ` Eric W. Biederman
2002-04-07 1:34 ` 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='001901c1ddd5$841955f0$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--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.