From mboxrd@z Thu Jan  1 00:00:00 1970
From: Craig A. Vanderborgh <craigv@voxware.com>
Date: Thu, 06 Jan 2005 22:48:10 -0500
Subject: [U-Boot-Users] Kernel 2.4.19-rmk7 & Unlock Before Erase w/Strataflash K3
Message-ID: <41DE067A.5050003@voxware.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hello, booters - and Happy New Year!

I am looking for a bit of advice on a seemingly messy problem.  Our 
PXA-255 board uses the K3-type Intel Strataflash chips, the kind you 
have to "unlock before you can erase".  If I do a "protect off all" in 
u-boot BEFORE I boot my kernel, my target board boots the kernel 
correctly, and is able to mount its JFFS2 root filesystem.  If I DON'T 
do "protect off all", the boot fails because Linux cannot write to the 
JFFS2 - because my kernel does not currently "unlock" before it tries to 
erase...

I put an "unlock before erase" fix into my u-boot port - that's why it 
works correctly.  The question is - What is the best way to deal with 
this in the Linux kernel?  Is there some "correct" and/or 
straightforward way to accomplish this??

Thanks in advance,
craig vanderborgh
voxware incorporated