e8834e95a2
igb: ensure setting MTU sets also max_frame_size
...
This is a regression from the out-of-tree Intel IGB driver happened
between 5.3.5.10 and 5.3.5.18.
The condition here should be actually reveresed, but as we always can
be sure to have a MAX/MIN MTU defined we can just remove it,
essentially going back to the previous code state (which also works
with our current 4.15 kernel).
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com >
2018-06-18 17:07:01 +02:00
515973635b
renenable out-of-tree intel ethernet driver (e1000e, igb, ixgbe)
...
There where just to much issues with the 4.15 in tree drivers for our
users [1]. The updated igb and ixgbe drivers are compatible with
4.15, the e1000e driver needed to be ported to the new internal
kernel timer API, which is pretty straight forward.
[1]: https://forum.proxmox.com/threads/4-15-based-test-kernel-for-pve-5-x-available.42097/page-5
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com >
2018-06-08 11:58:18 +02:00
6eb123031d
revert igb to 5.3.5.10
...
because 5.3.5.12 broke JUMBO_FRAMES (again)
2017-12-05 13:05:16 +01:00
25c35b26a1
update intel drivers to latest upstream releases
2017-11-22 09:47:25 +01:00
a8ee21761c
ixgbe: add 4.13 compat patch
2017-09-26 10:46:35 +02:00
628004c405
igb: add 4.12 compat patch
2017-09-26 10:46:35 +02:00
8021de509c
intel: drop patches which are no longer needed
2017-09-26 10:46:35 +02:00
2f7beffd96
build: move intel NIC patches
2017-09-26 10:46:35 +02:00
Thomas Lamprecht