From: Robert Berger <gmane@reliableembeddedsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ehci-hcd: Allow cleanups to happen on an EHCI timeout.
Date: Sun, 26 Jun 2011 11:04:10 +0300 [thread overview]
Message-ID: <4E06E7FA.3080405@reliableembeddedsystems.com> (raw)
In-Reply-To: <4E0636D0.9010107@gmail.com>
Hi Joel,
On 06/25/2011 10:28 PM, Joel A Fernandes wrote:
> ---
> Robert, Could you see if this patch solves the issue you're seeing without
> increasing the timeout?
The tftp session retrieves the uImage with your patch and a timeout of 5000:
OMAP3 beagleboard.org # tftp 0x82000000 beagle-xm-rev-c/uImage
Waiting for Ethernet connection... done.
Using sms0 device
TFTP from server 192.168.5.5; our IP address is 192.168.5.3
Filename 'beagle-xm-rev-c/uImage'.
Load address: 0x82000000
Loading: #################################################################
############################################################EHCI timed
out on TD - token=0x88008d80
T EHCI timed out on TD - token=0x88008d80
T EHCI timed out on TD - token=0x88008d80
T #####
###################################EHCI timed out on TD - token=0x88008d80
T EHCI timed out on TD - token=0x88008d80
T EHCI timed out on TD - token=0x88008d80
T #EHCI timed out on TD - token=0x88008d80
T ##############
done
Bytes transferred = 2632196 (282a04 hex)
OMAP3 beagleboard.org #
Regards,
Robert...fortune says today:There is no TRUTH. There is no REALITY.
There is no CONSISTENCY. There are no ABSOLUTE STATEMENTS I'm very
probably wrong.
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2011-06-26 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6885F5E-CA69-451D-B111-36836A0164E0@beagleboard.org>
2011-06-25 19:28 ` [U-Boot] [PATCH] ehci-hcd: Allow cleanups to happen on an EHCI timeout Joel A Fernandes
2011-06-26 8:04 ` Robert Berger [this message]
2011-07-28 23:22 ` 2bluesc at gmail.com
2011-06-29 22:32 ` Simon Glass
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=4E06E7FA.3080405@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.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