All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Espin <espin@idiom.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: 4 x AMD29LV800B CFI?
Date: Tue, 27 Nov 2001 19:30:15 -0800	[thread overview]
Message-ID: <20011127193015.A35212@idiom.com> (raw)
In-Reply-To: <16214.1006859128@redhat.com>; from David Woodhouse on Tue, Nov 27, 2001 at 11:05:28AM +0000

> >  Perhaps my h/w setup is insisting that all 4 parts are programmed at
> > once?  I see ifdef SOMEONE_ACTUALLY... for width 4 type 32 interleave
> > 4; maybe this means generate the right pattern? 
> That's around the code for 32-bit flash chips. You don't have 32-bit chips, 
> you have 16-bit chips, in 8-bit mode.
> I've used the 29LV160, and it's definitely CFI-compliant. Strangely, the 
> 29LV800 isn't. But the jedec_probe code doesn't yet recognise it. Try 
> this...
> Index: drivers/mtd/chips/jedec_probe.c
> ...

Thanks, David, ever so much for the patch.  I'd played with Jedec too.
I actually got amd_flash.c to seemingly work on its own -- just
tested with "mtd_debug read/write ..."  My hacked amd_flash.c prints:

    Physically mapped flash: Found 1 x 4MiB AMD AM29LV800BT (*4) at 0x0
                                                            ^^^^
Yeah!

I'd prefer to use your version, will give it a try...

Geoff
-- 
Geoffrey Espin
espin@idiom.com 

      reply	other threads:[~2001-11-28  3:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1669aI-0001iv-00@pentafluge.infradead.org>
2001-11-23 21:01 ` 4 x AMD29LV800B CFI? Geoffrey Espin
2001-11-27 11:05   ` David Woodhouse
2001-11-28  3:30     ` Geoffrey Espin [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=20011127193015.A35212@idiom.com \
    --to=espin@idiom.com \
    --cc=dwmw2@infradead.org \
    --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 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.