From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 05/14] dfu: allow read with 0 data for EOF indication
Date: Tue, 17 Sep 2019 12:28:52 +0200 [thread overview]
Message-ID: <20190917122852.10d8c0f0@jawa> (raw)
In-Reply-To: <20190913141930.15784-6-patrick.delaunay@st.com>
Hi Patrick,
> This patch allows into the DFU backend to indicate that there is no
> remaining data (for EOF for example). That allows users to read a
> buffer greater than the device size; the dfu stack stops the read
> request when the backend return a length=0 without error.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
>
> drivers/dfu/dfu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/dfu/dfu.c b/drivers/dfu/dfu.c
> index 8bd5216017..50919fcae9 100644
> --- a/drivers/dfu/dfu.c
> +++ b/drivers/dfu/dfu.c
> @@ -396,6 +396,8 @@ static int dfu_read_buffer_fill(struct dfu_entity
> *dfu, void *buf, int size) debug("%s: Read error!\n", __func__);
> return ret;
> }
> + if (dfu->b_left == 0)
> + break;
I guess that this is the use case for sending commands?
Could you provide a more descriptive use case for this change (the
description in the above commit message is not enough for me to get it).
> dfu->offset += dfu->b_left;
> dfu->r_left -= dfu->b_left;
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190917/161ad24c/attachment.sig>
next prev parent reply other threads:[~2019-09-17 10:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 14:19 [U-Boot] [PATCH 01/14] dfu: cosmetic: cleanup sf to avoid checkpatch error Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 02/14] dfu: sf: add partition support for nor backend Patrick Delaunay
2019-09-16 22:12 ` Lukasz Majewski
2019-09-13 14:19 ` [U-Boot] [PATCH 03/14] dfu: prepare the support of multiple interface Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 04/14] dfu: allow to manage DFU on several devices Patrick Delaunay
2019-09-17 10:25 ` Lukasz Majewski
2019-09-17 11:28 ` Patrick DELAUNAY
2019-09-13 14:19 ` [U-Boot] [PATCH 05/14] dfu: allow read with 0 data for EOF indication Patrick Delaunay
2019-09-17 10:28 ` Lukasz Majewski [this message]
2019-09-18 11:45 ` Patrick DELAUNAY
2019-09-13 14:19 ` [U-Boot] [PATCH 06/14] dfu: add backend for MTD device Patrick Delaunay
2019-09-17 10:35 ` Lukasz Majewski
2019-09-17 11:40 ` Patrick DELAUNAY
2019-09-13 14:19 ` [U-Boot] [PATCH 07/14] dfu: add partition support for MTD backend Patrick Delaunay
2019-09-17 10:38 ` Lukasz Majewski
2019-09-17 12:03 ` Patrick DELAUNAY
2019-09-13 14:19 ` [U-Boot] [PATCH 08/14] dfu: add DFU virtual backend Patrick Delaunay
2019-09-17 10:42 ` Lukasz Majewski
2019-09-13 14:19 ` [U-Boot] [PATCH 09/14] dfu: add callback for flush and initiated operation Patrick Delaunay
2019-09-17 10:44 ` Lukasz Majewski
2019-09-17 12:52 ` Patrick DELAUNAY
2019-09-13 14:19 ` [U-Boot] [PATCH 10/14] stm32mp1: activate DFU support and command MTD Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 11/14] stm32mp1: activate SET_DFU_ALT_INFO Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 12/14] stp32mp1: configs: activate CONFIG_MTD_SPI_NAND Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 13/14] stm32mp1: board: add spi nand support Patrick Delaunay
2019-09-13 14:19 ` [U-Boot] [PATCH 14/14] stm32mp1: add support for virtual partition read Patrick Delaunay
2019-09-16 21:49 ` [U-Boot] [PATCH 01/14] dfu: cosmetic: cleanup sf to avoid checkpatch error 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=20190917122852.10d8c0f0@jawa \
--to=lukma@denx.de \
--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.