> > --- a/meta/cfg/kernel-cache/features/amt/mei/mei.cfg > > +++ b/meta/cfg/kernel-cache/features/amt/mei/mei.cfg > > @@ -1,4 +1,4 @@ > > CONFIG_STAGING=y > > CONFIG_WATCHDOG_CORE=y > > CONFIG_INTEL_MEI=y > The CONFIG_INTEL_MEI also need to be converted to module. > I realize that there is no CONFIG_INTEL_MEI_TXE which is meant for BayTrail. mei.scc is added in meta-intel/common/recipes-kernel/linux/linux-yocto_3.10.bbappend with comment for NUC & valleyisland. So, I think this is a miss for Baytrail case.
Ya, agree that we should make all of the following configs as module. CONFIG_INTEL_MEI=m CONFIG_INTEL_MEI_ME=m CONFIG_INTEL_MEI_TXE=m I am curious why "etc/modprobe.d/blacklist" is needed if these are kernel module and the user should have the wisdom to know whether its Romley platform has the correct ME firmware or not. Adding the blacklist will reject any Romley platform with correct ME firmware to load the kernel altogether. + -- _______________________________________________ linux-yocto mailing list linux-yo...@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
