From: "Timofei V. Bondarenko" <timm@ipi.ac.ru>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: nand locking
Date: Wed, 27 Apr 2005 13:09:21 +0400 [thread overview]
Message-ID: <426F56C1.6020204@ipi.ac.ru> (raw)
In-Reply-To: <1114592403.879.175.camel@tglx.tec.linutronix.de>
Thomas Gleixner wrote:
> On Wed, 2005-04-27 at 11:34 +0400, Timofei V. Bondarenko wrote:
>
>>Is there a straight way to lock/unlock nand pages?
>>
>
> You talk about "the nand chip". Which chip is it exactly and what makes
> you believe that it has a per page locking feature ?
Samsung k9f5608u0c-d
http://www.samsung.com/Products/Semiconductor/Flash/NAND/256Mbit/K9F5608U0C/K9F5608U0C.htm
http://www.samsung.com/Products/Semiconductor/Flash/NAND/256Mbit/K9F5608U0C/ds_k9f5608u0c_rev32.pdf
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
I'm really using that chip and could provide some code.
The chip is locked at power on.
So i'm checking the locking status at startup and then unlocking it
(using range of pages).
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?
BTW. Can I post patches to this list?
I've already sent one as attacment, but that message gets bounced
"awaits moderator approval".
Regards.
Timofei.
next prev parent reply other threads:[~2005-04-27 9:09 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 [this message]
2005-04-27 10:45 ` Thomas Gleixner
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=426F56C1.6020204@ipi.ac.ru \
--to=timm@ipi.ac.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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