All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX6 nand bootupdate
Date: Wed, 15 Jun 2016 14:40:31 +0800	[thread overview]
Message-ID: <20160615064029.GA22546@linux-7smt.suse> (raw)
In-Reply-To: <alpine.LFD.2.20.1606141117220.28557@maverick.koi8.net>

Hi Sergey,

On Tue, Jun 14, 2016 at 11:32:37AM -0700, Sergey Kubushyn wrote:
>Here is the initial support for writing i.MX6 NAND U-Boot into NAND
>with all FCB and DBBT stuff as required.
>
>Just build U-Boot for NAND as u-boot.imx, load it somehow in RAM and
>say "nand bootupdate [addr] [size]". It will create all necessary
>structures and write everything as needed.
>
>No SPL required, just plain single stage U-Boot. Supposed to write into
>first NAND partition, recommended size 4MiB. Creates 4 redundant copies
>of boot structures in first 4 sectors and 2 redundant copies of U-Boot
>in the remaining space.
>
>Tested on a Variscite VAR-SOM-SOLO based board with i.MX6DL SoC. Will
>probably post that board support files later, when config is cleaned up
>so people could have a working NAND boot DCD portion to be able actually
>use those braindead SOMs.

I would like to test this, but seems this patch is not rebased
to lastest U-Boot (:

Thanks,
Peng.

[...]

  reply	other threads:[~2016-06-15  6:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 18:32 [U-Boot] [PATCH] i.MX6 nand bootupdate Sergey Kubushyn
2016-06-15  6:40 ` Peng Fan [this message]
2016-06-15 10:14 ` Stefano Babic
2016-06-15 19:42   ` Sergey Kubushyn
2016-06-16  8:44     ` Stefano Babic
2016-06-16  9:56   ` Ladislav Michl

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=20160615064029.GA22546@linux-7smt.suse \
    --to=van.freenix@gmail.com \
    --cc=u-boot@lists.denx.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.