From: Martin Fuzzey <mfuzzey@parkeon.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Firmware problems with Lesswire Wibear 11n module using mwifiex
Date: Tue, 16 Apr 2013 10:19:11 +0200 [thread overview]
Message-ID: <516D097F.7030905@parkeon.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430D9DF761EC@SC-VEXCH1.marvell.com>
Hi Bing,
On 16/04/13 01:41, Bing Zhao wrote:
> That's right. The host controller and/or its driver need to be
> checked. Thanks, Bing
Ok I've fixed my host controller driver and it works now.
Patch submitted: [http://article.gmane.org/gmane.linux.kernel.mmc/20121]
Thank you for pointing me in the right direction.
Regards,
Martin
prev parent reply other threads:[~2013-04-16 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 16:21 Firmware problems with Lesswire Wibear 11n module using mwifiex Martin Fuzzey
2013-03-29 21:32 ` Bing Zhao
2013-04-15 12:55 ` Martin Fuzzey
2013-04-15 23:41 ` Bing Zhao
2013-04-16 8:19 ` Martin Fuzzey [this message]
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=516D097F.7030905@parkeon.com \
--to=mfuzzey@parkeon.com \
--cc=bzhao@marvell.com \
--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).