ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew C. Dingman" <andrew@dingman.org>
To: ath10k@lists.infradead.org
Subject: Re: QCA6164 txbf failure
Date: Mon, 05 Oct 2015 10:46:18 -0400	[thread overview]
Message-ID: <1444056378.9501.17.camel@dingman.org> (raw)
In-Reply-To: <1444055929.9501.14.camel@dingman.org>

On Mon, 2015-10-05 at 10:38 -0400, Andrew C. Dingman wrote:
> It looks like the QCA6164 in my Lenovo Yoga 3 11" has problems with
> txbf. I'm using Fedora with a 4.3.0-rc3 kernel from Koji. (A
> development build system - it's not a released kernel)
> 
> Using firmware from https://github.com/kvalo/ath10k-firmware.git exce
> pt
> for the board.bin, which came https://github.com/atondwal/ath10k-firm
> wa
> re.git. Specifically, to get the card to boot I ran "sudo cp
> ath10k/QCA6164/hw2.1/board.bin
> /lib/firmware/ath10k/QCA6174/hw2.1/board-pci-168c:0041:17aa:3545.bin"
> from the latter git repo.
> 
> Using the unmodified 4.3 kernel above, this allowed the card to be
> recognized, and even report successful authentication and association
> to an access point in dmesg. However, it never completed a
> connection,
> and scanning access points failed.
> 
> Based on the dmesg output, michalk in IRC suggested that I try
> applying
> the patch from http://lists.infradead.org/pipermail/ath10k/2015-Augus
> t/
> 005909.html. With that change, the device seems to work fine.

Adding for completeness:

The device in question, as shown by lspci
    [    andrew@amphitrite     ~]$ sudo lspci -v -n -s 2:0
    02:00.0 0280: 168c:0041 (rev 20)
    	    Subsystem: 17aa:3545
    	    Flags: bus master, fast devsel, latency 0, IRQ 50
    	    Memory at c1000000 (64-bit, non-prefetchable) [size=2M]
    	    Capabilities: [40] Power Management version 3
    	    Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit-
    	    Capabilities: [70] Express Endpoint, MSI 00
    	    Capabilities: [100] Advanced Error Reporting
    	    Capabilities: [148] Virtual Channel
    	    Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-
    00
    	    Capabilities: [178] Latency Tolerance Reporting
    	    Capabilities: [180] L1 PM Substates
    	    Kernel driver in use: ath10k_pci
    	    Kernel modules: ath10k_pci

Also, michalk points out that the log contained "failed to poke peer
XXX param for ps workaround on vdev Y: -11"

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

      reply	other threads:[~2015-10-05 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 14:38 QCA6164 txbf failure Andrew C. Dingman
2015-10-05 14:46 ` Andrew C. Dingman [this message]

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=1444056378.9501.17.camel@dingman.org \
    --to=andrew@dingman.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox