[U-Boot] [PATCH v2 6/6] x86: Convert microcode format to device-tree-only

Bin Meng bmeng.cn at gmail.com
Wed Dec 17 09:07:30 CET 2014


Hi Simon,

On Wed, Dec 17, 2014 at 10:49 AM, Simon Glass <sjg at chromium.org> wrote:
> Hi Bin,
>
> On 16 December 2014 at 03:01, Bin Meng <bmeng.cn at gmail.com> wrote:
>> On Tue, Dec 16, 2014 at 1:02 PM, Simon Glass <sjg at chromium.org> wrote:
>>> To avoid having two microcode formats, adjust the build system to support
>>> obtaining the microcode from the device tree, even in the case where it
>>> must be made available before the device tree can be accessed.
>>>
>>> Also move the microcode for queensbay (unfortunately the wrong version).
>>>
>>> Signed-off-by: Simon Glass <sjg at chromium.org>
>>> ---
>>>
>>> Changes in v2:
>>> - Update microcode file to version 5_cv
>>> - Drop patches that have already been applied
>>>
>>>  Makefile                                   |    4 +-
>>>  arch/x86/cpu/queensbay/M0220661105.inc     | 1288 ----------------------------
>>>  arch/x86/cpu/queensbay/tnc_car.S           |   11 +-
>>>  arch/x86/dts/crownbay.dts                  |    7 +
>>>  arch/x86/dts/microcode/m0220661105_cv.dtsi |  366 ++++++++
>>>  5 files changed, 380 insertions(+), 1296 deletions(-)
>>>  delete mode 100644 arch/x86/cpu/queensbay/M0220661105.inc
>>>  create mode 100644 arch/x86/dts/microcode/m0220661105_cv.dtsi
>>>
> [snip]
>>> --
>>
>> Reviewed-by: Bin Meng <bmeng.cn at gmail.com>
>>
>> Tested on Intel Crown Bay
>>
>> Tested-by: Bin Meng <bmeng.cn at gmail.com>
>
> This patch is for you, I cannot apply it as it depends on one of your
> patches. If I apply your patch then it breaks the build.
>
> So it would be best if you squashed this patch into one of yours. I'll
> push everything to x86/master (except the microcode patch which needs
> another rev) ready for you to rebase your patches.
>
> Regards,
> Simon

This patch is integrated into my series @
http://patchwork.ozlabs.org/patch/422192/. Thanks!

Regards,
Bin


More information about the U-Boot mailing list