Searched hist:ea2453d56b8860dbd18a3c517531ffc8dcb5c839 (Results 1 – 4 of 4) sorted by relevance
/openbmc/u-boot/drivers/dfu/ |
H A D | dfu_mmc.c | 051f9a3eedb13eb29151917e38231e37a4383fe5 Fri Jun 28 11:41:49 CDT 2013 Łukasz Majewski <l.majewski@samsung.com> dfu:ext4:fix Fix ext4{read|write} command formatting
In the following commit: "dfu: Support larger than memory transfers." SHA1: ea2453d56b8860dbd18a3c517531ffc8dcb5c839
The ext4{read|write} command formatting has been changed. It removed a write mandatory [sizebytes] parameter.
It extents DFU_FS_EXT4 case at mmc_file_op to provide mandatory parameter for DFU write.
Signed-off-by: Lukasz Majewski <l.majewski@samsung.com> Cc: Tom Rini <trini@ti.com> Cc: Pantelis Antoniou <panto@antoniou-consulting.com> Cc: Marek Vasut <marex@denx.de> Cc: Heiko Schocher <hs@denx.de> ea2453d56b8860dbd18a3c517531ffc8dcb5c839 Thu Mar 14 00:32:48 CDT 2013 Pantelis Antoniou <panto@antoniou-consulting.com> dfu: Support larger than memory transfers.
Previously we didn't support upload/download larger than available memory. This is pretty bad when you have to update your root filesystem for example.
This patch removes that limitation (and the crashes when you transfered any file larger than 4MB) by making raw image writes be done in chunks and making file maximum size be configurable.
The sequence number is a 16 bit counter; make sure we handle rollover correctly. This fixes the wrong transfers for large (> 256MB) images.
Also utilize a variable to handle initialization, so that we don't rely on just the counter sent by the host.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Tom Rini <trini@ti.com>
|
H A D | dfu.c | ea2453d56b8860dbd18a3c517531ffc8dcb5c839 Thu Mar 14 00:32:48 CDT 2013 Pantelis Antoniou <panto@antoniou-consulting.com> dfu: Support larger than memory transfers.
Previously we didn't support upload/download larger than available memory. This is pretty bad when you have to update your root filesystem for example.
This patch removes that limitation (and the crashes when you transfered any file larger than 4MB) by making raw image writes be done in chunks and making file maximum size be configurable.
The sequence number is a 16 bit counter; make sure we handle rollover correctly. This fixes the wrong transfers for large (> 256MB) images.
Also utilize a variable to handle initialization, so that we don't rely on just the counter sent by the host.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Tom Rini <trini@ti.com>
|
/openbmc/u-boot/include/ |
H A D | dfu.h | ea2453d56b8860dbd18a3c517531ffc8dcb5c839 Thu Mar 14 00:32:48 CDT 2013 Pantelis Antoniou <panto@antoniou-consulting.com> dfu: Support larger than memory transfers.
Previously we didn't support upload/download larger than available memory. This is pretty bad when you have to update your root filesystem for example.
This patch removes that limitation (and the crashes when you transfered any file larger than 4MB) by making raw image writes be done in chunks and making file maximum size be configurable.
The sequence number is a 16 bit counter; make sure we handle rollover correctly. This fixes the wrong transfers for large (> 256MB) images.
Also utilize a variable to handle initialization, so that we don't rely on just the counter sent by the host.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Tom Rini <trini@ti.com>
|
/openbmc/u-boot/ |
H A D | README | ea2453d56b8860dbd18a3c517531ffc8dcb5c839 Thu Mar 14 00:32:48 CDT 2013 Pantelis Antoniou <panto@antoniou-consulting.com> dfu: Support larger than memory transfers.
Previously we didn't support upload/download larger than available memory. This is pretty bad when you have to update your root filesystem for example.
This patch removes that limitation (and the crashes when you transfered any file larger than 4MB) by making raw image writes be done in chunks and making file maximum size be configurable.
The sequence number is a 16 bit counter; make sure we handle rollover correctly. This fixes the wrong transfers for large (> 256MB) images.
Also utilize a variable to handle initialization, so that we don't rely on just the counter sent by the host.
Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> Signed-off-by: Tom Rini <trini@ti.com>
|