From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] USB storage performance EHCI question
Date: Fri, 14 Jan 2011 20:41:06 -0800 [thread overview]
Message-ID: <4D312562.1020806@caviumnetworks.com> (raw)
In-Reply-To: <20110114091904.6A250160689@gemini.denx.de>
On 1/14/2011 1:19 AM, Wolfgang Denk wrote:
> Dear Aaron Williams,
>
> please always keep the ML on cc:
>
> In message<4D2FA7F0.7020900@caviumnetworks.com> you wrote:
>> It is based off of 2010.09 but I have applied all of the latest USB
>> updates from GIT with the exception of the multiple LUN support (this
>> breaks the SanDisk Cruzer because the Cruzer reports max lun=1). All
>> caches are enabled and this is on a 1.2GHz MIPS which is cache-coherent
>> (no need to flush/invalidate).
> Maybe there are other issues with your code. It's hard to comment on
> onknown out-of-tree ports.
>
> Best regards,
>
> Wolfgang Denk
>
I don't think so. The only changes I made were to the register access
macros to use a couple assembly functions since our EHCI registers
require 64-bit addressing and a very quick virtual to physical
conversion for the descriptors which is quite fast. Other than that, the
code is stock from GIT. Note that we do not use interrupts either but
polling.
Unless I'm reading it wrong it also looks like in EHCI it only uses one
descriptor and I wonder if this might have something to do with it?
I can provide a diff when I return to the office next week.
-Aaron
next prev parent reply other threads:[~2011-01-15 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 3:55 [U-Boot] USB storage performance EHCI question Aaron Williams
2011-01-13 6:09 ` Wolfgang Denk
2011-01-13 11:51 ` Sergei Shtylyov
[not found] ` <4D2FA7F0.7020900@caviumnetworks.com>
[not found] ` <20110114091904.6A250160689@gemini.denx.de>
2011-01-15 4:41 ` Aaron Williams [this message]
2011-01-21 0:05 ` [U-Boot] USB storage performance EHCI question - ext2fs performance Aaron Williams
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=4D312562.1020806@caviumnetworks.com \
--to=aaron.williams@caviumnetworks.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