public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Timofei V. Bondarenko" <timm@ipi.ac.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: nand locking
Date: Wed, 27 Apr 2005 12:45:06 +0200	[thread overview]
Message-ID: <1114598706.879.185.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <426F56C1.6020204@ipi.ac.ru>

On Wed, 2005-04-27 at 13:09 +0400, Timofei V. Bondarenko wrote:
> Thomas Gleixner wrote:
> See the 'Block Lock Mode' chapter.
> 
> Lock block: 2Ah
> Unlock Block: 23h - start block - 24h - end block
> Lock tight: 2Ch
> Block Lock Status Read: 7Ah - block address

Ah, I see. Yes I remember that I have seen that before, but I was
puzzled by your per page locking question :)

> It would be nice to unlock the rw partitions only.
> But it's weird a bit:
> the mtd_partition may be incomplete before add_mtd_partitions() done.
> After add_mtd_partitions() my startap code has no handle to actual 
> partition info.
> The mtd_partition.mtdp seems only choice, though it prevents partitions 
> from registering...
> So, could couple of lines in add_mtd_partitions() do that work?

I'm not quite understanding, what your problem is.

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.

> BTW. Can I post patches to this list?

Yes

> I've already sent one as attacment, but that message gets bounced
> "awaits moderator approval".

Thats list policy. Attachments have to be approved

tglx

  reply	other threads:[~2005-04-27  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27  7:34 nand locking Timofei V. Bondarenko
2005-04-27  9:00 ` Thomas Gleixner
2005-04-27  9:09   ` Timofei V. Bondarenko
2005-04-27 10:45     ` Thomas Gleixner [this message]
2005-04-27 10:27       ` Timofei V. Bondarenko
2005-04-27 10:32         ` Artem B. Bityuckiy
2005-04-27 11:35         ` Thomas Gleixner
2005-04-27 11:19           ` Timofei V. Bondarenko
2005-04-27 18:27     ` Todd Poynor
2005-04-28  7:00       ` Timofei V. Bondarenko
2005-04-29 22:19         ` Todd Poynor

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=1114598706.879.185.camel@tglx.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=timm@ipi.ac.ru \
    /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