public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: mtd@infradead.org
Subject: Re: Supported flash memory (fwd)
Date: Fri, 05 Jan 2001 16:27:39 +0000	[thread overview]
Message-ID: <8005.978712059@redhat.com> (raw)

forwarded by request,

--
dwmw2

------- Forwarded Message

Date: Fri, 05 Jan 2001 09:23:26 -0700 (MST)
From: Russ.Dill@asu.edu
Subject: Re: Supported flash memory
To: David Woodhouse <dwmw2@infradead.org>

Quoting David Woodhouse <dwmw2@infradead.org>:

> 
> Russ.Dill@asu.edu said:
> >  Besides footprints, pinouts, etc, my other concern is software. The
> > logical combination would seem to be blob/mtd. What flash products
> are
> > known or probable to be compatible with this combination, what should
> > I look for to attempt to assertain compatibilty? Does blob/mtd work
> > transparently with a 16bit or 32bit ROM bus? 
> 
> The MTD code ought to work with any CFI-compliant flash chip from Intel
> or 
> AMD, and with a few others too. In most combinations of bus size / 
> interleave.
> 
> I don't know about blob, but RedBoot should support most of the flash 
> setups you're likely to encounter, too.

What about flashes that say they have CUI (Command user interface) and SR
(Status register)? 

what are CFI commands? are they 8bit, 16bit? if you have 2 chips giving you a
32bit databus, does it write out the same command on the high lane and the low
lane? 

I've noticed LART connects address and data lines to flash in  positions most
convienent to route. Does this break any CFI functionality?


------- End of Forwarded Message





To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2001-01-05 16:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8005.978712059@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=mtd@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