All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] usb: dfu: make nand upload working
Date: Mon, 14 Oct 2013 15:25:58 +0800	[thread overview]
Message-ID: <525B9C86.5050801@atmel.com> (raw)
In-Reply-To: <20131012231914.0e4516f9@jawa>

Hi Lukasz Majewski,

On 10/13/2013 05:19, Lukasz Majewski wrote:
> On Sat, 12 Oct 2013 15:47:14 +0800
> Bo Shen <voice.shen@atmel.com> wrote:
>
>> If won't pass value to dfu->r_left, it always 0, make no transfer,
>> the dfu-util on host side report failed. So, before starting transfer,
>> pass the value, then nand uploading can work.
>>
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>>
>> ---
>>   drivers/dfu/dfu.c |    1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/dfu/dfu.c b/drivers/dfu/dfu.c
>> index 56b21c7..3c3ad1b 100644
>> --- a/drivers/dfu/dfu.c
>> +++ b/drivers/dfu/dfu.c
>> @@ -274,6 +274,7 @@ int dfu_read(struct dfu_entity *dfu, void *buf,
>> int size, int blk_seq_num) if (dfu->i_buf_start == NULL)
>>   			return -ENOMEM;
>>
>> +		dfu->r_left = dfu->data.nand.size;
>
> Please do not add nand related code to "generic" DFU code. This can
> damage DFU operation with other memories (like eMMC).
>
> Such code shall be added to dfu_nand.c file.

Thanks for point out this.
I will check it.

>>   		ret = dfu->read_medium(dfu, 0, dfu->i_buf_start,
>> &dfu->r_left); if (ret != 0) {
>>   			debug("%s: failed to get r_left\n",
>> __func__);
>
> Best regards,
>
> Lukasz Majewski
>

Best Regards,
Bo Shen

  parent reply	other threads:[~2013-10-14  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12  7:47 [U-Boot] [RFC PATCH] usb: dfu: make nand upload working Bo Shen
2013-10-12 21:19 ` Lukasz Majewski
2013-10-13 20:50   ` Marek Vasut
2013-10-14  7:25   ` Bo Shen [this message]
2013-10-16  9:00     ` Bo Shen
2013-11-01  1:20       ` Bo Shen

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=525B9C86.5050801@atmel.com \
    --to=voice.shen@atmel.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.