From: Andreas Kemnade <andreas@kemnade.info>
To: hong zhang <henryzhang62@yahoo.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, dsd@laptop.org,
libertas-dev@lists.infradead.org
Subject: Re: poor performance with W2CBW003 (Marvell 8686)
Date: Thu, 14 Jun 2012 07:45:45 +0200 [thread overview]
Message-ID: <20120614074545.105a459d@kemnade.info> (raw)
In-Reply-To: <1339612748.69001.YahooMailClassic@web161703.mail.bf1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Hi,
On Wed, 13 Jun 2012 11:39:08 -0700 (PDT)
hong zhang <henryzhang62@yahoo.com> wrote:
> You have to identify problem caused by
> SDIO host controller or wifi driver.
>
> If driver is working well in x86 with Roch SDIO, that means wifi driver is ok.
>
> You have to find out
> 1. SDIO interface if using Interrupt or PIO
Hmm, very interesting point, of course, there are interrupts. But after reading
the commit logs in the patched 2.6.32 kernel I see there is a patch enabling
asynchronous *sdio* interrupts. That looks clearly suspicious.
> 2. 1 bit or 4 bit
Hmm, 4bit.
Greetings
Andreas Kemnade
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-06-14 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 13:03 poor performance with W2CBW003 (Marvell 8686) Andreas Kemnade
2012-06-12 19:18 ` Dan Williams
2012-06-12 22:16 ` Andreas Kemnade
2012-06-13 17:06 ` hong zhang
2012-06-13 17:42 ` Andreas Kemnade
2012-06-13 18:39 ` hong zhang
2012-06-14 5:45 ` Andreas Kemnade [this message]
2012-06-14 16:11 ` hong zhang
2012-06-14 16:30 ` hong zhang
2012-06-15 6:18 ` Andreas Kemnade
2012-06-15 14:56 ` hong zhang
2012-06-15 16:48 ` Dan Williams
2012-10-29 17:10 ` Martin Chaplet
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=20120614074545.105a459d@kemnade.info \
--to=andreas@kemnade.info \
--cc=dcbw@redhat.com \
--cc=dsd@laptop.org \
--cc=henryzhang62@yahoo.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).