Searched hist:"377656 b2cc3be3e704fc574041669a4a84ea6bb8" (Results 1 – 3 of 3) sorted by relevance
| /rk3399_rockchip-uboot/arch/x86/cpu/baytrail/ |
| H A D | Kconfig | 377656b2cc3be3e704fc574041669a4a84ea6bb8 Wed Jun 15 04:33:23 UTC 2016 Bin Meng <bmeng.cn@gmail.com> x86: baytrail: Introduce a Kconfig option for the internal UART
There are quite a number of BayTrail boards that uses an external
SuperIO chipset to provide the legacy UART. For such cases, it's
better to have a Kconfig option to enable the internal UART.
So far BayleyBay and MinnowMax boards are using internal UART as
the U-Boot console, enable this on these two boards.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| /rk3399_rockchip-uboot/configs/ |
| H A D | bayleybay_defconfig | 377656b2cc3be3e704fc574041669a4a84ea6bb8 Wed Jun 15 04:33:23 UTC 2016 Bin Meng <bmeng.cn@gmail.com> x86: baytrail: Introduce a Kconfig option for the internal UART
There are quite a number of BayTrail boards that uses an external
SuperIO chipset to provide the legacy UART. For such cases, it's
better to have a Kconfig option to enable the internal UART.
So far BayleyBay and MinnowMax boards are using internal UART as
the U-Boot console, enable this on these two boards.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
| H A D | minnowmax_defconfig | 377656b2cc3be3e704fc574041669a4a84ea6bb8 Wed Jun 15 04:33:23 UTC 2016 Bin Meng <bmeng.cn@gmail.com> x86: baytrail: Introduce a Kconfig option for the internal UART
There are quite a number of BayTrail boards that uses an external
SuperIO chipset to provide the legacy UART. For such cases, it's
better to have a Kconfig option to enable the internal UART.
So far BayleyBay and MinnowMax boards are using internal UART as
the U-Boot console, enable this on these two boards.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Stefan Roese <sr@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
|