public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederman@lnxi.com (Eric W. Biederman)
To: Pantelis Antoniou <panto@intracom.gr>
Cc: linux-mtd@lists.infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: MTD lock support for AMD_STD flash.
Date: 15 Sep 2004 12:15:51 -0600	[thread overview]
Message-ID: <m3pt4n8kko.fsf@maxwell.lnxi.com> (raw)
In-Reply-To: <41457E01.6060507@intracom.gr>

Pantelis Antoniou <panto@intracom.gr> writes:

> Hi there
> 
> While trying to get MTD in 2.6 working in my board I stubbled on
> this.
> 
> The lock/unlock logic does not seem to work for AMD STD jedec flashes.

Right.  We got away with this for a while because the on devices
without lock/unlock methods people usually don't call them.
 
> This happens when trying to lock a block for MX29LV040C, and I think
> will happen with all AMD STD flashes.
> 
> The thing is that these chips don't have support for locking, but I can't
> find a way to declare it in the command set.
> 
> So the way to avoid this I set the lock & unlock methods in my map file.
> 
> This is a gross hack however and I'm wondering if there's an easier way...

Yes.  It should already be committed into MTD cvs.  Please check it out.
With a little luck I will start pushing these changes to 2.6 in the next
day or so.

Eric

      reply	other threads:[~2004-09-15 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 11:01 MTD lock support for AMD_STD flash Pantelis Antoniou
2004-09-15 18:15 ` Eric W. Biederman [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=m3pt4n8kko.fsf@maxwell.lnxi.com \
    --to=ebiederman@lnxi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=panto@intracom.gr \
    /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