All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Request for testing: AMD/Fujitsu flash chips
Date: Mon, 10 Dec 2007 09:43:41 +0200	[thread overview]
Message-ID: <475CEE2D.2030509@compulab.co.il> (raw)
In-Reply-To: <1196443609.13978.53.camel@pmac.infradead.org>



David Woodhouse wrote:
> For a long time, there's been confusion about the "unlock addresses" for
> AMD-compatible NOR flash -- the chip definition in our table have an
> _array_ giving the addresses at which we should do the magic unlock
> write cycles, according to the different modes (16-bit, 8-bit) that the
> chip could be used in.
> 
> For a while now, we've been deliberately ignoring all but the first
> entry in that array, on the basis that it shouldn't actually vary -- the
> chip needs the same levels on the same address lines, whatever mode it's
> in. The data sheets can be very confusing... for example:
> 
> 	5. The system should generate the following address patterns:
> 	    Word Mode: 555H or 2AAH to addresses A0 to A10
> 	    Byte Mode: AAAH or 555H to addresses A-1 to A10
> 
> I've just got rid of the array of unlock addresses, and _attempted_ to
> make the code cope and work again. I would very much appreciate some
> testing, before I put that in the MTD git tree:
> 
> 	git://git.infradead.org/~dwmw2/jedec-unlock.git
> 	http://git.infradead.org/?p=users/dwmw2/jedec-unlock.git

I've tested with Eon EN29SL800 (not in the main tree). Works Ok.


-- 
Sincerely yours,
Mike.

  reply	other threads:[~2007-12-10  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 17:26 Request for testing: AMD/Fujitsu flash chips David Woodhouse
2007-12-10  7:43 ` Mike Rapoport [this message]
2007-12-10 13:32   ` David Woodhouse
2007-12-10 15:09     ` Mike Rapoport

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=475CEE2D.2030509@compulab.co.il \
    --to=mike@compulab.co.il \
    --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.