public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/4] dfu: add SF backend
Date: Mon, 21 Sep 2015 21:23:21 -0600	[thread overview]
Message-ID: <5600C9A9.7020107@wwwdotorg.org> (raw)
In-Reply-To: <CAOMZO5BYw0gzx21ea_UHc+hiWyWGqxkENsC82v2ZdtHVb9juYA@mail.gmail.com>

On 09/21/2015 08:55 PM, Fabio Estevam wrote:
> On Mon, Sep 21, 2015 at 10:50 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> Stephen,
>>
>> On Mon, Sep 21, 2015 at 2:37 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>> On Mon, Sep 21, 2015 at 2:31 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>
>>>> I haven't tested SF support recently (only MMC). However, it should still
>>>> work:-) Are you using ci_udc? If so, make sure you have this very recent
>>>> patch:
>>>>
>>>>> commit b337b3b2a53f112a217f4bd31307b02f830bb787
>>>>> Author: Stephen Warren <swarren@nvidia.com>
>>>>> Date:   Fri Sep 11 17:10:02 2015 -0600
>>>>>
>>>>>     usb: ci_udc: fix emissions of ZLPs
>>>
>>> Yes, I am using ci_udc and this patch is applied.
>>
>> Do you recall what you used as 'dfu_alt_info' variable when flashing
>> SPI via DFU?
> 
> Nevermind. I fixed the issue and will submit the patch shortly.

Oh good:-)

I was going to give you my dfu_alt_info, but it's at work right now, so
I was waiting until tomorrow. I did try to repro this, but I was having
a lot of trouble with both the two boards I have that have SPI, so
wasn't able to test yet.

One thing I did notice: dfu_sf.c's parsing code doesn't work with
multiple entries in dfu_alt_info (e.g. for different partitions) since
the parsing of the device parameter (to the dfu command; not part of
dfu_info) modifies that parameter so it can't be parsed the second time
around. Since you're set up to test this, perhaps you could fix it too?
I assume all it'd need is to add a strdup()/free() to the start/end of
the alt info parsing function?

  reply	other threads:[~2015-09-22  3:23 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
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 [this message]
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=5600C9A9.7020107@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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