Hi Bin,
On 9 November 2014 20:02, Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Fri, Nov 7, 2014 at 4:20 AM, Simon Glass sjg@chromium.org wrote:
Add two microcode updates that are provided for this CPU. The updates have been converted to a device tree form.
(The license needs to be converted to SPDX)
Signed-off-by: Simon Glass sjg@chromium.org
arch/x86/dts/link.dts | 10 + arch/x86/dts/m12206a7_00000028.dtsi | 622 ++++++++++++++++++++++++++++++ arch/x86/dts/m12306a9_00000017.dtsi | 750 ++++++++++++++++++++++++++++++++++++ 3 files changed, 1382 insertions(+) create mode 100644 arch/x86/dts/m12206a7_00000028.dtsi create mode 100644 arch/x86/dts/m12306a9_00000017.dtsi
diff --git a/arch/x86/dts/link.dts b/arch/x86/dts/link.dts index 2e91631..ea4b0ba 100644 --- a/arch/x86/dts/link.dts +++ b/arch/x86/dts/link.dts @@ -67,4 +67,14 @@ }; }; };
microcode {update@0 {+#include "m12206a7_00000028.dtsi"
};update@1 {+#include "m12306a9_00000017.dtsi"
};};}; diff --git a/arch/x86/dts/m12206a7_00000028.dtsi b/arch/x86/dts/m12206a7_00000028.dtsi new file mode 100644 index 0000000..bcd5248 --- /dev/null +++ b/arch/x86/dts/m12206a7_00000028.dtsi @@ -0,0 +1,622 @@ +/*
- Copyright (c) <1995-2013>, Intel Corporation.
- All rights reserved.
- Redistribution. Redistribution and use in binary form, without modification, are
- permitted provided that the following conditions are met:
.Redistributions must reproduce the above copyright notice and the following
- disclaimer in the documentation and/or other materials provided with the
- distribution.
- Neither the name of Intel Corporation nor the names of its suppliers may be used
- to endorse or promote products derived from this software without specific prior
- written permission.
.No reverse engineering, decompilation, or disassembly of this software is
- permitted.
."Binary form" includes any format commonly used for electronic conveyance
- which is a reversible, bit-exact translation of binary representation to ASCII or
- ISO text, for example, "uuencode."
- DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
- HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
- WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
- WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
- PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
- OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
- CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
- ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- *---
- This is a device tree fragment. Use #include to add these properties to a
- node.
- */
+compatible = "intel,microcode"; +intel,header-version = <1>; +intel,update-revision = <0x28>; +intel,date-code = <0x04242012>; +intel,processor-signature = <0x000206a7>; +intel,checksum = <0xf3e9935d>; +intel,loader-revision = <1>; +intel,processor-flags = <0x12>;
+/* The 48-byte public header is omitted. */ +data = <
0x00000000 0x000000a1 0x00020001 0x000000280x00000000 0x00000000 0x20120423 0x000008f10x00000001 0x000206a7 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x000000000x00000000 0x000008f1 0x00000000 0x000000000x00000000 0x00000000 0x00000000 0x00000000Do you plan to create a tool to convert the Intel released microcode file to dts automatically? Or if not, we need document on how to convert the Intel version to dts manually, maybe in the dts-bindings documentation.
Yes I think a tool would be great. It could operate on the tar file that Intel provides. I'll take a look sometime.
Regards, Simon