All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] QCA9558 problems for MCS 14/15
Date: Sat, 30 Nov 2013 17:22:17 +0100	[thread overview]
Message-ID: <201311301722.17991.sw@simonwunderlich.de> (raw)
In-Reply-To: <CAJ-Vmonc=qGKBxgowB0Y0r4r0VCSMsDZZf=_xTkj=LQbXciSKg@mail.gmail.com>

Hey Adrian,

> On 29 November 2013 09:59, Simon Wunderlich <sw@simonwunderlich.de> wrote:
> > Anyone any other ideas? :)
> > 
> > Today we've tried another round of the latest OpenWRT + pending patches
> > from the ath9k mailing list, but still no change. We'd appreciate your
> > ideas a lot.
> > 
> > :)
> 
> 9.5.3.15 works fine, right? Do you have the source for it?

Yes, it works fine, or at least much better than ath9k in its current state. We 
don't have the source for Atheros drivers, it was part of the original firmware 
which was installed on these devices. We have asked if the vendor modified 
anything to "tune" for these particular devices, and that would be: disabled 
RTS/CTS, increased beacon interval, disabled beamforming. This didn't give us 
any clue why we have problems in ath9k, though ....
> 
> I'll go hit up QCA people (under NDA, of course! :) to see if I can
> get this particular LSDK version and see what particular hacks are in
> for this driver version.

Thanks a lot for your help! :D

Cheers,
    Simon

  reply	other threads:[~2013-11-30 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 15:57 [ath9k-devel] QCA9558 problems for MCS 14/15 Simon Wunderlich
2013-11-23  9:37 ` Thomas Hühn
2013-11-25 15:10   ` Sven Eckelmann
2013-11-29 17:59     ` Simon Wunderlich
2013-11-30  0:51       ` Adrian Chadd
2013-11-30 16:22         ` Simon Wunderlich [this message]
2013-11-30 19:27           ` Adrian Chadd
2013-12-02 11:45             ` Simon Wunderlich

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=201311301722.17991.sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --cc=ath9k-devel@lists.ath9k.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.