From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] dfu: allow backend to specify a maximum buffer size
Date: Fri, 20 Jun 2014 09:54:48 +0200 [thread overview]
Message-ID: <20140620095448.1a513a4f@amdc2363> (raw)
In-Reply-To: <1402524216-9999-2-git-send-email-swarren@wwwdotorg.org>
Hi Stephen,
> From: Stephen Warren <swarren@nvidia.com>
>
> CONFIG_SYS_DFU_DATA_BUF_SIZE may be large to allow for FAT/ext layouts
> to transfer large files. However, this means that individual write
> operations will take a long time. Allow backends to specify a maximum
> buffer size, so that each write operation is limited to a smaller data
> block. This prevents the DFU protocol from timing out when e.g.
> writing to SPI flash. I would guess that NAND might benefit from
> setting this value too, but I can't test that.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
Applied to u-boot-dfu
Thanks for the patch.
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2014-06-20 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 22:03 [U-Boot] [PATCH 1/4] dfu: defer parsing of device string to IO backend Stephen Warren
2014-06-11 22:03 ` [U-Boot] [PATCH 2/4] dfu: allow backend to specify a maximum buffer size Stephen Warren
2014-06-20 7:54 ` Lukasz Majewski [this message]
2014-06-11 22:03 ` [U-Boot] [PATCH 3/4] dfu: add free_entity() to struct dfu_entity Stephen Warren
2014-06-20 7:55 ` Lukasz Majewski
2014-06-11 22:03 ` [U-Boot] [PATCH 4/4] dfu: add SF backend Stephen Warren
2014-06-20 7:55 ` Lukasz Majewski
2015-09-21 17:13 ` Fabio Estevam
2015-09-21 17:31 ` Stephen Warren
2015-09-21 17:37 ` Fabio Estevam
2015-09-22 1:50 ` Fabio Estevam
2015-09-22 2:55 ` Fabio Estevam
2015-09-22 3:23 ` Stephen Warren
2015-09-22 3:37 ` Fabio Estevam
2015-09-22 7:23 ` Lukasz Majewski
2014-06-20 7:54 ` [U-Boot] [PATCH 1/4] dfu: defer parsing of device string to IO backend Lukasz Majewski
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=20140620095448.1a513a4f@amdc2363 \
--to=l.majewski@samsung.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