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 1/2] usb: ci_udc: allow multiple buffer allocs per ep
Date: Thu, 12 Jun 2014 11:42:55 -0600	[thread overview]
Message-ID: <5399E69F.1030307@wwwdotorg.org> (raw)
In-Reply-To: <201406121930.26124.marex@denx.de>

On 06/12/2014 11:30 AM, Marek Vasut wrote:
> On Thursday, June 12, 2014 at 05:55:40 PM, Stephen Warren wrote:
> [...]
>>>> I'm slightly confused by this log. Do you have 2 boards running U-Boot,
>>>> one running the USB controller in device mode, and this is the log from
>>>> some other board that's talking to that first board?
>>>
>>> I have one board connect to a PC. The log shows two different errors
>>> happening on the board. The first log shows a tftp command on the board
>>> stopping with a timeout after receiving some packets. The second log
>>> shows a tftp command on the same board throwing an error before
>>> receiving any packet.
>>
>> So U-Boot is running on the board, and the logs are from the board, i.e.
>> you're running the "tftp" command in U-Boot on the board?
>>
>> If so, I'm confused how ci_udc comes into play at all; doesn't "tftp"
>> use the USB controller in host mode, whereas ci_udc is only used for
>> device mode?
> 
> U-Boot CDC ethernet support, that's pretty normal mode of operation ;-)

Oh, so that makes U-Boot into a kind of virtual NIC where the packets
don't go anywhere but U-Boot's internal network stack, and that feature
runs in the background with the interactive shell still fully operation
then?

All the USB device mode support I've used is a synchronous/blocking
shell command (dfu, ums) rather than something that runs in the
background, so I figured CDC Ethernet would work the same.

Perhaps I should try and get CDC Ethernet working... Can both
CONFIG_USB_GADGET and CONFIG_USB_ETHER co-exist I wonder? Actually,
U-Boot acting as a USB serial port running at the same time as dfu or
ums would be more useful to me.

  reply	other threads:[~2014-06-12 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 23:48 [U-Boot] [PATCH 1/2] usb: ci_udc: allow multiple buffer allocs per ep Stephen Warren
2014-05-05 23:48 ` [U-Boot] [PATCH 2/2] usb: ums: remove ci_udc special case Stephen Warren
2014-05-07 21:31   ` Marek Vasut
2014-05-07 21:31 ` [U-Boot] [PATCH 1/2] usb: ci_udc: allow multiple buffer allocs per ep Marek Vasut
2014-06-02 22:57 ` Jörg Krause
2014-06-02 23:02   ` Jörg Krause
2014-06-10 19:34     ` Stephen Warren
2014-06-12  8:36       ` Jörg Krause
2014-06-12 12:59         ` Marek Vasut
2014-06-12 15:55         ` Stephen Warren
2014-06-12 17:30           ` Marek Vasut
2014-06-12 17:42             ` Stephen Warren [this message]
2014-06-16  1:00               ` Marek Vasut

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=5399E69F.1030307@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