All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] non-blocking flash functions - is this	possible/acceptable?
Date: Tue, 27 Oct 2009 10:03:49 -0400	[thread overview]
Message-ID: <4AE6FDC5.5070106@ge.com> (raw)
In-Reply-To: <4AE6F3D5.5060403@ge.com>

Jerry Van Baren wrote:
> Wolfgang Wegner wrote:
>> Hi,
>>
>> we have an update protocol that normally relies on data being
>> received while the previous block is written to flash.

[snip]

> My 2c: Overlapping data transfer with flash erase/write operations can 
> be beneficial as it can reduce the programming time substantially. 
> (Erase is less beneficial than write since erases don't happen as often 
> and take a relatively long time, so the overlap optimization savings is 
> a smaller percentage of the total erase time - Amdahl's Law.)

By the way, what sort of benefit do you see?  What is your load time 
with and without the non-blocking changes?

[snip]

>> Regards,
>> Wolfgang

Thanks,
gvb

  reply	other threads:[~2009-10-27 14:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 12:51 [U-Boot] non-blocking flash functions - is this possible/acceptable? Wolfgang Wegner
2009-10-27 13:21 ` Jerry Van Baren
2009-10-27 14:03   ` Jerry Van Baren [this message]
2009-10-27 15:22     ` Wolfgang Wegner
2009-10-27 15:57       ` Jerry Van Baren
2009-10-27 15:24   ` Wolfgang Wegner
2009-10-27 18:58 ` Wolfgang Denk
2009-10-30 14:48   ` [U-Boot] [RFC PATCH] Implementation of non-blocking flash write/erase/status check functions Wolfgang Wegner
2009-10-30 15:02     ` Wolfgang Wegner
2009-10-30 18:22     ` Wolfgang Denk
2009-11-02 16:26       ` [U-Boot] [PATCH] " Wolfgang Wegner
2009-11-02 16:33       ` [U-Boot] [RFC PATCH] Implementation of " Wolfgang Wegner
2009-12-09 16:00       ` [U-Boot] [PATCH RFC v2] " Wolfgang Wegner
2010-01-22 10:03         ` Wolfgang Wegner
2010-01-22 12:03           ` Wolfgang Denk
2010-01-25  8:35             ` Stefan Roese

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=4AE6FDC5.5070106@ge.com \
    --to=gerald.vanbaren@ge.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.