mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christian Hemp <c.hemp@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Grigory Milev <g.milev@sam-solutions.com>,
	barebox@lists.infradead.org,
	Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
Subject: Re: [PATCH] i.MX6: bbu: Barebox update support for NAND.
Date: Tue, 01 Apr 2014 09:36:29 +0200	[thread overview]
Message-ID: <1396337789.2240.66.camel@lws-hemp> (raw)
In-Reply-To: <20140331084209.GO17250@pengutronix.de>

Hello Sascha,

I have tested the patch on three phyCARD-i.MX6 and three phyFLEX-i.MX6
modules without problems.


Christian


Am Montag, den 31.03.2014, 10:42 +0200 schrieb Sascha Hauer:
> On Thu, Mar 13, 2014 at 07:54:58AM +0100, Sascha Hauer wrote:
> > Hi Dmitry,
> > 
> > On Wed, Mar 12, 2014 at 10:54:11AM +0300, Dmitry Lavnikevich wrote:
> > > This patch implements updating barebox on i.MX6 NAND. In userspace
> > > similar task is performed by freescale kobs-ng utility.
> > > To use this bbu profile nand handler should be registered in board
> > > code with 'imx6_bbu_internal_nand_register_handler' function.
> > 
> > I have the very same patch in the queue, it seems we have duplicated
> > some work. As this version has some shortcomings I'll post my version as
> > an alternative implementation. Also I'll try your version on a board I
> > have here on which my version doesn't work (which is the reason I
> > haven't posted my patch yet)
> 
> The NAND boot on our board finally works. It turned out to be a silly
> bug in the DCD table. The DCD table turned off the GPMI clocks which
> of course prevented the ROM from loading the rest of the image.
> 
> I just resent my version of this patch, but included the missing check
> for a valid image and the confirmation question from your version.
> 
> Maybe you could give this a test on your board.
> 
> Sascha
> 



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

      reply	other threads:[~2014-04-01  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  7:54 Dmitry Lavnikevich
2014-03-13  6:54 ` Sascha Hauer
2014-03-13  7:50   ` Dmitry Lavnikevich
2014-03-20 10:28   ` Dmitry Lavnikevich
2014-03-22  7:06     ` Sascha Hauer
2014-03-31  8:42   ` Sascha Hauer
2014-04-01  7:36     ` Christian Hemp [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=1396337789.2240.66.camel@lws-hemp \
    --to=c.hemp@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=d.lavnikevich@sam-solutions.com \
    --cc=g.milev@sam-solutions.com \
    --cc=s.hauer@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