ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Plata <gregor.plata@t-online.de>
To: ath10k@lists.infradead.org
Subject: Re: QCA6174 hw2.1 firmware, take two?
Date: Sun, 07 Jun 2015 19:08:36 +0200	[thread overview]
Message-ID: <2128694.iEsF7A6qyf@gregors> (raw)
In-Reply-To: <CAMQd7maBxv_AeVZfkdMCri1C0Vq+nU8Jc386FU1LGUrPX0+gpA@mail.gmail.com>

Hi all,

the solution described in the bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184 (comment #150) 
works perfectly for me. Wi-fi is stable without any drops and the 4.1.0-rc6-
wl-ath kernel doesn't cause any  issues but the wi-fi performance comes only 
to about 35%-40% of the performance on windows on the same machine downloading 
the same file from the same server .

best regards
Gregor

Am Donnerstag, 4. Juni 2015, 19:03:55 schrieb Enrico Tagliavini:
> Hi there,
> 
> Just got the following device
> 
> enrico@alientux ~ $ lspci -nn | grep QCA
> 03:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac
> Wireless Network Adapter [168c:003e] (rev 20)
> 
> And discovered there is no firmware available for it. I looked already
> at the April thread about it, but didn't managed to get it working.
> This is on Fedora 22, kernel 4.0.4.
> 
> I used dissect.py from here
> https://gist.github.com/kazikcz/8e5845ad84ca251aa295 to generate the
> firmware image from my Windows installation:
> $ cat
> /windows/Windows/System32/DriverStore/FileRepository/netathrx.inf_amd64_481
> f6e2b133b287d/qca61x420.bin
> | ./dissect.py
> 
> but I have no clue if that is actually the correct file. For sure it's
> the only one containing "qca" end ending in ".bin" alongside
> eeprom_qca9377_1p0_NFA435_olpc.bin which I used as board.bin.
> 
> Unfortunately when trying those I get
> root@alientux ~ # dmesg | grep ath
> [   18.518677] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [   18.519124] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [   18.667191] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [   18.668652] ath10k_pci 0000:03:00.0: invalid firmware magic
> [   18.668791] ath10k_pci 0000:03:00.0: invalid firmware magic
> [   18.670086] ath10k_pci 0000:03:00.0: invalid firmware magic
> [   18.670265] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware.bin failed with error -2
> [   18.670267] ath10k_pci 0000:03:00.0: could not fetch firmware (-2)
> [   18.670269] ath10k_pci 0000:03:00.0: could not fetch firmware files (-2)
> [   18.670271] ath10k_pci 0000:03:00.0: could not probe fw (-2)
> 
> No idea where to go from here. I'm currently not sure if I want to try
> kvalo sources. Don't get me wrong but if I have to apply a patch to
> the official Linux source tree that's ok, but switching to the
> development tree is not what I was looking forward for this machine.
> Can 4.1 help instead? I'm afraid it might now since I can see the fix
> for the firmware crash is still not included.
> 
> Thank you for the help.
> Best regards.
> 
> Enrico
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k


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

  parent reply	other threads:[~2015-06-07 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 17:03 QCA6174 hw2.1 firmware, take two? Enrico Tagliavini
2015-06-04 17:13 ` Adrian Chadd
2015-06-04 17:22 ` Enrico Tagliavini
2015-06-04 21:12   ` Jason H
     [not found]     ` <CAAiUAtu2ESMaMZ0-qVm6bS2Syy4sf1A8TSRGh7SWMaMM51KZ3A@mail.gmail.com>
2015-06-06 11:47       ` Enrico Tagliavini
2015-06-07 17:08 ` Gregor Plata [this message]
2015-06-09  9:23   ` Enrico Tagliavini

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=2128694.iEsF7A6qyf@gregors \
    --to=gregor.plata@t-online.de \
    --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