From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] split nand writes
Date: Thu, 20 Dec 2012 17:18:14 -0600 [thread overview]
Message-ID: <1356045494.21086.13@snotra> (raw)
In-Reply-To: <50D30625.3070401@nedap.com> (from jaap.dejong@nedap.com on Thu Dec 20 06:35:49 2012)
On 12/20/2012 06:35:49 AM, Jaap de Jong wrote:
>
> 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?
There isn't.
-Scott
prev parent reply other threads:[~2012-12-20 23:18 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
2012-12-20 23:18 ` Scott Wood [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=1356045494.21086.13@snotra \
--to=scottwood@freescale.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