From: David Woodhouse <dwmw2@infradead.org>
To: Stuart Menefy <Stuart.Menefy@st.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CFI vs JEDEC read commands
Date: Tue, 12 Jun 2001 09:51:06 +0100 [thread overview]
Message-ID: <7578.992335866@redhat.com> (raw)
In-Reply-To: <1010611181131.ZM26024@bristol.st.com>
Stuart.Menefy@st.com said:
> However, this got me looking at the code. In virtually every case, a
> 'read' command is 0xf0, apart from two (one in cfi_cfi_probe and the
> other in cfi_cmdset_unknown), when is it 0xff. Is this deliberate, and
> would changing the remaining two to 0xf0 cause any problems?
They were originally 0xFF because I was dealing with Intel flash when I
wrote the CFI probe code, and that's the 'Read Array' command for Intel
flash. AFAICT CFI doesn't actually specify a way to take the chip _out_ of
read mode, and hence to detect aliases. I suspect 0xF0 should work. Let's
change it and see if it breaks - if it does we have to implement a
cmdset-specific 'switch back to read mode' function.
--
dwmw2
prev parent reply other threads:[~2001-06-12 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 17:11 CFI vs JEDEC read commands Stuart Menefy
2001-06-12 8:51 ` David Woodhouse [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=7578.992335866@redhat.com \
--to=dwmw2@infradead.org \
--cc=Stuart.Menefy@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox