summaryrefslogtreecommitdiff
path: root/packages/linux-kernel/patches
AgeCommit message (Collapse)Author
2024-08-12Kernel: T5887: update Linux Kernel to v6.6.45mergify/bp/sagitta/pr-733Christian Breunig
(cherry picked from commit faa6453ec86ecebeff2e2a28dd01db2ee655a22c)
2024-07-03Kernel: T5887: update Linux Kernel to v6.6.36Christian Breunig
(cherry picked from commit dd322145bec2902dd4f18064d6c6f18464b987f9)
2024-06-19Kernel: T5887: update Linux Kernel to v6.6.34Christian Breunig
(cherry picked from commit 41771586bd7cef98cd8151e9b36e3d045baa7622)
2024-05-19Kernel: T5887: update Linux Kernel to v6.6.31Christian Breunig
(cherry picked from commit 20b42272c56e5cd006f7f5096fe90520f4b2da00)
2024-05-02Kernel: T5887: update Linux Kernel to v6.6.30Christian Breunig
(cherry picked from commit 5978fd1df855d163436e4e9108a32bc2d1157af4)
2024-04-29ixgbe: T6162: Add 1000BASE-BX supportErnesto Castellotti
The ixgbe driver did not support the 1000BASE-BX standard so for example FS.com SFP-GE-BX 1310/1490nm 10km transceiver received an unsupported module error even with allow_unsupported_sfp enabled. To solve this problem I created a patch that was accepted by Linux upstream (https://github.com/torvalds/linux/commit/1b43e0d20f2d007ec4c124b0deaa848ff8d61f4a) so starting from kernel 6.9 the ixgbe driver will have 1000BASE-BX support, however VyOS uses the out of tree driver so it is necessary to backport the patch. (cherry picked from commit a44647f0982f2a6b7a78af80f82e1c650ab0b11e)
2024-04-03Kernel: T5887: rebase inotify patchChristian Breunig
(cherry picked from commit 28c08a784ebdddfe56d8d33b4f28b147ad0a5265)
2024-03-23ixgbe: T6155: always enable allow_unsupported_sfp even if module_param_array ↵Christian Breunig
is undefined This extends an else path with the logic from commit ea7d59a4b ("ixgbe: T6155: always enable allow_unsupported_sfp for all NICs by default") (cherry picked from commit 70ac747b2889757e35ac2a90fd77cda9d4b97ebd)
2024-03-22ixgbe: T6155: always enable allow_unsupported_sfp for all NICs by defaultChristian Breunig
In-tree vs. Out-Of-Tree drivers differ in the way how unsupported transceivers are defined (uint vs array of int) for the Kernel module parameters. This results in: kernel: ixgbe 0000:5e:00.0: failed to initialize because an unsupported SFP+ module type was detected. kernel: ixgbe 0000:5e:00.0: Reload the driver after installing a supported module. kernel: ixgbe 0000:5e:00.0: removed PHC on eth6 This patch always enables unsupported SFP+ modules as wo do anyway from the userspace but only for the first port. (cherry picked from commit ea7d59a4bf64a854be04ccf7566e1cf95d4e09a8)
2024-03-07Kernel: T5887: forward patch linkstate-ip-device-attribute for 6.6.211.4.0-epa2Christian Breunig
(cherry picked from commit 016809208da4d5500734f275d544463d8122bbd1)
2024-03-01Kernel: T5887: forward patch linkstate-ip-device-attribute for 6.6.19Christian Breunig
(cherry picked from commit d93cb288d7d6bb16afad0df727f012837123a47e)
2024-01-10Kernel: T5887: updae patch for HUNK offsetChristian Breunig
(cherry picked from commit bf211f4558c2799d4258c4225d4d795064a52fd7)
2024-01-05Kernel: T5887: update Linux Kernel to v6.6.9Christian Breunig
(cherry picked from commit cc04a75932345ba37e4e18f82ae3f85330cedf68)
2023-12-22Kernel: T4928: rebase patches ontop of Kernel 6.1.59 to get clean appliesChristian Breunig
(cherry picked from commit e6701712e12189506e49be8c0e25c52a2b1325a1)
2023-04-04accel-ppp: T5138: Use L2TP Calling-Number in RADIUS attributeszsdc
Use L2TP Calling-Number in Calling-Station-ID RADIUS attribute
2023-01-11Kernel: T4928: update Linux Kernel to v6.1.4Christian Breunig
2022-09-13Kernel: T4691: Initial support for 5.15.67Christian Poessinger
2020-12-31Kernel: Initial support for 5.10.4Christian Poessinger
2020-12-19kernel: rename patchesChristian Poessinger
2020-12-14Kernel: T3129: update Linux Kernel to v5.4.83Christian Poessinger
2020-10-17Kernel: T2990: Update Linux Kernel to v4.19.152Christian Poessinger
2020-10-17Kernel: update patches to current versionChristian Poessinger
2020-09-12Revert "Kernel: T2843: upgrade Kernel to v5.8.5"Christian Poessinger
This reverts commit 78c43c2078e292ac9b53d2d6a41a47466d283914. Unfortunately we must revert the Kernel upgrade as there are two problematic issues. One which is the break of ABI functionality with parted [1] and second the internal cryptop API [2] which removed required literals for the build of Intel QAT acceleration. In the two weeks running 5.8 we still learned a lot - we experienced a performance improvement of ~30% when doing NAT @ > 10GBit/s and also utilizing the build in updated drivers for Intel NICs and WireGuard. We are looking forward to the release of this years LTS kernel and we hope to ship this in the final 1.3 release. 1: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.8.y&id=692d062655 2: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.5.y&id=d63007eb95
2020-08-30Kernel: T2843: upgrade Kernel to v5.8.5Christian Poessinger
Note: Intel does not provide a compatible QAT version. There is a custom patch which make QAT compile for the specified Kernel version. This patch will change the source to a non backwards-compatible version - this is fine as we run 5.8 anyways.
2020-08-30Kernel: WireGuard: T2839: update to recent versionsChristian Poessinger
* wireguard user-space tools debian/1.0.20200513-1_bpo10+1 * wireguard-linux-compat kernel modules debian/1.0.20200712-1_bpo10+1
2020-06-24Jenkins: T2625: import Kernel PipelineChristian Poessinger
Imported from https://github.com/vyos/vyos-build-kernel commit 9e7c12b
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-09 20:26:16 +0000