clear-pkgs-linux-iot-lts2018/0040-the-igb_avb-direver-ca...

41 lines
1.3 KiB
Diff
Raw Normal View History

From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
2018-10-11 02:06:46 +08:00
From: "Gross, Mark" <mark.gross@intel.com>
Date: Fri, 14 Sep 2018 13:16:02 -0700
Subject: [PATCH] the igb_avb direver cannot coexist with e1000 or e1000e
drivers.
2018-10-11 02:06:46 +08:00
So I'm making the config protest from enabling igb_avb and e1000 or
e1000e at the same time.
I hope this constraint is not a deal breaker.
Signed-off-by: mark gross<mark.gross@intel.com>
---
drivers/staging/igb_avb/Kconfig | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/igb_avb/Kconfig b/drivers/staging/igb_avb/Kconfig
2020-10-27 02:14:06 +08:00
index e3da46a6f381..2d3780b250c8 100644
2018-10-11 02:06:46 +08:00
--- a/drivers/staging/igb_avb/Kconfig
+++ b/drivers/staging/igb_avb/Kconfig
@@ -1,6 +1,6 @@
config IGB_AVB
tristate "Avnu IGB AVB driver"
- depends on IGB=n
+ depends on IGB=n && E1000=n && E1000E=n
select DCA
default n
---help---
@@ -13,6 +13,5 @@ config IGB_AVB
frame transmission, or test harnesses for measuring system
latencies and sampling events. It is exclusive with the
in-tree IGB driver, so only one of them can be enabled
- at any point in time.
-
- To build this as a module, say M, if not sure say N.
+ at any point in time. There are also coexistance issues with
+ the e1000 and e1000e.
--
https://clearlinux.org
2018-10-11 02:06:46 +08:00