ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
Date: Thu, 05 Jan 2017 15:31:31 +0100	[thread overview]
Message-ID: <1483626691.8560.90.camel@free.fr> (raw)
In-Reply-To: <CA+BoTQkN9mxw5SwMc-c53_P=ZnL8tY4RmfrqGC=QpJ2-ukGCAg@mail.gmail.com>

Le jeudi 05 janvier 2017 à 14:51 +0100, Michal Kazior a écrit :
> > On 5 January 2017 at 14:28, Xavier Bestel <xavier.bestel@free.fr> wrote:
> > I have an XPS 13 9360 with a stock Killer 1535, and I suffer random
> > freeze when enabling on-board WiFi. I'm not yet sure if it's due to
> > i915 or ath10k.
> 
> Does it freeze the entire system? Try making sure ath10k_pci is loaded
> with reset_mode, e.g. via /etc/modprobe.d/ with:
> 
>  options ath10k_pci reset_mode=1

What's that "reset_mode" ? Where can I find doc about the various
options ?

[...]
> > So why does it try to load a firmware if it's not useful ?
> 
> Driver tries to load latest-to-oldest version blobs (for backward
> compatibility) and uses whatever it finds first. Due to deficient
> firmware API in kernel you see these "error" messages. There's been
> some work going on but it's progressing slowly.

OK I understand. A little message telling the user that such failures
are harmless would be nice though.

	Xav

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

  reply	other threads:[~2017-01-05 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 13:28 Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Xavier Bestel
2017-01-05 13:51 ` Michal Kazior
2017-01-05 14:31   ` Xavier Bestel [this message]
2017-01-06 14:25     ` Xavier Bestel
2017-01-09 14:43       ` Michal Kazior
2017-01-10  8:55         ` Xavier Bestel

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=1483626691.8560.90.camel@free.fr \
    --to=xavier.bestel@free.fr \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.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