diff options
author | Nico Huber <nico.huber@secunet.com> | 2017-05-22 13:49:22 +0200 |
---|---|---|
committer | Nico Huber <nico.h@gmx.de> | 2017-06-08 14:58:15 +0200 |
commit | d4ebeaf475dc1137f489f12ffa4e55d914238662 (patch) | |
tree | 413472484c5fbb9ac2f2a003b592c37bbc0ce826 /src/mainboard/google/beltino/lan.c | |
parent | 26ce9af9a04ae282ff7c186eac0476f13a37cfa0 (diff) |
device/Kconfig: Put gfx init methods into a `choice`
Provide all gfx init methods as a Kconfig `choice`. This elimates the
option to select native gfx init along with running a Video BIOS. It's
been only theoretically useful in one corner case: Hybrid graphics
where only one controller is supported by native gfx init. Though I
suppose in that case it's fair to assume that one would use SeaBIOS to
run the VBIOS.
For the case that we want the payload to initialize graphics or no
pre-boot graphics at all, the new symbol NO_GFX_INIT was added to the
choice. If multiple options are available, the default is chosen as
follows:
* NO_GFX_INIT, if we add a Video BIOS and the payload is SeaBIOS,
* VGA_ROM_RUN, if we add a Video BIOS and the payload is not SeaBIOS,
* NATIVE_VGA_INIT, if we don't add a Video BIOS.
As a side effect, libgfxinit is now an independent choice.
Change-Id: I06bc65ecf3724f299f59888a97219fdbd3d2d08b
Signed-off-by: Nico Huber <nico.huber@secunet.com>
Reviewed-on: https://review.coreboot.org/19814
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/mainboard/google/beltino/lan.c')
0 files changed, 0 insertions, 0 deletions