<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/x86/Kconfig, 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>2019-05-09T23:52:55Z</updated>
<entry>
<title>Fix spelling of available.</title>
<updated>2019-05-09T23:52:55Z</updated>
<author>
<name>Vagrant Cascadian</name>
</author>
<published>2019-05-03T22:28:37Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=048a92ea54355756292aa49a4cf88518a98ec37a'/>
<id>urn:sha1:048a92ea54355756292aa49a4cf88518a98ec37a</id>
<content type='text'>
Signed-off-by: Vagrant Cascadian &lt;vagrant@debian.org&gt;
</content>
</entry>
<entry>
<title>x86: Support booting with TPL</title>
<updated>2019-05-08T05:02:12Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-26T03:58:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=7c2ca877fee42085ad1b6ff24d9d10d91dcd9332'/>
<id>urn:sha1:7c2ca877fee42085ad1b6ff24d9d10d91dcd9332</id>
<content type='text'>
Some boards want to use TPL as the first phase of U-Boot. This allows
selection of A or B SPL phases, thus allowing the memory init to be
upgraded in the field.

Add a new Kconfig option for this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: Support SPL and TPL</title>
<updated>2019-05-08T05:02:11Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-26T03:58:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=9898790247040772e068f1ef9ac8a16c01d197ac'/>
<id>urn:sha1:9898790247040772e068f1ef9ac8a16c01d197ac</id>
<content type='text'>
At present only chromebook_link64 supports SPL. It is useful to eb able to
support both TPL and SPL to implement verified boot on x86.

Enable the options for both along with some suitable default options
needed to boot through these phases.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: kconfig: Allow board defconfig file to disable 8259 and APIC</title>
<updated>2018-12-10T02:14:34Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-11-30T03:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=2677a15e5839ee8f7073192a666348e2e3e5cdcd'/>
<id>urn:sha1:2677a15e5839ee8f7073192a666348e2e3e5cdcd</id>
<content type='text'>
At present the Kconfig options (CONFIG_I8259_PIC and CONFIG_APIC)
do not include a prompt message, which makes it impossible to
be disabled from a board defconfig file.

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: make the LAPIC / IOAPIC construct switchable with Kconfig</title>
<updated>2018-12-10T02:12:29Z</updated>
<author>
<name>Hannes Schmelzer</name>
</author>
<published>2018-11-18T22:19:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=da4cfa6b442809fc99a6b75255a99eee51a4e13b'/>
<id>urn:sha1:da4cfa6b442809fc99a6b75255a99eee51a4e13b</id>
<content type='text'>
There are still systems running which do not have any LAPIC or even
IOAPIC. Responsible MSRs for those do not exist and the systems are
crashing on trying to setup LAPIC.

This commit makes the APIC stuff able to switch off for those boards
which dont' have an LAPIC / IOAPIC.

Signed-off-by: Hannes Schmelzer &lt;oe5hpm@oevsv.at&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&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>x86: Conditionally build the pinctrl_ich6 driver</title>
<updated>2018-06-13T01:50:57Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2018-06-10T13:25:01Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=fcfc8a82b10c8acb844b8f0ed6c5d2cadce1291f'/>
<id>urn:sha1:fcfc8a82b10c8acb844b8f0ed6c5d2cadce1291f</id>
<content type='text'>
The pinctrl_ich6 driver is currently unconditionally built for all
x86 boards. Let's use a Kconfig option to control the build.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>pylibfdt: compile pylibfdt only when dtoc/binman is necessary</title>
<updated>2017-11-17T12:43:32Z</updated>
<author>
<name>Masahiro Yamada</name>
</author>
<published>2017-10-17T04:42:44Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=d6a0c78a4efb1353f4ec6f6c59c0771298510f58'/>
<id>urn:sha1:d6a0c78a4efb1353f4ec6f6c59c0771298510f58</id>
<content type='text'>
Currently, pylibfdt is always compiled if swig is installed on your
machine.  It is really annoying because most of targets (excepts
x86, sunxi, rockchip) do not use dtoc or binman.

"checkbinman" and "checkdtoc" are wrong.  It is odd that the final
build stage checks if we have built necessary tools.  If your platform
depends on dtoc/binman, you must be able to build pylibfdt.  If swig
is not installed, it should fail immediately.

I added PYLIBFDT, DTOC, BINMAN entries to Kconfig.  They should be
property select:ed by platforms that need them.  Kbuild will descend
into scripts/dtc/pylibfdt/ only when CONFIG_PYLIBFDT is enabled.

Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Revert "x86: fsp: Configure SPI opcode registers before SPI is locked down"</title>
<updated>2017-10-27T07:13:47Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2017-10-19T01:20:56Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=fb2c53091ff457ce8a0b547f37e7374d10d855ea'/>
<id>urn:sha1:fb2c53091ff457ce8a0b547f37e7374d10d855ea</id>
<content type='text'>
This reverts commit 1e6ebee667da47fd3a87839a239a7574c66f5659.

It's not appropriate to call the Intel SPI driver specific stuff in
the FSP codes. We may add a simple DTS property "intel,spi-lock-down"
and let the Intel SPI driver call these stuff instead.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: Fix ACPI resume dependency to MRC cache</title>
<updated>2017-10-27T07:13:47Z</updated>
<author>
<name>Bin Meng</name>
</author>
<published>2017-10-19T01:20:55Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=aa9c5956c9b921f3745e024d1572fd3dcc283091'/>
<id>urn:sha1:aa9c5956c9b921f3745e024d1572fd3dcc283091</id>
<content type='text'>
In an S3 resume path, MRC cache is mandatory. Enforce the dependency
in the Kconfig.

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