From: Nishanth Menon <menon.nishanth@gmail.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH/RFC] ARM: OMAP: unlock flash device during boot
Date: Thu, 18 Oct 2007 20:23:58 -0500 [thread overview]
Message-ID: <4718072E.7020104@gmail.com> (raw)
In-Reply-To: <47176E1C.3060009@mvista.com>
Kevin Hilman stated on 10/18/2007 9:30 AM:
> Woodruff, Richard wrote:
>> Long ago when the part size changed one version of the omap-nor driver did need to unlock partitions. This was done on some internal tree version.
>>
>> By partitions I mean physical ones, inside the NOR part. Not mtd_partitions(). This only needed to be done on a per-partition basis not a per-sector one.
>>
>> These physical partitions, allow for simultaneous XIP and programming on the same NOR chip. One partition can be in status mode while another has code executing out of it.
>>
>> It kind of looks like this patch was aiming to do this.
>
> FWIW, this patch was taken from the TI kernels on linux.omap.com which
> have the same call to unlock in the probe hook.
>
I recollect some time back we had a similar discussion on a possibility of:
a) partition 1 (boot readonly partition) having a basic filesystem which
would unlock partition 2
b) partition 2: read/write which would contain all the stuff that
filesystem would like to move around.
This would allow for map drivers to do nothing special on bootup.
Regards,
Nishanth Menon
next prev parent reply other threads:[~2007-10-19 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 22:25 [PATCH/RFC] ARM: OMAP: unlock flash device during boot Kevin Hilman
2007-10-17 23:25 ` Woodruff, Richard
2007-10-18 14:30 ` Kevin Hilman
2007-10-19 1:23 ` Nishanth Menon [this message]
2007-10-19 14:07 ` Amit Kucheria
2007-10-31 12:53 ` Tony Lindgren
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=4718072E.7020104@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.com \
/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