All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: No NAND access on AT91SAM9G20-EK
Date: Fri, 18 Feb 2011 09:55:24 +0100	[thread overview]
Message-ID: <20110218085524.GD17919@game.jcrosoft.org> (raw)
In-Reply-To: <4D5DA526.1070801@pengutronix.de>

On 23:45 Thu 17 Feb     , Marc Kleine-Budde wrote:
> On 02/17/2011 10:50 PM, Marc Kleine-Budde wrote:
> > 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.
> 
> I just found in linux Kconfig:
> 
> > config MTD_NAND_ATMEL_ECC_HW
> > 	bool "Hardware ECC"
> > 	depends on ARCH_AT91SAM9263 || ARCH_AT91SAM9260 || AVR32
> 
> The sam9g45 is not listed here....Maybe we should hardcode "soft" in
> barebox for the 9g45
I prefer we detect it as we could change it the kernel

Best Regards,
J.

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

      reply	other threads:[~2011-02-18  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 11:09 No NAND access on AT91SAM9G20-EK 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
2011-02-17 22:45     ` Marc Kleine-Budde
2011-02-18  8:55       ` Jean-Christophe PLAGNIOL-VILLARD [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=20110218085524.GD17919@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.