From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>
Subject: IBSS mode is now supported by CT firmware.
Date: Tue, 25 Nov 2014 16:59:00 -0800 [thread overview]
Message-ID: <547525D4.5080701@candelatech.com> (raw)
A company that wishes to remain anonymous is sponsoring my
effort to add IBSS (ADHOC) support to my 10.1.467 CT firmware.
The kernel driver must be patched to enable IBSS mode when
CT firmware is detected.
The firmware was improved by copying some of the missing IBSS
code from the 999.x firmware branch.
I still cannot get WPA2 encryption to work, but open authentication
seems to work fine. I still have a good bit more testing to do.
I cannot get ath9k to do encryption in IBSS mode either, so I
probably am mis-configuring something.
If someone wants to try this out, please download the appropriate
firmware binary from here:
http://www.candelatech.com/downloads/ath10k-fw-beta/
Either hack your own kernel, or grab my latest 3.17 kernel:
git clone git://dmz2.candelatech.com/linux-3.17.dev.y
I'm interested to know results if someone tries it out.
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
next reply other threads:[~2014-11-26 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 0:59 Ben Greear [this message]
2014-11-26 1:21 ` IBSS mode is now supported by CT firmware Yeoh Chun-Yeow
2014-11-26 1:39 ` Ben Greear
2014-11-26 1:48 ` Yeoh Chun-Yeow
2014-11-26 1:50 ` Ben Greear
2014-11-26 2:14 ` Yeoh Chun-Yeow
2014-11-26 1:57 ` Dave Taht
2014-11-26 22:36 ` Pushpal Sidhu
2014-11-27 1:04 ` Yeoh Chun-Yeow
2014-11-28 11:42 ` Yeoh Chun-Yeow
2014-11-28 16:28 ` Ben Greear
2014-11-29 0:25 ` Yeoh Chun-Yeow
2014-12-01 17:38 ` Pushpal Sidhu
2014-12-01 17:57 ` Ben Greear
2014-12-04 15:28 ` Sven Eckelmann
2014-12-01 17:13 ` Pushpal Sidhu
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=547525D4.5080701@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.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.