[U-Boot] [PATCH v2 1/7] x86: Correct microcode documentation

Bin Meng bmeng.cn at gmail.com
Wed Aug 19 05:36:12 CEST 2015


On Sun, Aug 16, 2015 at 4:37 AM, Simon Glass <sjg at chromium.org> wrote:
> This is incorrect since we require the -m parameter to the microcode tool.
> Update the two examples to show this.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
>
> Changes in v2: None
>
>  doc/README.x86 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/README.x86 b/doc/README.x86
> index e7dc090..8c3e176 100644
> --- a/doc/README.x86
> +++ b/doc/README.x86
> @@ -654,13 +654,13 @@ Use the device tree for configuration where possible.
>  For the microcode you can create a suitable device tree file using the
>  microcode tool:
>
> -  ./tools/microcode-tool -d microcode.dat create <model>
> +  ./tools/microcode-tool -d microcode.dat -m <model> create
>
>  or if you only have header files and not the full Intel microcode.dat database:
>
>    ./tools/microcode-tool -H BAY_TRAIL_FSP_KIT/Microcode/M0130673322.h \
>         -H BAY_TRAIL_FSP_KIT/Microcode/M0130679901.h \
> -       create all
> +       -m all create
>
>  These are written to arch/x86/dts/microcode/ by default.
>
> --

Reviewed-by: Bin Meng <bmeng.cn at gmail.com>


More information about the U-Boot mailing list