mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2026-02-02 10:02:23 +08:00
bf8e868d1e
7265D device is really much like 7265 but with more embedded memory which allows to have more firmware features. 7265D device can use 7265.ucode but then won't get the features that could fit into the 'D' version of the frimware. When iwlwifi-7265D-10.ucode was released, there were no such features and from a functional point of view, iwlwifi-7265D-10.ucode is really the same as iwlwifi-7265-10.ucode. Moreover, a user reported that iwlwifi-7265D-10.ucode is causing issues on his device while iwlwifi-7265-10.ucode works perfectly. Remove iwlwifi-7265D-10.ucode and make a soft link to iwlwifi-7265-10.ucode. Fixes https://bugzilla.kernel.org/show_bug.cgi?id=109531. Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Linux firmware
==============
<http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
This repository contains all these firmware images which have been
extracted from older drivers, as well various new firmware images which
we were never permitted to include in a GPL'd work, but which we _have_
been permitted to redistribute under separate cover.
To submit firmware to this repository, please send either a git binary
diff or preferably a git pull request to:
linux-firmware@kernel.org
and also cc: to related mailing lists.
Your commit should include an update to the WHENCE file clearly
identifying the license under which the firmware is available, and
that it is redistributable. Being redistributable includes ensuring
the firmware license provided includes an implicit or explicit
patent grant to end users to ensure full functionality of device
operation with the firmware. If the license is long and involved, it's
permitted to include it in a separate file and refer to it from the
WHENCE file.
And if it were possible, a changelog of the firmware itself.
Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code).
WARNING:
=======
Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
request. Otherwise your firmware _will never be accepted_.
Maintainers are really busy, so don't expect a prompt reply.