mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-18 03:04:45 +08:00
da416b04f7dea86e322f340d468e6f32b84c858c
Add latest verified version of Mellanox Spectrum-family switch firmware, for Spectrum (13.2008.2946), Spectrum-2 (29.2008.2946) and Spectrum-3 (30.2008.2946). The following issues have been fixed: - A Spectrum-2 issue where control traffic generated on the switch would not egress a front panel port. - Minimum shaper would not guarantee the requested bandwidth if the configured rate is 100Gbps+. - On Spectrum-1, when bulk-updating FDB, a multicast tunnel entry update would be corrupted, and a unicast entry would not change VID. - When ECMP or LAG are in symmetric hash mode, a packet would be steered to the wrong port. - Obtaining activity for MC routes would sometimes exhibit a latency of >1us on Spectrum-3. The following new features are available: - Elephant & mice flow detection - Register PMTDB, for querying of possible split-port scenarios - Router interface profiles, which relax the requirement that all router interfaces have the same MAC address prefix. Signed-off-by: Petr Machata <petrm@nvidia.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
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.
If your commit adds new firmware, it must update the WHENCE file to
clearly state 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 ('See LICENSE.foo for details.').
And if it were possible, a changelog of the firmware itself.
Run 'make check' to check that WHENCE is consistent with the
repository contents.
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.
Description
Languages
TL-Verilog
67.4%
C
23.8%
Assembly
5.4%
CMake
1.2%
Python
0.9%
Other
1.3%