<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/arch/x86/include, branch v2018.09</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/arch/x86/include?h=v2018.09</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/arch/x86/include?h=v2018.09'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2018-08-30T03:23:15Z</updated>
<entry>
<title>x86: zimage: Remove acpi_rsdp_addr propagation to kernel boot parameters</title>
<updated>2018-08-30T03:23:15Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-08-24T04:28:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e69cc6bc42c37598e2fdda421360be6cbc0470fd'/>
<id>urn:sha1:e69cc6bc42c37598e2fdda421360be6cbc0470fd</id>
<content type='text'>
As of today, the proposal of adding "acpi_rsdp_addr" to the kernel
boot protocol does not make its way to the kernel mainline. This
creates some confusion if we leave it in the U-Boot code base.
Remove it for now until we have a clear picture with kernel upstream.

Note this eventually does a partial revert to commit 3469bf427454
("x86: zImage: Propagate acpi_rsdp_addr to kernel via boot parameters")

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Acked-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>x86: zimage: Support booting Linux kernel from an EFI payload</title>
<updated>2018-08-30T03:23:14Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-08-23T15:24:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1fdeacd32c6335acb7bd5f00c3f177013d971d3d'/>
<id>urn:sha1:1fdeacd32c6335acb7bd5f00c3f177013d971d3d</id>
<content type='text'>
At present Linux kernel loaded from U-Boot as an EFI payload does
not boot. This fills in kernel's boot params structure with the
required critical EFI information like system table address and
memory map stuff so that kernel can obtain essential data like
runtime services and ACPI table to boot.

With this patch, now U-Boot as an EFI payload becomes much more
practical: it is another option of kernel bootloader, ie, can be
a replacement for grub.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>elf: Move x86 reloc defines to common elf.h</title>
<updated>2018-07-25T12:57:43Z</updated>
<author>
<name>Alexander Graf</name>
<email>agraf@suse.de</email>
</author>
<published>2018-06-18T15:23:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=dae73c4cdc862017a10d09588571e7f98de0cdd4'/>
<id>urn:sha1:dae73c4cdc862017a10d09588571e7f98de0cdd4</id>
<content type='text'>
We need to know about x86 relocation definitions even in cases where
we don't officially build against the x86 target, such as with sandbox.

So let's move the x86 definitions into the common elf header, where all
other architectures already have them.

Signed-off-by: Alexander Graf &lt;agraf@suse.de&gt;
</content>
</entry>
<entry>
<title>x86: acpi: Prevent acpi_table.h from being included more than once</title>
<updated>2018-07-20T01:33:22Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-07-19T04:42:17Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=05855fd31a3f7483534aabe69a7030ff38978510'/>
<id>urn:sha1:05855fd31a3f7483534aabe69a7030ff38978510</id>
<content type='text'>
The wrapper #ifndef is currently missing in acpi_table.h. Add it to
prevent it from being included multiple times.

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: acpi: Move APIs unrelated to ACPI tables generation to a separate library</title>
<updated>2018-07-20T01:33:22Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-07-19T04:42:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a0609a8d19d4a9a86572fffb7cb8a3661fffbcf7'/>
<id>urn:sha1:a0609a8d19d4a9a86572fffb7cb8a3661fffbcf7</id>
<content type='text'>
acpi_find_fadt(), acpi_find_wakeup_vector() and enter_acpi_mode()
are something unrelated to ACPI tables generation. Move these to
a separate library.

This also fixes several style issues reported by checkpatch in the
original codes.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>x86: Switch to use DM sysreset driver</title>
<updated>2018-07-20T01:33:22Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-07-19T10:07:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b37b7b2063e02718970ca1882a4522ccbe1106e9'/>
<id>urn:sha1:b37b7b2063e02718970ca1882a4522ccbe1106e9</id>
<content type='text'>
This converts all x86 boards over to DM sysreset.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Tested-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&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: 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: 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: irq: Support discrete PIRQ routing registers via device tree</title>
<updated>2018-06-13T01:50:57Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2018-06-12T08:26:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=51050ff0a239f2640467d4c2fe54e0e8679a4093'/>
<id>urn:sha1:51050ff0a239f2640467d4c2fe54e0e8679a4093</id>
<content type='text'>
Currently both pirq_reg_to_linkno() and pirq_linkno_to_reg() assume
consecutive PIRQ routing control registers. But this is not always
the case on some platforms. Introduce a new device tree property
intel,pirq-regmap to describe how the PIRQ routing register offset
is mapped to the link number and adjust the irq router driver to
utilize the mapping.

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