linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Xuebing Wang <xbing6@gmail.com>
Cc: Sven Eckelmann <sven@narfation.org>,
	b.a.t.m.a.n@lists.open-mesh.org, linux-wireless@vger.kernel.org,
	OpenWrt Development List <openwrt-devel@lists.openwrt.org>
Subject: Re: [B.A.T.M.A.N.] [batman-adv] Does batman-adv works perfectly?
Date: Tue, 18 Apr 2017 12:40:16 +0200	[thread overview]
Message-ID: <3124220.7tTabXjFJx@prime> (raw)
In-Reply-To: <CAG5qQ7hQACaP=vz6jmvWDXoK=Sn0wpE3DrDhJv8Qajnhjbp+Og@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

Hi Xuebing,

I didn't try the QSDK on those devices, mainly because of its poor upstream 
support/community involvement. We tried it on other devices, with "mixed" 
results.

Cheers,
      Simon

On Monday, April 17, 2017 10:19:02 PM CEST Xuebing Wang wrote:
> Hi Sven and Simon,
> 
> Thank you very much for your help. I am curious that did you try QCA-WiFi
> driver for ath9k device (like AR9331) + OpenWRT, instead of trying to
> improve ath9k driver?
> 
> QCA-WiFi driver included in QSDK:
> https://www.codeaurora.org/projects/all-active-projects/qsdk
> 
> Thanks.
> Xuebing Wang
> 
> On Thu, Apr 6, 2017 at 3:13 PM, Sven Eckelmann <sven@narfation.org> wrote:
> > On Donnerstag, 6. April 2017 09:04:50 CEST Simon Wunderlich wrote:
> > > Hello Xuebing,
> > > 
> > > it sounds like you have WiFi driver issues. There are some effects like
> > 
> > key
> > 
> > > cache corruption, deafness, and other effects known for the AR93xx
> > 
> > series.
> > 
> > Correct, completely forgot about the deaf and 0xdeadbeef issues. There
> > were
> > also two workarounds for them [1,2] from Simon.
> > 
> > Kind regards,
> > 
> >         Sven
> > 
> > [1] https://patchwork.kernel.org/patch/9433619/
> > [2] https://patchwork.kernel.org/patch/9433621/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

           reply	other threads:[~2017-04-18 10:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAG5qQ7hQACaP=vz6jmvWDXoK=Sn0wpE3DrDhJv8Qajnhjbp+Og@mail.gmail.com>]

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=3124220.7tTabXjFJx@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=sven@narfation.org \
    --cc=xbing6@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).