On 24/08/17 01:08, Wold, Saul wrote:
On Tue, 2017-08-22 at 15:39 +0300, Mikko Ylinen wrote:
Hi,
On 21/08/17 09:26, Syed Mohamad Fauzi, Syed Johan Arif wrote:
removing in-tree ixgbe and ixgbevf kernel modules to enable out-of-
tree ixgbe and ixgbevf modules from linux-intel
Signed-off-by: Syed Mohamad Fauzi, Syed Johan Arif <syed.johan.arif
[email protected]>
---
common/recipes-kernel/linux/linux-intel.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/recipes-kernel/linux/linux-intel.inc
b/common/recipes-kernel/linux/linux-intel.inc
index 20f01f0..3b0c576 100644
--- a/common/recipes-kernel/linux/linux-intel.inc
+++ b/common/recipes-kernel/linux/linux-intel.inc
@@ -38,6 +38,8 @@ do_compile_kernelmodules_append() {
rm -rf ${B}/drivers/net/wireless/intel/iwlwifi
rm -rf ${B}/net/mac80211
rm -rf ${B}/net/wireless
+ rm -rf ${B}/drivers/net/ethernet/intel/ixgbe
+ rm -rf ${B}/drivers/net/ethernet/intel/ixgbevf
}
RDEPENDS_kernel-modules += "iwlwifi"
This does not look right (the same for iwlwifi). Why not to disable
the config fragments if the modules are not wanted?
Mikko,
Since we are using the same base yocto-kernel-cache data for both the
linux-intel and linux-yocto kernel, the value add by the linux-intel
kernel is that it uses the out of tree modules (newer, shiner, better),
while the linux-yocto kernel still needs to have the iwlwifi and ixgbe
drivers there, since it does not DEPEND on the iwlwifi OOT modules.
So removal is easiest.
What's easiest usually means you'll run into trouble sooner or later.
In this case it's rather 'soon' because what backport-iwlwifi does is
it also builds and installs the mac80211 driver which may or may
not work with the other wifi drivers that are build from linux-intel.
I played with this a little and I can send patches for comments.
-- Mikko
--
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel
