public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Ian S. Nelson" <ian.nelson@echostar.com>
To: "mtd@infradead.org" <mtd@infradead.org>
Subject: CFI Physical Mapped working?
Date: Wed, 06 Dec 2000 16:59:06 -0700	[thread overview]
Message-ID: <3A2ED2CA.14522213@echostar.com> (raw)

I've been trying to get either the CFI AMD or CFI Physical Mapping to
work with no luck.  Are there any tricks to making it work?  It doesn't
look like any of that code is ever called.  I can load the modules but
nothing ever happens.  I've put some printks in the init_module function
and nothing ever prints.

I'm running with the code in  the 2.4.0test10 tree,  I'm going to try
the CVS code here shortly though.

Also, what are the differences between the physical mapped interface and
CFI?  I'm using an AMD 2MB flash, it's the low power one AM29LV160, I
believe is the part number.  AMD says it's CFI compliant so I'm hoping
it works.    I can read it in physical memory as it is now so I know
that it is visible that way, if nothing else.  I'm working on a National
Semi based product, it has a MediaGX1 and the CS5530A in it if that
makes any difference, I'm under the impression that it shouldn't.  I'm
using their "Centaurus"  test board but I have custom "pizza boards"
too,  the Centaurus is a bit tricky as it has a 256K flash, a 2MB flash
and a 5 or 8 MB DoC and there is a chip select that determines which one
you're running, if that makes any difference.

thanks,
Ian



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

             reply	other threads:[~2000-12-06 23:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 23:59 Ian S. Nelson [this message]
2000-12-07  8:02 ` CFI Physical Mapped working? 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=3A2ED2CA.14522213@echostar.com \
    --to=ian.nelson@echostar.com \
    --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