From: Tony Lindgren <tony@atomide.com>
To: Amit Kucheria <kucheria.amit@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH/RFC] ARM: OMAP: unlock flash device during boot
Date: Wed, 31 Oct 2007 05:53:45 -0700 [thread overview]
Message-ID: <20071031125345.GE32547@atomide.com> (raw)
In-Reply-To: <52d486620710190707n29a00019u15b9db7196f22f7b@mail.gmail.com>
* Amit Kucheria <kucheria.amit@gmail.com> [071019 07:09]:
> On 10/18/07, Kevin Hilman <khilman@mvista.com> wrote:
> > The bootloader may lock the flash device upon booting. This requires
> > the use of 'flash_unlock' on each partition before using them.
> >
> > However, when booting from flash the MTD driver is unable to "mark
> > space as dirty" since the device is locked. This results lots of boot
> > warnings from the MTD layer.
> >
> > The MTD driver for OMAP needs to unlock the device during init so
> > booting from flash can work without errors.
>
> This patch does fix the copious amounts of the following messages that
> I get when I put a jffs2 filesystem on the NOR flash.
>
> "Erase at 0x012e0000 failed immediately: -EROFS. Is the sector locked?
> Dec 31 18:00:13 12 user.info ker<5>Write of 68 bytes at 0x0026111c
> failed. returned -30, retlen 0
> Write of 68 bytes at 0x0026111c failed. returned -30, retlen 0
> nel: serial8250.0: ttyS0 at MMIO<5>Not marking the space at 0x0026111c
> as dirty because the flash driver returned retlen zero
> Not marking the space at 0x0026111c as dirty because the flash driver
> returned retlen zero
> 0x4806a000 (irq = 72) is a ST16<5>Write of 68 bytes at 0x0026111c
> failed. returned -30, retlen 0
> Write of 68 bytes at 0x0026111c failed. returned -30, retlen 0
> 654
> <5>Not marking the space at 0x0026111c as dirty because the flash
> driver returned retlen zero
> Not marking the space at 0x0026111c as dirty because the flash driver
> returned retlen zero
> <4>Erase at 0x012c0000 failed immediately: -EROFS. Is the sector locked?
> Erase at 0x012c0000 failed immediately: -EROFS. Is the sector locked?
> <4>Erase at 0x012a0000 failed immediately: -EROFS. Is the sector locked?
> Erase at 0x012a0000 failed immediately: -EROFS. Is the sector locked?"
I'll push this today. If somebody comes up with a better solution, then
let's consider that.
Tony
prev parent reply other threads:[~2007-10-31 12:53 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
2007-10-19 14:07 ` Amit Kucheria
2007-10-31 12:53 ` Tony Lindgren [this message]
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=20071031125345.GE32547@atomide.com \
--to=tony@atomide.com \
--cc=kucheria.amit@gmail.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