From: Oscar Rydberg <oscarrydberg@gmail.com>
To: ath10k@lists.infradead.org
Subject: Re: First QCA6174 firmware release
Date: Sat, 25 Apr 2015 18:22:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20150425T202151-34@post.gmane.org> (raw)
In-Reply-To: 54DB5CD8.80302@dreyero.de
Olaf Dreyer <olaf <at> dreyero.de> writes:
>
> I have a new Acer Aspire VN7-591 Laptop with a Qualcom Atheros
QCNF344
> wireless chip, which is shown by lspci as:
>
> Qualcomm Atheros Device 003e (rev 20)
> Subsystem: Foxconn International, Inc. Device e08e
>
> I have installed the linux-next kernel from today 8:00 UTC.
> I was able to load the ath10k_pci driver, but the driver complains
about
> missing firmware.
> I installed a firmware from here: https://github.com/kvalo/ath10k-
firmware
> under /lib/firmware/ath10k/QCA6174/hw2.1/
> But also the card is not working.
>
> The output from dmesg is:
> [ 9360.538767] ath10k_pci 0000:07:00.0: pci irq msi interrupts 1
> irq_mode 0 reset_mode 0
> [ 9360.788588] ath10k_pci 0000:07:00.0: Direct firmware load for
> ath10k/cal-pci-0000:07:00.0.bin failed with error -2
> [ 9362.729118] ath10k_pci 0000:07:00.0: unable to write to the
device
> [ 9362.729120] ath10k_pci 0000:07:00.0: failed to download normal
> firmware: -110
> [ 9362.729121] ath10k_pci 0000:07:00.0: could not init core (-110)
> [ 9362.729156] ath10k_pci 0000:07:00.0: could not probe fw (-110)
>
> I would like to know, as Austin Hendrix wrote it at 8 Feb 14:12
2015
> too, where can I find the firmware on the
> internet / my Windows7 partition and how can I prepare the needed
files.
>
> Many thanks,
>
> Olaf
>
Hi did you advance anything on this?
Trying to run a QCA6164 card myself on a Lenovo 3-14 laptop.
Sems I've gotten as far as you.
Prepared Ath10k hw2.1 board.bin and firmware-4.bin for hw2.1 using
windows binary driver. (And assemble.py, disassemble.py tools linked
elsewhere)
Board.bin seems to load and execute fine. But after that when
loading firmware-4.bin, it ends up with Unable to write to the
device.
I see it starts sending firmware-4.bin and first 256 bytes ce_send
fine.
2nd ce_send 256 bytes seem to also ce_send fine, however after that
bmi_wait times out. (-110)
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-04-25 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 13:44 First QCA6174 firmware release Olaf Dreyer
2015-04-25 18:22 ` Oscar Rydberg [this message]
2015-04-27 5:34 ` Michal Kazior
-- strict thread matches above, loose matches on Subject: below --
2015-02-08 13:12 Austin Hendrix
2015-02-08 13:17 ` Sebastian Gottschall
2015-02-12 6:04 ` Austin Hendrix
2015-02-12 6:31 ` Michal Kazior
2015-02-13 7:25 ` Austin Hendrix
2015-02-09 10:14 ` Austin Hendrix
2015-01-27 13:45 Kalle Valo
2015-02-03 17:04 ` Joris Guisson
[not found] ` <CAAmLN2Y8L_BZbZBCvUEw_i9OJoWvzaUT6H5UsyBymaozLubcOA@mail.gmail.com>
2015-02-04 12:08 ` Kalle Valo
2015-02-04 18:13 ` Joris Guisson
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=loom.20150425T202151-34@post.gmane.org \
--to=oscarrydberg@gmail.com \
--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 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.