public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] split nand writes
Date: Thu, 20 Dec 2012 13:35:49 +0100	[thread overview]
Message-ID: <50D30625.3070401@nedap.com> (raw)
In-Reply-To: <1355957232.12062.12@snotra>


On 12/19/2012 11:47 PM, Scott Wood wrote:
> On 12/19/2012 09:43:01 AM, Jaap de Jong wrote:
>> Hi All,
>> suppose the image I want to flash is bigger than the available ram in
>> the unit.
>> Is there a way to copy the image f.i. in pieces into the flash?
>> nand write should have a 'continue on last block' option for that
>> purpose.
> Something like that would be nice.
>
> These patches are relevant:
> http://patchwork.ozlabs.org/patch/204939/
> http://patchwork.ozlabs.org/patch/204940/
>
That could do the trick also. You would have to do some arithmetic to 
calculate the next startaddress in the flash.
So there is not an out-of-the-box solution at the moment?

  reply	other threads:[~2012-12-20 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 15:43 [U-Boot] split nand writes Jaap de Jong
2012-12-19 22:47 ` Scott Wood
2012-12-20 12:35   ` Jaap de Jong [this message]
2012-12-20 23:18     ` Scott Wood

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=50D30625.3070401@nedap.com \
    --to=jaap.dejong@nedap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox