public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andy Hawkins <a.hawkins@cabletime.com>
To: D.A.Fedorov@inp.nsk.su
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem writing to NOR flash
Date: 26 Jul 2004 17:07:27 +0100	[thread overview]
Message-ID: <1090858047.2219.77.camel@adh> (raw)
In-Reply-To: <1090856360.2220.63.camel@adh>

Hi all,

After a bit more digging and reading of the data sheet, it appears the
the chip I'm using doesn't need locking and unlocking. I then went back
to the version of the code where we had this working (whatever came with
the 2.4.20 kernel) and found that none of this locking / unlocking
mechanism was present.

So, to test I commented out the contents of cfi_amdstd_lock_varsize and
cfi_amdstd_unlock_varsize, and I can now successfully write to the NOR!

Are these functions only required for some very specific chips? If so,
what is the *correct* way for this code to determine whether or not they
are needed (this code is in a 'generic' file, so I'm surprised that
there's chip specific information in there).

Thanks for any advice you can offer.

Andy

  reply	other threads:[~2004-07-26 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 13:32 Problem writing to NOR flash Andy Hawkins
2004-07-26 14:00 ` Dmitry A. Fedorov
2004-07-26 14:11   ` Andy Hawkins
2004-07-26 14:35     ` Dmitry A. Fedorov
2004-07-26 14:49       ` Andy Hawkins
2004-07-26 15:00         ` Dmitry A. Fedorov
2004-07-26 15:39           ` Andy Hawkins
2004-07-26 16:07             ` Andy Hawkins [this message]
2004-08-05 23:24               ` Eric W. Biederman
2004-08-12  6:59                 ` Eric W. Biederman
2004-07-29 19:41 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-07-19 16:06 Andy Hawkins

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=1090858047.2219.77.camel@adh \
    --to=a.hawkins@cabletime.com \
    --cc=D.A.Fedorov@inp.nsk.su \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox