From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: No NAND access on AT91SAM9G20-EK
Date: Thu, 17 Feb 2011 22:50:25 +0100 [thread overview]
Message-ID: <4D5D9821.6070500@pengutronix.de> (raw)
In-Reply-To: <20110210114858.GC11255@game.jcrosoft.org>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
Hello Jean-Christophe,
On 02/10/2011 12:48 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> which ecc did u use before?
I'm working on a at91sam9m10ek, using latest origin/next.
The ecc-mode is "hardcoded" to NAND_ECC_HW in
arch/arm/mach-at91/at91sam9g45_devices.c. I've got the same -74 problem
when reading from the nand.
Barebox fails to read the environment, even if barebox has written it.
After changing the ecc mode to soft the env can be read and written
without problems.
I ported the atmel nand driver from linux-2.6.37, which had no
significant differences.
cheers, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-02-17 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 11:09 Mickael Chazaux
2011-02-10 11:48 ` Jean-Christophe PLAGNIOL-VILLARD
2011-02-10 13:47 ` Mickael Chazaux
2011-02-17 21:50 ` Marc Kleine-Budde [this message]
2011-02-17 22:45 ` Marc Kleine-Budde
2011-02-18 8:55 ` Jean-Christophe PLAGNIOL-VILLARD
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=4D5D9821.6070500@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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