On 9/18/14, 9:18, "Kamble, Nitin A" <nitin.a.kam...@intel.com> wrote:
> > >On 9/18/14, 9:13 AM, "Hart, Darren" <darren.h...@intel.com> wrote: > >>On 9/17/14, 13:51, "Kamble, Nitin A" <nitin.a.kam...@intel.com> wrote: >> >>>>The problem with this of course is we can't use it easily with the >>>>common >>>>BSPs and ultimately we want to eliminate as many of the other BSPs as >>>>possible. >>>> >>>>What is the exact issue with microcode? How does it break certain >>>>systems >>>>when enabled on the intel common BSPs? >>> >>>1st there is no boot issue related to microcode. What was reported is a >>>build issue. His initrd file was not built correctly. And we believe >>>that >>>it happened because he used older version of poky/oecore. So that is >>>turning out to be a build setup issue. >>> >>>Here are the updates on the bug: >>>https://bugzilla.yoctoproject.org/show_bug.cgi?id=6730 >>> >>> >>>Nitin >> >>Oh great! >> >>So what's the status of this then? Can it be enabled by default? > > >I see no blockage for enabling by default. But usages like microyocto may >want to disable the feature to save some space. So I am working on make >the the intel microcode feature available as a machine feature, and all >the machines in meta-intel will include the machine feature. Right, and I should have said "make it the default for intel-core* machines". Thanks Nitin, -- Darren Hart Open Source Technology Center darren.h...@intel.com Intel Corporation -- _______________________________________________ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel