ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Denton Gentry <denton.gentry@gmail.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Malformed AddBA Response prevents clients from associating?
Date: Mon, 25 Aug 2014 09:59:08 +0300	[thread overview]
Message-ID: <87sikl6on7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CABnBrYUv4tLcmOJLUD99B96jWRwepk1_-6NQ1LdEaCaPQ5QOwg@mail.gmail.com> (Denton Gentry's message of "Sun, 24 Aug 2014 19:28:52 -0700")

Denton Gentry <denton.gentry@gmail.com> writes:

> [   18.047597] ath10k: qca988x hw2.0 (0x4100016c, 0x043202ff) fw
> 10.1.467.2-1 api 2 htt 2.1
>
> On Sun, Aug 24, 2014 at 7:22 PM, Adrian Chadd <adrian@freebsd.org> wrote:
>> Which firmware build are you using?

(Standard whining: top posting is annoying.)

Denton, any chance you could test with 10.2 firmware and see if the bug
happens on that firmware as well? I don't know what version of ath10k
you are using, but I think it should be enough to just to have this
patch:

https://github.com/kvalo/ath/commit/24c88f7807fb7c723690474d0a5d3441468185d9

And then take the firmware from here:

https://github.com/kvalo/ath10k-firmware/tree/master/10.2

Do not rename the firmware to firmware-2.bin or anything like that. To
avoid problems keep the name firmware-3.bin.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-08-25  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25  2:17 Malformed AddBA Response prevents clients from associating? Denton Gentry
2014-08-25  2:22 ` Adrian Chadd
2014-08-25  2:28   ` Denton Gentry
2014-08-25  6:59     ` Kalle Valo [this message]
2014-08-26 16:44       ` Denton Gentry
2014-08-26 18:33         ` Kalle Valo

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=87sikl6on7.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=adrian@freebsd.org \
    --cc=ath10k@lists.infradead.org \
    --cc=denton.gentry@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