From: Takashi Iwai <tiwai@suse.de>
To: Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: MODULE_FIRMWARE() for fallback ucode files?
Date: Mon, 06 Feb 2017 17:12:59 +0100 [thread overview]
Message-ID: <s5hvasn47sk.wl-tiwai@suse.de> (raw)
Hi,
currently iwlwifi driver lists only the latest firmware files in
MODULE_FIRMWARE() although the driver may read other older files.
And this confuses the openSUSE installer, since the installation image
is created based on the module information and copies only the
firmwares listed there. A bug report is found at:
https://bugzilla.suse.com/show_bug.cgi?id=1021082
Would it be better to list up all firmware files? Or how can we
inform user-space which firmware files would be possibly loaded?
In anyway, the current situation is messy. The driver declares the
firmware files that don't exist in the common linux-firmware git
tree. If we list up only the latest API version, we should guarantee
that these files are landed in the official tree before upstreaming.
thanks,
Takashi
reply other threads:[~2017-02-06 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=s5hvasn47sk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luciano.coelho@intel.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