public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: swahl@brecis.com (Steve Wahl)
To: linux-mtd@lists.infradead.org
Subject: DQ5 & DQ6 in chips/cfi_cmdset_0002.c (Dairy Queen 5 warning)
Date: Wed, 19 Mar 2003 09:56:38 -0600	[thread overview]
Message-ID: <20030319095638.V1745@brecis.com> (raw)
In-Reply-To: <1048033423.11512.1657.camel@tubarao>; from tharbaugh@lnxi.com on Tue, Mar 18, 2003 at 05:23:43PM -0700

On Tue, Mar 18, 2003 at 05:23:43PM -0700, Thayne Harbaugh wrote:
>   It likely could be simplified even more - take out feeble support for
> interleaved chips (which I don't have and can't test and I'm not even
> sure that the chips that work this way support interleaving).

Interleaved operation is probably always supported, because the chips
don't "know" they're doing it.

Unless I'm completely mistaken, interleaving is simply having N chips
with a data bus width of W on a bus that's N * W wide.  For instance,
I once worked on a product with a processor that didn't do anything
smaller than a 32 bit bus, so the flash area of memory was populated
with 4 chips (each 8 bits wide).

For these, you generally issue the commands to all chips at one time,
in this case writing 32 bit words with the command bytes replicated in
each byte of the word.  Makes the polling a little complicated,
perhaps, because you have to watch for all chips to reach a finished
state before you continue.

Still thinking about the rest of what you wrote.  My initial thoughts
are this shouldn't really need a whole separate command set file.

--> Steve

  reply	other threads:[~2003-03-19 15:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  0:25 DQ5 & DQ6 in chips/cfi_cmdset_0002.c (Dairy Queen 5 warning) Thayne Harbaugh
2003-03-12 15:44 ` John Burch
2003-03-12 16:35   ` Thayne Harbaugh
2003-03-12 16:27 ` Steve Wahl
2003-03-12 17:12   ` John Burch
2003-03-12 21:43     ` Steve Wahl
2003-03-12 22:17       ` John Burch
2003-03-13  7:17       ` David Woodhouse
2003-03-13  7:26         ` Russ Dill
2003-03-17 15:54       ` Thayne Harbaugh
2003-03-17 16:09         ` John Burch
2003-03-17 16:19         ` Steve Wahl
2003-03-17 18:27           ` Thayne Harbaugh
2003-03-18 16:51             ` Steve Wahl
2003-03-18 17:22               ` Thayne Harbaugh
2003-03-17 15:40   ` Thayne Harbaugh
2003-03-17 18:38     ` Thayne Harbaugh
2003-03-19  0:23       ` Thayne Harbaugh
2003-03-19 15:56         ` Steve Wahl [this message]
2003-03-19 19:38           ` Thayne Harbaugh

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=20030319095638.V1745@brecis.com \
    --to=swahl@brecis.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