nand locking

Thomas Gleixner tglx at
Wed Apr 27 07:35:47 EDT 2005

On Wed, 2005-04-27 at 14:27 +0400, Timofei V. Bondarenko wrote:
> > Lock/unlock are general features and should be added to nand_base.c.
> > I guess the chips which have those functions can be identified and an
> > appropriate option flag set in the ID list, which then lets nand_scan
> > decide whether to fill in the lock/unlock function pointers or not.
> An easy problem: I'm looking for the simplest way to protect
> read-only mtd partitions by hardware lock.
> The current nand_base seems lack of this feature.
> Should i hack the nand_base? Or is there a correct workaround?

As I said above, it is functionality which should be integrated cleanly
into nand_base.c. It should be automatically available for those chips
which support it.

There is no workaround. Its missing and must be added. I'm happy if you
can provide a patch.

> It awaits since 18 Apr - longer than a week... is it ok?

David Woodhouse was travelling last week

> Are there other ways to submit a patch? (a small bugfix to cmdlinepart).
> AFAIK, placing diffs into message text is not welcomed too.

It's a correct way to do it, when your mail client can handle the
whitespace (tabs) correct and does no line truncating at 80, which is
requested for the mail text itself.


More information about the linux-mtd mailing list