Hi Ivan,
On Tue, Jun 19, 2018 at 9:19 AM, Bin Meng wrote:
> On Mon, Jun 18, 2018 at 8:58 PM, Bin Meng wrote:
>> On Sat, Jun 16, 2018 at 2:01 AM, Ivan Gorinov wrote:
>>> Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
>>> the microcode update data block encoded in Devi
On Mon, Jun 18, 2018 at 8:58 PM, Bin Meng wrote:
> On Sat, Jun 16, 2018 at 2:01 AM, Ivan Gorinov wrote:
>> Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
>> the microcode update data block encoded in Device Tree to the bootstrap
>> processor but not passed to the other
On Sat, Jun 16, 2018 at 2:01 AM, Ivan Gorinov wrote:
> Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
> the microcode update data block encoded in Device Tree to the bootstrap
> processor but not passed to the other CPUs when multiprocessing is enabled.
>
> If the boots
Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
the microcode update data block encoded in Device Tree to the bootstrap
processor but not passed to the other CPUs when multiprocessing is enabled.
If the bootstrap processor successfully performs a microcode update
from De
Built without a ROM image with FSP (u-boot.rom), the U-Boot loader applies
the microcode update data block encoded in Device Tree to the bootstrap
processor but not passed to the other CPUs when multiprocessing is enabled.
If the bootstrap processor successfully performs a microcode update
from De
5 matches
Mail list logo
