From: David Woodhouse <dwmw2@infradead.org>
To: Nicolas Pitre <nico@cam.org>
Cc: Alice Hennessy <ahennessy@mvista.com>,
"Fry, Dan" <dfry@bb.directv.com>,
linux-mtd@lists.infradead.org
Subject: Re: Improper Command Sequence
Date: Sat, 05 May 2001 16:45:04 +0100 [thread overview]
Message-ID: <5543.989077504@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105051113080.15370-100000@xanadu.home>
nico@cam.org said:
> ... and don't forget possible chip interleaves.
We currently deal with that to a certain extent, but not particularly
nicely:
if (status & CMD(0x3a)) {
unsigned char chipstatus = status;
if (status != CMD(status & 0xff)) {
int i = cfi->interleave;
for (i = 1; i<cfi->interleave; i++) {
chipstatus |= status >> (cfi->device_type * 8);
}
printk(KERN_WARNING "Status is not identical for all chips: 0x%x. Merging to give 0x%02x\n", status, chipstatus);
}
Actually I think the device_type there ought to be buswidth / interleave.
--
dwmw2
prev parent reply other threads:[~2001-05-05 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 23:09 Improper Command Sequence Fry, Dan
2001-05-04 23:54 ` Alice Hennessy
2001-05-05 11:11 ` David Woodhouse
2001-05-05 15:13 ` Nicolas Pitre
2001-05-05 15:45 ` 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=5543.989077504@redhat.com \
--to=dwmw2@infradead.org \
--cc=ahennessy@mvista.com \
--cc=dfry@bb.directv.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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.