<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/x86/cpu/efi, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2018-12-10T02:14:42Z</updated>
<entry>
<title>efi: payload: only init usb if necessary</title>
<updated>2018-12-10T02:14:42Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-11-30T04:07:13Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=d3d6531866f2d7aa85b053cef553090b251e909f'/>
<id>urn:sha1:d3d6531866f2d7aa85b053cef553090b251e909f</id>
<content type='text'>
Up until now the call to initialize the USB subsystem was hardcoded
for U-Boot running as an EFI payload. This was used to enable the
use of a USB keyboard in the U-Boot shell. However not all boards
might need this functionality. As initializing the USB subsystem can
take a considerable amount of time (several seconds on some boards),
we now initialize the USB subsystem only if U-Boot is configured to
use USB keyboards.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Christian Gmeiner &lt;christian.gmeiner@gmail.com&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>
</author>
<published>2018-08-23T15:24:10Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/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>x86: efi: payload: Install E820 map from EFI memory map</title>
<updated>2018-08-30T01:56:58Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-08-23T15:24:08Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=aac79251c7dfeb325f17dbded3076df278bfca89'/>
<id>urn:sha1:aac79251c7dfeb325f17dbded3076df278bfca89</id>
<content type='text'>
This implements payload-specific install_e820_map() to get E820 map
from the EFI memory map descriptors.

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>
</author>
<published>2018-06-22T08:38:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/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: efi-x86_payload: Enable usb keyboard during boot</title>
<updated>2018-06-24T00:56:04Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-17T12:57:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/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: efi: app: Display correct CPU info during boot</title>
<updated>2018-06-17T13:16:04Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-12T15:36:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/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>
<entry>
<title>x86: Rename efi-x86 target to efi-x86_app</title>
<updated>2018-06-17T13:16:04Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-12T15:36:24Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=3ebd892fda2d07f153a14cb30e60ae707e9e4208'/>
<id>urn:sha1:3ebd892fda2d07f153a14cb30e60ae707e9e4208</id>
<content type='text'>
To avoid confusion, let's rename the efi-x86 target to efi-x86_app.

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: Add arch_cpu_init()</title>
<updated>2018-06-17T13:16:04Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-12T15:36:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=3773c6a20a1cd736a340f1141a6d3d8ee3c2ddc6'/>
<id>urn:sha1:3773c6a20a1cd736a340f1141a6d3d8ee3c2ddc6</id>
<content type='text'>
This adds arch_cpu_init() to the payload codes, in preparation for
supporting a generic efi payload.

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: Refactor the directory of EFI app and payload support</title>
<updated>2018-06-17T13:16:04Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-12T15:36:16Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=4f1dacd43fcb5d4e97407df51b48dfde5e920078'/>
<id>urn:sha1:4f1dacd43fcb5d4e97407df51b48dfde5e920078</id>
<content type='text'>
At present the EFI application and payload support codes in the x86
directory is distributed in a hybrid way. For example, the Kconfig
options for both app and payload are in arch/x86/lib/efi/Kconfig,
but the source codes in the same directory get built only for
CONFIG_EFI_STUB.

This refactors the codes by consolidating all the EFI support codes
into arch/x86/cpu/efi, just like 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>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
