From: Simon Wunderlich <sw@simonwunderlich.de>
To: "Pedersen, Thomas" <twp@qca.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"openwrt-devel@lists.openwrt.org"
<openwrt-devel@lists.openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath10k mesh + ap + encryption?
Date: Sun, 25 Sep 2016 22:16:43 +0200 [thread overview]
Message-ID: <3338244.IC8yTOzn2x@prime> (raw)
In-Reply-To: <1474669037.16013.9.camel@qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
On Friday, September 23, 2016 10:18:49 PM CEST Pedersen, Thomas wrote:
> On Mon, 2016-09-19 at 08:43 +0200, Simon Wunderlich wrote:
>
> > On Tuesday, September 13, 2016 5:54:38 PM CEST Pedersen, Thomas wrote:
> >
> > > On Tue, 2016-09-13 at 14:30 +0200, Simon Wunderlich wrote:
> > >
> > >
> > > > [...]
> > > >
> > > >
> > > >
> > > > Thanks for the clarification. We will then stick to the 70's branch
> > > > then.
> > > >
> > > > Does anyone have pointers for the other questions? :) I would believe
> > > > hat many
> > > > people would be interested in running AP + Mesh encrypted at the same
> > > > time (at
> > > > least in the open source community ...).
> > >
> > >
> > >
> > > We're testing encrypted AP + Mesh quite successfully right now with
> > > this firmware: https://github.com/kvalo/ath10k-firmware/commit/307cb46b
> > > 06661ebd3186723b5002de769c7add83, of course that is for a QCA4019 chip.
> > > Which chip are you using? I can poke the firmware guys for possibility
> > > of getting a 10.4.3.2 firmware build for it.
> >
> >
> > Hi Thomas,
> >
> > thanks for the hint! We are using an older QCA9882. I assume your firmware
> > will
not work for this one? If you can poke the firmware guys, that
> > would be great.>
> > :)
>
>
> Hi Simon,
>
> According to firmware guys the latest code can actually compile down to
> any chipset, so it should simply be a matter of getting builds released.
Hi Thomas,
thats great news, thanks for the heads up!
How are we going to get those builds released? Who can I ask, or do you want
to take care of that?
Thanks,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-25 20:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 8:00 ath10k mesh + ap + encryption? Simon Wunderlich
2016-09-13 10:59 ` Valo, Kalle
2016-09-13 11:13 ` Simon Wunderlich
2016-09-13 11:25 ` Valo, Kalle
2016-09-13 11:38 ` Sebastian Gottschall
2016-09-13 12:30 ` Simon Wunderlich
2016-09-13 17:54 ` Pedersen, Thomas
2016-09-19 6:43 ` Simon Wunderlich
2016-09-19 9:34 ` [OpenWrt-Devel] " Sven Eckelmann
2017-01-24 16:41 ` Sven Eckelmann
2016-09-23 22:18 ` Pedersen, Thomas
2016-09-25 20:16 ` Simon Wunderlich [this message]
2016-09-13 18:54 ` Martin Blumenstingl
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=3338244.IC8yTOzn2x@prime \
--to=sw@simonwunderlich.de \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=openwrt-devel@lists.openwrt.org \
--cc=twp@qca.qualcomm.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).