public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kenneth Johansson <kenneth.johansson@inn.ericsson.se>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Russ.Dill@asu.edu, mtd@infradead.org
Subject: Re: Supported flash memory
Date: Fri, 05 Jan 2001 14:56:15 +0100	[thread overview]
Message-ID: <3A55D27F.C1E734C2@inn.ericsson.se> (raw)
In-Reply-To: 2842.978696346@redhat.com

David Woodhouse wrote:

> 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 have a custom made flassh module,so-dimm (72 pin), that I want to use but
don't know if  I can .

The module can have up to 16 chips. (AMD)
Every chip has a to be in 8 bit mode.
The address range is divided into 8 chip select, giving a 16 bit data bus.
Thus I can't do any other access than 16 bit and always activate two chip's.

Also, we make them with a version that has a boot block (different block
size) but I think MTD can handle that or ?
I don't see any problem switching over to a version with all block the same
size.


>
> I don't know about blob, but RedBoot should support most of the flash
> setups you're likely to encounter, too.
>

Why do the boot code need to support flash? Flash looks like a ordinary ROM
for everything not knowing the magic sequence.




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

  reply	other threads:[~2001-01-05 13:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 19:28 Supported flash memory Russ.Dill
2001-01-05 12:05 ` David Woodhouse
2001-01-05 13:56   ` Kenneth Johansson [this message]
2001-01-05 14:09     ` David Woodhouse
     [not found]   ` <978711806.3a55f4fe37922@webmail1.asu.edu>
2001-01-05 16:29     ` David Woodhouse
2001-01-05 16:57       ` Kenneth Johansson
2001-01-05 17:03         ` David Woodhouse
2001-01-05 18:01           ` Nicolas Pitre
2001-01-05 21:07             ` David Woodhouse
2001-01-07 16:42         ` David Woodhouse
2001-01-05 17:53       ` Nicolas Pitre
  -- strict thread matches above, loose matches on Subject: below --
2001-02-02  0:49 Supported Flash memory Jose Guilberto
2001-02-02 10:30 ` David Woodhouse

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=3A55D27F.C1E734C2@inn.ericsson.se \
    --to=kenneth.johansson@inn.ericsson.se \
    --cc=Russ.Dill@asu.edu \
    --cc=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