From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dfu:ext4:fix Fix ext4{read|write} command formatting
Date: Wed, 26 Jun 2013 16:41:28 +0200 [thread overview]
Message-ID: <20130626164128.58eb5542@amdc308.digital.local> (raw)
In-Reply-To: <1372083498-19938-1-git-send-email-l.majewski@samsung.com>
Hi Tom,
> In the following commit:
> "dfu: Support larger than memory transfers."
> SHA1: ea2453d56b8860dbd18a3c517531ffc8dcb5c839
>
> The ext4{read|write} command formatting has been changed. It removed
> a mandatory [sizebytes] parameter.
>
> It prevented from ext4 update via dfu. This commit restored the
> previous behaviour.
Tom, please drop this patch, since it only fixes DFU eMMC write.
Unfortunately after dfu.c code changes to support NAND and arbitrary
files transmission, the eMMC ext4 read needs to be fixed.
I will prepare one patch set, which fixes read and write.
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2013-06-26 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 14:18 [U-Boot] [PATCH] dfu:ext4:fix Fix ext4{read|write} command formatting Lukasz Majewski
2013-06-26 14:41 ` Lukasz Majewski [this message]
2013-06-26 15:05 ` Tom Rini
2013-06-26 15:27 ` 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=20130626164128.58eb5542@amdc308.digital.local \
--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