u-boot.git/board/google, branch v2017.09 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: kconfig: Let board select BOARD_EARLY_INIT_F 2017-08-01T12:17:02+00:00 Bin Meng bmeng.cn@gmail.com 2017-07-30T13:23:11+00:00 30b1ecd26533fdd680b66c0ed6767cc4b875fbc6 CONFIG_BOARD_EARLY_INIT_F literally indicates board-specific codes and should be not 'default y' for all x86 boards. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
CONFIG_BOARD_EARLY_INIT_F literally indicates board-specific codes
and should be not 'default y' for all x86 boards.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
rockchip: Correct MAINTAINER entry for chromebook_minnie 2017-02-09T19:10:59+00:00 Simon Glass sjg@chromium.org 2017-01-14T17:26:08+00:00 f568ac219c8db716df1726b383a70553407ca77e This is wrong at present, so genboardscfg.py gives the following warnings: WARNING: no status info for 'chromebook_minnie' WARNING: no maintainers for 'chromebook_minnie' Fix it. Signed-off-by: Simon Glass <sjg@chromium.org> 
This is wrong at present, so genboardscfg.py gives the following warnings:

WARNING: no status info for 'chromebook_minnie'
WARNING: no maintainers for 'chromebook_minnie'

Fix it.

Signed-off-by: Simon Glass <sjg@chromium.org>
x86: link: Add a config for 64-bit U-Boot 2017-02-07T05:16:27+00:00 Simon Glass sjg@chromium.org 2017-01-16T14:04:27+00:00 fda4eb48e60b0ea5a575ed7bc0b853fc6db2da29 Add a new board config which uses 64-bit U-Boot. This is not fully functional but is it a start. Missing features: - SDRAM sizing - Booting linux - EFI support - SCSI device init (and others) Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> 
Add a new board config which uses 64-bit U-Boot. This is not fully
functional but is it a start. Missing features:

- SDRAM sizing
- Booting linux
- EFI support
- SCSI device init
(and others)

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
x86: link: Add a text base for 64-bit U-Boot 2017-02-07T05:10:53+00:00 Simon Glass sjg@chromium.org 2017-01-16T14:04:22+00:00 19f8b32cea3021b116ad196eb0194af22532fcd8 Set up the 64-bit U-Boot text base if building for that target. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> 
Set up the 64-bit U-Boot text base if building for that target.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
rockchip: Add support for veyron-minnie (ASUS Chromebook Flip) 2016-11-26T00:59:32+00:00 Simon Glass sjg@chromium.org 2016-11-13T21:24:54+00:00 c420ef67e5799d80b807c2866576bf3881893cbf This adds support for the Asus Chromebook Flip, an RK3288-based clamshell device which can flip into 'tablet' mode. The device tree file comes from Linux v4.8. The SDRAM parameters are for 4GB Samsung LPDDR3. Signed-off-by: Simon Glass <sjg@chromium.org> 
This adds support for the Asus Chromebook Flip, an RK3288-based clamshell
device which can flip into 'tablet' mode. The device tree file comes from
Linux v4.8. The SDRAM parameters are for 4GB Samsung LPDDR3.

Signed-off-by: Simon Glass <sjg@chromium.org>
rockchip: Add support for veyron-mickey (Chromebit) 2016-11-26T00:59:32+00:00 Simon Glass sjg@chromium.org 2016-11-13T21:22:16+00:00 e70408c069795fc2084aaee65a1a6c5f42c91a8f This adds support for the Asus Chromebit, and RK3288-based device designed to plug directly into an HDMI monitor. The device tree file comes from Linux v4.8. Signed-off-by: Simon Glass <sjg@chromium.org> 
This adds support for the Asus Chromebit, and RK3288-based device designed
to plug directly into an HDMI monitor. The device tree file comes from
Linux v4.8.

Signed-off-by: Simon Glass <sjg@chromium.org>
rockchip: veyron: Add a note about the SDRAM voltage 2016-11-26T00:59:31+00:00 Simon Glass sjg@chromium.org 2016-11-13T21:22:11+00:00 38ffcb679b1694f8ebf4e5670614fb830ae0c2f2 Add a comment to indicate that we are not supporting the PWM regulator yet. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a comment to indicate that we are not supporting the PWM regulator
yet.

Signed-off-by: Simon Glass <sjg@chromium.org>
rockchip: Rename jerry files to veyron 2016-11-26T00:59:31+00:00 Simon Glass sjg@chromium.org 2016-11-13T21:22:10+00:00 5e9b15034b9e38a6908610229788cf0746d138fc At present we have a single rk3288-based Chromebook: chromebook_jerry. But all such Chromebooks can use the same binary with only device-tree differences. The family name is 'veyron', so rename the files accordingly. Also update the device-tree filename since this currently differs from Linux. Signed-off-by: Simon Glass <sjg@chromium.org> 
At present we have a single rk3288-based Chromebook: chromebook_jerry. But
all such Chromebooks can use the same binary with only device-tree
differences. The family name is 'veyron', so rename the files accordingly.

Also update the device-tree filename since this currently differs from
Linux.

Signed-off-by: Simon Glass <sjg@chromium.org>