From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] thor integration with ci_udc
Date: Thu, 14 Aug 2014 08:26:01 +0200 [thread overview]
Message-ID: <20140814082601.7559d9c9@amdc2363> (raw)
In-Reply-To: <CAAhU36guSYmwxPfSWQ5GBwp5Xw8qW1i_uawbwGxE-OEEXG0LMQ@mail.gmail.com>
Hi S,
> Hi Stephen,
>
> Thanks for your reply. I used your patches after 2014.07 and able to
> test the DFU successfully using ci_udc,but not thor it looks like
> that it needs some patches to work for thor.
I can only add that thor shares code with dfu to perform correct
operation.
At least on the s3c_hsotg UDC driver I didn't need any extra
modifications.
>
> Regards,
> DP
>
>
> On Wed, Aug 13, 2014 at 9:38 PM, Stephen Warren
> <swarren@wwwdotorg.org> wrote:
>
> > On 08/13/2014 04:58 AM, S Durga Prasad Paladugu wrote:
> >
> >> Hi,
> >>
> >> Does anyone tested by integrating thor functionality with the
> >> ci_udc driver
> >> instead of samsung s3c_udc_otg? I am trying to do the same on my
> >> zynq board
> >> then the enumeration was successful but not able to download the
> >> file using
> >> lthor.
> >> Any other inputs on this would be fine.
> >>
> >
> > I haven't used the Thor protocol, but I have used both USB mass
> > storage (UMS) and Device Firmware Upgrade (DFU) with success on an
> > NVIDIA Tegra system. DFU at least required some patches that have
> > been merged after v2014.07, but I think that was all to the DFU
> > stack, not ci_udc itself.
> >
>
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
prev parent reply other threads:[~2014-08-14 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 10:58 [U-Boot] thor integration with ci_udc S Durga Prasad Paladugu
2014-08-13 16:08 ` Stephen Warren
2014-08-13 17:49 ` S Durga Prasad Paladugu
2014-08-14 6:26 ` Lukasz Majewski [this message]
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=20140814082601.7559d9c9@amdc2363 \
--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