From: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
To: Brad Pousland <bpousland@izuma.net>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Compex QCA9880 Aarch64 ath10k firmware?
Date: Wed, 18 May 2016 18:37:56 +0530 [thread overview]
Message-ID: <20160518130756.GA2065@atheros-ThinkPad-T61> (raw)
In-Reply-To: <CAGBdaZnYrA_wFVAnD1fsp9Wu2xbcbhhrJaSedGc8rRThnep5Bg@mail.gmail.com>
Hi,
On Wed, May 18, 2016 at 08:01:30AM -0500, Brad Pousland wrote:
> Is anyone aware of the ath10k driver working with arm64 backported to
> 3.19? I'm running into a firmware crash.
>
> [ 194.460687] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [ 194.638979] ath10k_pci 0000:01:00.0: Direct firmware load for
> ath10k/cal-pci-0000:01:00.0.bin failed with error -2
> [ 195.788482] ath10k_pci 0000:01:00.0: received unsolicited fw crash interrupt
> [ 195.794237] ath10k_pci 0000:01:00.0: received unsolicited fw crash interrupt
[shafi] Are you using the latest backports, you can try to create your owna
http://linuxwireless.org/en/users/Drivers/ath10k/backports/
> [ 196.793965] ath10k_pci 0000:01:00.0: failed to receive control
> response completion, polling..
> [ 196.801242] ath10k_pci 0000:01:00.0: received unsolicited fw crash interrupt
> [ 196.806991] ath10k_pci 0000:01:00.0: received unsolicited fw crash interrupt
> [ 197.793962] ath10k_pci 0000:01:00.0: Service connect timeout
> [ 197.798308] ath10k_pci 0000:01:00.0: failed to connect htt (-110)
> [ 197.874806] ath10k_pci 0000:01:00.0: could not init core (-110)
> [ 197.879434] ath10k_pci 0000:01:00.0: could not probe fw (-110)
https://github.com/kvalo/ath10k-firmware
please check you have the latest firmware as well
>
> Brad
>
>
> Brad Pousland
> Principle Software Engineer
> WigWag, Inc.
> c - 512-963-2446
> www.wigwag.com
>
>
>
> On Wed, May 18, 2016 at 12:02 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
> > On 18 May 2016 at 01:11, Brad Pousland <bpousland@izuma.net> wrote:
> >> Hello,
> >>
> >> I'm cross compiling backports-4.2.6-1 to Aarch64 for Linux 3.19.3+ and
> >> running the ath10k drivers against the Compex QCA9880 module. I get
> >> some firmware load errors.
> >>
> >> [ 47.824874] Loading modules backported from Linux version v4.2.6-0-g1c02865
> >> [ 47.830525] Backport generated by backports.git v4.2.6-1-0-g90118c7
> >> [ 209.931062] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 8
> >> irq_mode 0 reset_mode 0
> >> [ 210.106576] ath10k_pci 0000:01:00.0: Direct firmware load for
> >> ath10k/cal-pci-0000:01:00.0.bin failed with error -2
> >> [ 210.115638] ath10k_pci 0000:01:00.0: Direct firmware load for
> >> ath10k/QCA988X/hw2.0/board.bin failed with error -2
> >> [ 210.124598] ath10k_pci 0000:01:00.0: failed to fetch generic board data: -2
> >> [ 210.130245] ath10k_pci 0000:01:00.0: failed to fetch board file: -2
> >> [ 210.135211] ath10k_pci 0000:01:00.0: could not fetch firmware files (-2)
> >> [ 210.140598] ath10k_pci 0000:01:00.0: could not probe fw (-2)
> >>
> >> Firmware is:
> >> firmware-2.bin_10.1.467.3-1
> >> firmware-5.bin_10.2.4.70.42-2
> >> firmware-3.bin_10.2.2.39.6-1
> >>
> >> Why does it appear to be looking for board.bin? I understood that was
> >> removed from the latest ath10k driver?
> >
> > You're probably referring to the removal of FW API 1. This didn't
> > concern board files. You still need board.bin or board-2.bin.
> >
> >
> > Michał
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2016-05-18 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 23:11 Compex QCA9880 Aarch64 ath10k firmware? Brad Pousland
2016-05-18 5:02 ` Michal Kazior
2016-05-18 13:01 ` Brad Pousland
2016-05-18 13:07 ` Mohammed Shafi Shajakhan [this message]
2016-05-18 13:11 ` Manoharan, Rajkumar
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=20160518130756.GA2065@atheros-ThinkPad-T61 \
--to=mohammed@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=bpousland@izuma.net \
/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