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 <s...@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. -- 2.5.0.276.gf5e568e _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot