> -----Original Message----- > From: linux-yocto-boun...@yoctoproject.org [mailto:linux-yocto- > boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A > Sent: Friday, May 16, 2014 1:52 AM > To: linux-yocto@yoctoproject.org > Subject: Re: [linux-yocto] [PATCH 0/5] [linux-yocto-3.10] Update meta for > Romley platform configuration > > > On 5/15/2014 12:22 PM, wei.sern.c...@intel.com wrote: > > From: Chan Wei Sern <wei.sern.c...@intel.com> > > > > Hi All, > > > > This is a patch series targetting linux-yocto-3.10:meta branch. > > > > This is a patch series that consist of below: > > 1. Removed using of common-pc-64.scc from romley. > > 2. Start using ktypes/standard/standard.scc for romley platforms to align > with YP1.6 > > Intel common kernel. > > 3. Add back RTC configuration for romley after changing from common-pc- > 64.scc > > to standard.scc. > > 4. Add back USB HID configuration for romley after changing from > common-pc-64.scc > > to standard.scc. > > 5. Due to not all platform's BIOS comes ready with AMT/MEI firmware. > > So will change > The issue here is not of missing firmware, but of broken MEI firmware on the > target. It is actually a hardware/fimware issue which we are trying to deal > with in the OS. > > CONFIG_INTEL_MEI_ME from built-in driver to as module driver. This will > then > > make possible for appending this driver on /etc/modprobe.d/blacklist to > allow > > Romley to reboot without issue. > > ( Will place a note on the README to mention that user has to append > > on /etc/modprobe.d/blacklist to make the reboot happened ). > This need be done in a custon recipe for the BSP, instead of mentioning in > the README. > Noted. Will find a way to blacklist the MEI driver in custom recipe and placed them under meta-romley.
> > > > > > For this patch series, I have done below:- 1. Build smoothly and boot > > test on romley. > > 2. Boot test on Romley via USB drive and SATA. > > 3. Confirm all the IO drivers are loaded propperly. > > 4. Confirm reboot issue is solved. > Did just converting to modules solved the issue? Or blacklisting of the MEI > module was also needed? > > Thanks, > Nitin > It needs blacklisting still after making the MEI related config to module and for your info, It will only take effect on 2nd reboot and onwards. Agree this has to be placed under custom recipe just like your suggestion. Thanks. Regards, Wei Sern. > > > > Thanks. > > Regards, > > Chan Wei Sern > > The following changes since commit > d07bc7ba4ff00ddcd77db1026a63c327b81a35d8: > > > > meta: crystalforest: included USB HID configuration (2014-05-12 > > 16:47:35 -0400) > > > > are available in the git repository at: > > > > git://git.yoctoproject.org/linux-yocto-contrib wchan9/romley-common- > meta > > > > http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=wchan9 > > /romley-common-meta > > > > Sreeju Selvaraj (4): > > meta: romley: removed using of common-pc-64.scc > > meta: romley: added power management > > meta: romley: included USB HID Configuration > > meta: romley: included RTC configuration > > > > Sreeju Slevaraj (1): > > mei.cfg: configure Intel MEI driver as module > > > > meta/cfg/kernel-cache/bsp/romley/romley-preempt-rt.scc | 1 - > > meta/cfg/kernel-cache/bsp/romley/romley-standard.scc | 3 +-- > > meta/cfg/kernel-cache/bsp/romley/romley.cfg | 4 ++++ > > meta/cfg/kernel-cache/bsp/romley/romley.scc | 3 +++ > > meta/cfg/kernel-cache/features/amt/mei/mei.cfg | 2 +- > > 5 files changed, 9 insertions(+), 4 deletions(-) > > > > -- > _______________________________________________ > linux-yocto mailing list > linux-yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/linux-yocto -- _______________________________________________ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
