From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: New ath10k CT firmware released.
Date: Mon, 10 Nov 2014 14:53:22 -0800 [thread overview]
Message-ID: <546141E2.2080309@candelatech.com> (raw)
In-Reply-To: <545C16A5.9030106@candelatech.com>
On 11/06/2014 04:47 PM, Ben Greear wrote:
> On 11/06/2014 11:57 AM, Ben Greear wrote:
>> I have uploaded the latest CT version of the ath10k firmware.
>>
>> http://www.candelatech.com/ath10k.php
>>
>> This firmware fixes bugs in raw-tx mode, though probably only
>> non-encrypted frames can be sent in this manner, and it requires
>> an out-of-tree patch from Michal Kazior to make it work:
>>
>> http://comments.gmane.org/gmane.linux.drivers.ath10k.devel/246
>>
>> This firmware also significantly improves association times when using
>> more than one vdev. This, requires an additional kernel patch:
>>
>> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=commitdiff;h=a9756b6e2efffbec4101dbe81e9d6a2c503239ff;hp=5bfa637376c352fc17c56afc7b1d2e752750162c
>
> I was a bit too clever it seems.... I have to be more careful about disabling
> the ch reservation when there are no vdevs active, I think.
>
> Hope to have it fixed shortly.
Looks like firmware was fine, so it remains unchanged. But, the driver patch has to
be more careful and only disable ch reservation if we currently have an active channel.
This patch (on top of the one linked above) seems to work well:
http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.17.dev.y/.git;a=commitdiff;h=5ed93f05d72769b06246280d514b72d617bb9fde
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2014-11-10 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 19:57 New ath10k CT firmware released Ben Greear
2014-11-07 0:47 ` Ben Greear
2014-11-10 22:53 ` Ben Greear [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=546141E2.2080309@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@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).