mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: barebox mailing list <barebox@lists.infradead.org>
Subject: Re: problem with env in NOR
Date: Wed, 17 Feb 2010 07:53:29 +0100	[thread overview]
Message-ID: <20100217065329.GW17643@pengutronix.de> (raw)
In-Reply-To: <4B7B0393.2090907@pengutronix.de>

On Tue, Feb 16, 2010 at 09:44:03PM +0100, Marc Kleine-Budde wrote:
> Hello,
> 
> on my PXA270 I put a splash image into the environment. The env image
> with the splash image covers more than one flash sector. (The flash
> sector size is 256 KiB.)
> 
> Loading the environment fails:
> 
> uboot:/ loadenv /dev/env0
> loading environment from /dev/env0
> read: error -262116
> 
> (This fails during boot, too.)
> 
> [frogger@hardanger:barebox (dev/pxa270)]$ grep CFI .config
> CONFIG_HAS_CFI=y
> CONFIG_DRIVER_CFI=y
> # CONFIG_DRIVER_CFI_NEW is not set
> CONFIG_DRIVER_CFI_OLD=y
> CONFIG_CFI_BUFFER_WRITE=y
> 
> Sascha it's probably the problem we discussed the other day, that the
> cfi driver doesn't handle the offset correct. I haven't looked at the
> code though.

Yes, saveenv probably saves the whole environment with one write call
whereas other writes usually don't cross sector boundaries and so the
bug never showed up

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2010-02-17  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 20:44 Marc Kleine-Budde
2010-02-17  6:53 ` Sascha Hauer [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=20100217065329.GW17643@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mkl@pengutronix.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