linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org,
	ath10k@lists.infradead.org
Subject: Re: [RFC] ath10k: silence firmware file probing warnings
Date: Thu, 21 Jul 2016 09:09:39 +0200	[thread overview]
Message-ID: <20160721070938.GA2658@redhat.com> (raw)
In-Reply-To: <1468933237-5226-1-git-send-email-michal.kazior@tieto.com>

On Tue, Jul 19, 2016 at 03:00:37PM +0200, Michal Kazior wrote:
> Firmware files are versioned to prevent older
> driver instances to load unsupported firmware
> blobs. This is reflected with a fallback logic
> which attempts to load several firmware files.
> 
> This however produced a lot of unnecessary
> warnings sometimes confusing users and leading
> them to rename firmware files making things even
> more confusing.

This happens on kernels configured with
CONFIG_FW_LOADER_USER_HELPER_FALLBACK and cause not only ugly warnings,
but also 60 seconds delay before loading next firmware version.
For some reason RHEL kernel needs above config option, so this
patch is very welcome from my perspective.

Stanislaw

  reply	other threads:[~2016-07-21  7:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 13:00 [RFC] ath10k: silence firmware file probing warnings Michal Kazior
2016-07-21  7:09 ` Stanislaw Gruszka [this message]
2016-07-21  7:36   ` Emmanuel Grumbach
2016-07-21  8:05     ` Stanislaw Gruszka
2016-07-21 10:23       ` Prarit Bhargava
2016-07-21 11:51         ` Stanislaw Gruszka
2016-07-21 12:01           ` Prarit Bhargava
2016-07-22  8:38           ` Arend Van Spriel
2016-07-22 10:26             ` Stanislaw Gruszka
2016-07-22 12:21               ` Arend Van Spriel
2016-07-22 12:51                 ` Prarit Bhargava
2016-07-22 22:19                   ` Luis R. Rodriguez
2016-07-25  7:51                     ` Emmanuel Grumbach
2016-07-22 22:15               ` Luis R. Rodriguez
2016-07-28 19:23                 ` Arend van Spriel
2016-08-02 11:10                 ` Valo, Kalle
2016-08-02 14:16                   ` Luis R. Rodriguez
2016-08-03 11:33                     ` Arend van Spriel
2016-08-03 14:21                       ` Luis R. Rodriguez
2016-08-03 15:04                         ` Valo, Kalle
2016-08-03 17:10                           ` Luis R. Rodriguez
2016-08-03 19:19                             ` Arend van Spriel
2016-07-22 22:05             ` Luis R. Rodriguez
2016-07-28 19:23               ` Arend van Spriel
2016-07-28 23:28                 ` Luis R. Rodriguez
2016-08-02 11:18 ` Valo, Kalle
2016-08-02 11:24   ` Felix Fietkau
2017-01-20 12:51 ` Kalle Valo
2017-01-20 12:56   ` Michal Kazior
2017-01-31 15:02 ` Kalle Valo

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=20160721070938.GA2658@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).