public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Craig A. Vanderborgh <craigv@voxware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Kernel 2.4.19-rmk7 & Unlock Before Erase w/Strataflash K3
Date: Thu, 06 Jan 2005 22:48:10 -0500	[thread overview]
Message-ID: <41DE067A.5050003@voxware.com> (raw)

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

             reply	other threads:[~2005-01-07  3:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07  3:48 Craig A. Vanderborgh [this message]
2005-01-07  8:33 ` [U-Boot-Users] Kernel 2.4.19-rmk7 & Unlock Before Erase w/Strataflash K3 Wolfgang Denk

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=41DE067A.5050003@voxware.com \
    --to=craigv@voxware.com \
    --cc=u-boot@lists.denx.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