From: James Cameron <quozl@laptop.org>
To: Andrew Wiley <wiley.andrew.j@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Fwd: mwifiex and SD8787: How to create AP interface?
Date: Mon, 3 Feb 2014 08:51:41 +1100 [thread overview]
Message-ID: <20140202215141.GL30112@us.netrek.org> (raw)
In-Reply-To: <CAAUTuq-O1BFBmJfYe2xuRfLmNDNKY=V9CkMCM-QCq1iujE3n2w@mail.gmail.com>
On Sat, Feb 01, 2014 at 11:01:02PM -0600, Andrew Wiley wrote:
> Hello Avinash,
>
> Thanks! That works for me. Would it be possible to add this to the
> mwifiex page on wireless.kernel.org? As far as I know, this command is
> completely undocumented within iw, and I know I'm not the only
> Dreamplug owner experiencing this problem.
>
> As for other issues, I'm seeing a hang in the TX queue on the device
> after running an AP for a while, but I'm still gathering information
> on that. I'll follow up with another thread.
I've also seen hangs, in both RX and TX, but mostly RX.
The response to failing to alloc an skb is a bit weak in mwifiex, we
noted this on OLPC XO-4 with the 8787. You can see more about the
problem and some local fixes in our private branch:
http://dev.laptop.org/git/olpc-kernel/log/?h=arm-3.5
http://dev.laptop.org/ticket/12694 (kernel 3.5)
I did backport the latest mwifiex at the time, but it did not fix the
issue, so I dug into it more.
--
James Cameron
http://quozl.linux.org.au/
next prev parent reply other threads:[~2014-02-02 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 2:56 mwifiex and SD8787: How to create AP interface? Andrew Wiley
[not found] ` <CAJwzM1=0xBkQ0cw-T+zMcAHSZVJsJ7vJmK6O9eisqttn_qGyMA@mail.gmail.com>
[not found] ` <CAAUTuq--5EUYgKb1Bg9UWZnDAZRqcPZFd=GRVEo-YKictJJWwg@mail.gmail.com>
2014-02-02 5:01 ` Fwd: " Andrew Wiley
2014-02-02 5:19 ` Avinash Patil
2014-02-02 21:51 ` James Cameron [this message]
2014-02-03 22:09 ` Fwd: " Andrew Wiley
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=20140202215141.GL30112@us.netrek.org \
--to=quozl@laptop.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wiley.andrew.j@gmail.com \
/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).