From: Vitaly Kuzmichev <vkuzmichev@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB CDC branch
Date: Wed, 14 Jul 2010 14:06:18 +0400 [thread overview]
Message-ID: <4C3D8C1A.1090103@mvista.com> (raw)
In-Reply-To: <AANLkTim-TN6W6LAo2qby8XZuKKb0C0zjBjGTvQoRdQSp@mail.gmail.com>
Hi,
> We also implemented the CDC and RNDIS on our board and working well.
> If you merge your usb gadget tree then we will send the patches also.
Have you shared this anywhere (public git?)?
I would like to look at your patches to sync them with mine.
___
WBR,
Vitaly.
On 07/14/2010 11:10 AM, Kyungmin Park wrote:
> On Wed, Jul 14, 2010 at 4:48 AM, Remy Bohmer <linux@bohmer.net> wrote:
>> Hi,
>>
>> 2010/7/13 Vitaly Kuzmichev <vkuzmichev@mvista.com>:
>>> FYI I'm doing some work on this branch too.
>>
>> Great!
>>
>>> Actually I have ported it to 2010.03
>>
>> What do you mean with ported to 2010.03?
>> It was already working on latest git, do you mean you backported it to
>> an older version? (I would not expect this would be a big difference
>> though)
>>
>>> added RNDIS support
>>
>> Is RNDIS working stable? We had quite some troubles with it,
>> especially with BSODs on those Windows boxes...
>> The device unplug/plug behaviour was a pain for RNDIS, hence the
>> reason why we removed that from the code.
>> But, I do not want to scare you off from this rndis work, please
>> continue. Maybe you can get it to work properly :-)
>>
>> We use it to communicate with a CDC driver on a Windows XP-embedded
>> host (http://www.thesycon.de/eng/usb_cdcecm.shtml). CDC works much
>> more stable, and much more faster compared to rndis.
>
> We also implemented the CDC and RNDIS on our board and working well.
> If you merge your usb gadget tree then we will send the patches also.
>
> To Minkyu,
> Can you prepare the patches and send to u-boot?
>
> Thank you,
> Kyungmin Park
>
>>
>>> and made integration into 'usb' command.
>>
>> Great!
>>
>>> However these changes aren't tested yet so the work is still under progress.
>>>
>>> Probably someone knows about any possible issues with CDC/RNDIS support?
>>
>> See above.
>> and CDC is working stable, no known issues with it.
>>
>> At least one hint: First get CDC working on your hardware before you
>> start to connect rndis, that would allow you to get the udc driver and
>> all other levels of SW working properly and that you would only need
>> to focus on rndis protocol rarities after that. And to prevent that
>> you are debugging all kinds of undocumented rndis calls from the
>> Windows host you could use a Linux host instead with the
>> Linux-rndis-usb-host driver ;-)
>>
>>> And also I would like to know the answers to Stefano's questions.
>>
>> See my other reply.
>>
>> I would suggest to merge all work in progress in the u-boot-usb/CDC
>> branch from which we push it to mainline.
>>
>>
>> Kind regards,
>>
>> Remy
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
next prev parent reply other threads:[~2010-07-14 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 7:26 [U-Boot] USB CDC branch Stefano Babic
2010-07-13 10:19 ` Vitaly Kuzmichev
2010-07-13 19:48 ` Remy Bohmer
2010-07-14 7:10 ` Kyungmin Park
2010-07-14 10:06 ` Vitaly Kuzmichev [this message]
2010-07-14 10:02 ` Vitaly Kuzmichev
2010-07-14 11:09 ` Remy Bohmer
2010-07-13 19:24 ` Remy Bohmer
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=4C3D8C1A.1090103@mvista.com \
--to=vkuzmichev@mvista.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