<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/x86, branch v2018.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/arch/x86?h=v2018.07</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/x86?h=v2018.07'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2018-07-02T01:23:28Z</updated>
<entry>
<title>x86: efi_loader: Build EFI memory map per E820 table</title>
<updated>2018-07-02T01:23:28Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-28T03:38:01Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=abe47ca728f5b22d1ec9fcf609e00b331c4d5273'/>
<id>urn:sha1:abe47ca728f5b22d1ec9fcf609e00b331c4d5273</id>
<content type='text'>
On x86 traditional E820 table is used to pass the memory information
to kernel. With EFI loader we can build the EFI memory map from it.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: Use microcode update from device tree for all processors</title>
<updated>2018-07-02T01:23:28Z</updated>
<author>
<name>Ivan Gorinov</name>
<email>ivan.gorinov@intel.com</email>
</author>
<published>2018-06-22T04:16:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8199a145c40791f0bc272fc016494028cf250195'/>
<id>urn:sha1:8199a145c40791f0bc272fc016494028cf250195</id>
<content type='text'>
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 Device Tree, use the same data block for the other processors.

Signed-off-by: Ivan Gorinov &lt;ivan.gorinov@intel.com&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
[bmeng: fixed build errors on edison and qemu-x86]
Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: Add scsi command to coreboot and qemu</title>
<updated>2018-07-02T01:23:28Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-26T10:58:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fc48ebe6dff059a799c8f85e31ee8dea6c2f77d8'/>
<id>urn:sha1:fc48ebe6dff059a799c8f85e31ee8dea6c2f77d8</id>
<content type='text'>
This adds the scsi command to coreboot and qemu, to be in consistent
with other x86 targets.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: efi: payload: Count in conventional memory above 4GB in DRAM bank</title>
<updated>2018-06-24T00:56:25Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-22T08:38:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=598374729e6b3f3070e06bdf2990dd8d10cddbda'/>
<id>urn:sha1:598374729e6b3f3070e06bdf2990dd8d10cddbda</id>
<content type='text'>
At present in dram_init_banksize() it ignores conventional memory
above 4GB. This leads to wrong DRAM size is printed during boot.
Remove such limitation.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: Change __kernel_size_t conditionals to use compiler provided defines</title>
<updated>2018-06-24T00:56:04Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-22T08:38:27Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5460fd076263a461442e4beb3215466536166026'/>
<id>urn:sha1:5460fd076263a461442e4beb3215466536166026</id>
<content type='text'>
Since commit bb0bb91cf0aa ("efi_stub: Use efi_uintn_t"), EFI x86
64-bit payload does not work anymore. The call to GetMemoryMap()
in efi_stub.c fails with return code EFI_INVALID_PARAMETER. Since
the payload itself is still 32-bit U-Boot, efi_uintn_t gets wrongly
interpreted as int, but it should actually be long in a 64-bit EFI
environment.

This changes the x86 __kernel_size_t conditionals to use compiler
provided defines instead. That way we always adhere to the build
environment we're in and the definitions adjust automatically.

Fixes: bb0bb91cf0aa ("efi_stub: Use efi_uintn_t")
Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: efi-x86_payload: Enable usb keyboard during boot</title>
<updated>2018-06-24T00:56:04Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-17T12:57:53Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1ab2c010879baff93c690be8d98d294e9ccfab94'/>
<id>urn:sha1:1ab2c010879baff93c690be8d98d294e9ccfab94</id>
<content type='text'>
For boards that don't route serial port pins out, it's quite common
to attach a USB keyboard as the input device, along with a monitor.
However USB is not automatically started in the generic efi payload
codes. This uses a payload specific last_stage_init() to start the
USB bus, so that a USB keyboard can be used on the U-Boot shell.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: Add 64-bit setjmp/longjmp implementation</title>
<updated>2018-06-24T00:56:04Z</updated>
<author>
<name>Ivan Gorinov</name>
<email>ivan.gorinov@intel.com</email>
</author>
<published>2018-06-19T18:40:42Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=964927323ff0b0cb7b00320d08589db7b429e442'/>
<id>urn:sha1:964927323ff0b0cb7b00320d08589db7b429e442</id>
<content type='text'>
Add setjmp/longjmp functions for x86_64.

Signed-off-by: Ivan Gorinov &lt;ivan.gorinov@intel.com&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: qemu: do not build car.o with start64.o</title>
<updated>2018-06-24T00:56:04Z</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>xypron.glpk@gmx.de</email>
</author>
<published>2018-06-19T17:12:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=cbd29ef9f1bbd837f363eb3f80a2f6ed9400a87c'/>
<id>urn:sha1:cbd29ef9f1bbd837f363eb3f80a2f6ed9400a87c</id>
<content type='text'>
car.o can only be used with start.o, not with start64.o.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>.gitignore: move *.dtb and *.dtb.S patterns to the top-level .gitignore</title>
<updated>2018-06-18T18:43:12Z</updated>
<author>
<name>Masahiro Yamada</name>
<email>yamada.masahiro@socionext.com</email>
</author>
<published>2018-06-11T07:21:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=28b538b69dd44b5f4ea595059612115069ace96b'/>
<id>urn:sha1:28b538b69dd44b5f4ea595059612115069ace96b</id>
<content type='text'>
Follow Linux commit 10b62a2f785a (".gitignore: move *.dtb and *.dtb.S
patterns to the top-level .gitignore").

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
</content>
</entry>
<entry>
<title>x86: efi: app: Display correct CPU info during boot</title>
<updated>2018-06-17T13:16:04Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-12T15:36:25Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0102023966558075e52758bd22ffd8f96b093a7e'/>
<id>urn:sha1:0102023966558075e52758bd22ffd8f96b093a7e</id>
<content type='text'>
Currently when EFI application boots, it says:

  CPU: x86_64, vendor &lt;invalid cpu vendor&gt;, device 0h

Fix this by calling x86_cpu_init_f() in arch_cpu_init().

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
