From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: New ath10k CT firmware released.
Date: Thu, 06 Nov 2014 11:57:11 -0800 [thread overview]
Message-ID: <545BD297.5040806@candelatech.com> (raw)
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
And, you may want the near-by patches that allow disabling some
logging, especially if using serial console.
There is also a small fix to max-nss logic in the firmware rate-control,
but I am not sure this is required. It _is_ required that you use
currently-out-of-tree patches if you want anything other than 3x3 station
connecting to 3x3 AP to work properly with ath10k.
As always, I am interested to know how people are using
the CT firmware, and I would welcome any help with getting
even basic support (such as reserved feature flags)
for this firmware in the upstream kernel.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: New ath10k CT firmware released.
Date: Thu, 06 Nov 2014 11:57:11 -0800 [thread overview]
Message-ID: <545BD297.5040806@candelatech.com> (raw)
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
And, you may want the near-by patches that allow disabling some
logging, especially if using serial console.
There is also a small fix to max-nss logic in the firmware rate-control,
but I am not sure this is required. It _is_ required that you use
currently-out-of-tree patches if you want anything other than 3x3 station
connecting to 3x3 AP to work properly with ath10k.
As always, I am interested to know how people are using
the CT firmware, and I would welcome any help with getting
even basic support (such as reserved feature flags)
for this firmware in the upstream kernel.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2014-11-06 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 19:57 Ben Greear [this message]
2014-11-06 19:57 ` New ath10k CT firmware released Ben Greear
2014-11-07 0:47 ` Ben Greear
2014-11-07 0:47 ` Ben Greear
2014-11-10 22:53 ` Ben Greear
2014-11-10 22:53 ` Ben Greear
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=545BD297.5040806@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.