u-boot.git/board/coreboot, branch v2018.01 Unnamed repository; edit this file 'description' to name the repository. x86: kconfig: Let board select SPI flash 2017-08-01T12:17:02+00:00 Bin Meng bmeng.cn@gmail.com 2017-07-30T13:23:26+00:00 1df7f0b6a00c2080c50de775b4ef621aad24c47e Only a specific type of SPI flash exists on a board, having board Kconfig to select the SPI flash seems to make more sense. Other flash types are not necessary except coreboot, which implies all available flash drivers there. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Only a specific type of SPI flash exists on a board, having board
Kconfig to select the SPI flash seems to make more sense. Other
flash types are not necessary except coreboot, which implies all
available flash drivers there.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
x86: kconfig: Select ARCH_EARLY_INIT_R in the platform Kconfig 2017-08-01T12:17:02+00:00 Bin Meng bmeng.cn@gmail.com 2017-07-30T13:23:13+00:00 5d89b37f71ff1833bdd34eeba6dbac6bec1c9fb2 This is architecture-dependent early initialization hence should be put in the platform Kconfig. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
This is architecture-dependent early initialization hence should
be put in the platform Kconfig.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
x86: Drop all the old pin configuration code 2016-03-17T02:27:25+00:00 Simon Glass sjg@chromium.org 2016-03-12T05:07:15+00:00 779653b0cbe3f634632bc4ecae1ce5df84638326 We don't need this anymore - we can use device tree and the new pinconfig driver instead. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> 
We don't need this anymore - we can use device tree and the new pinconfig
driver instead.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
x86: qemu: Create separate i440fx and q35 device trees 2015-06-04T09:03:18+00:00 Bin Meng bmeng.cn@gmail.com 2015-06-03T01:20:04+00:00 683b09d7837a71fb4c5dd53919c6afa4d800e60e Although the two qemu-x86 targets (i440fx and q35) share a lot in common, they still have something that cannot easily handled in one single device tree). Split to create two dedicated device tree files and make the i440fx be the default build target. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> 
Although the two qemu-x86 targets (i440fx and q35) share a lot in
common, they still have something that cannot easily handled in one
single device tree). Split to create two dedicated device tree files
and make the i440fx be the default build target.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
x86: Change coreboot default build configuration to QEMU 2015-06-04T08:39:38+00:00 Bin Meng bmeng.cn@gmail.com 2015-05-07T13:34:11+00:00 b28c1475691add24ecd220c69ccc469c77d9fc57 QEMU is much easier for us test booting U-Boot as a coreboot payload than having a real board like chromebook_link. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> Tested-by: Simon Glass <sjg@chromium.org> 
QEMU is much easier for us test booting U-Boot as a coreboot payload
than having a real board like chromebook_link.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
arch: Make board selection choices optional 2015-05-12T22:10:02+00:00 Joe Hershberger joe.hershberger@ni.com 2015-05-12T19:46:23+00:00 a26cd04920dc069fd6e91abb785426cf6c29f45f By making the board selections optional, every defconfig will include the board selection when running savedefconfig so if a new board is added to the top of the list of choices the former top's defconfig will still be correct. Signed-off-by: Joe Hershberger <joe.hershberger@ni.com> Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Stephen Warren <swarren@wwwdotorg.org> Cc: Tom Rini <trini@konsulko.com> 
By making the board selections optional, every defconfig will include
the board selection when running savedefconfig so if a new board is
added to the top of the list of choices the former top's defconfig will
still be correct.

Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Cc: Tom Rini <trini@konsulko.com>
x86: Kconfig: Remove deprecated CONFIG_SYS_EXTRA_OPTIONS 2015-04-30T00:51:50+00:00 Bin Meng bmeng.cn@gmail.com 2015-04-27T15:22:28+00:00 99556d7debe02d3af4c1b5cc17ad5fa457c2ce67 Currently all x86 boards still use CONFIG_SYS_EXTRA_OPTIONS to define the text base address. Since it is deprecated, just remove it and use CONFIG_SYS_TEXT_BASE directly. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> 
Currently all x86 boards still use CONFIG_SYS_EXTRA_OPTIONS to define
the text base address. Since it is deprecated, just remove it and use
CONFIG_SYS_TEXT_BASE directly.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
x86: Kconfig: Divide the target selection to vendor/model 2015-04-30T00:51:50+00:00 Bin Meng bmeng.cn@gmail.com 2015-04-27T15:22:24+00:00 65c4ac0a831d1a8640602ae966f913ec811843eb Let arch/x86/Kconfig prompt board vendor first, then select the board model under that vendor. This way arch/x86/Kconfig only needs concern board vendor and leave the supported target list to board/<vendor>/Kconfig. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> 
Let arch/x86/Kconfig prompt board vendor first, then select
the board model under that vendor. This way arch/x86/Kconfig
only needs concern board vendor and leave the supported target
list to board/<vendor>/Kconfig.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>
x86: cros_ec: Drop unnecessary init 2015-04-18T17:11:15+00:00 Simon Glass sjg@chromium.org 2015-03-26T15:29:34+00:00 a5dec5a5c4470901580383e91764ba0c6f3832a6 Since driver model will probe the EC when it is first used, we do not need to init it explicitly. Signed-off-by: Simon Glass <sjg@chromium.org> 
Since driver model will probe the EC when it is first used, we do not
need to init it explicitly.

Signed-off-by: Simon Glass <sjg@chromium.org>
x86: coreboot: Wrap cros_ec initialization 2015-01-13T15:25:04+00:00 Bin Meng bmeng.cn@gmail.com 2015-01-06T14:14:22+00:00 48a223e4ba0a7fec5940cccf7950b656e4f7cbed cros_ec_board_init() should be called only when CONFIG_CROS_EC is enabled. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org> 
cros_ec_board_init() should be called only when CONFIG_CROS_EC is
enabled.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Acked-by: Simon Glass <sjg@chromium.org>