Not really sure I understand this part? The code in coreboot_table.c creates the device that represents the entry in the table. The code in framebuffer-coreboot.c (which this Kconfig guards) contains the code that creates the device which will be the actual framebuffer. Doesn't it make sense for that part to depend on a framebuffer backend being available?
- Re: [PATCH v2 05/12] firmware: google: framebuffer: Fix ... Julius Werner
- Re: [PATCH v2 05/12] firmware: google: framebuffer:... Thomas Zimmermann
- Re: [PATCH v2 05/12] firmware: google: framebuf... Julius Werner
- Re: [PATCH v2 05/12] firmware: google: fram... Thomas Zimmermann
- Re: [PATCH v2 05/12] firmware: google: framebuffer:... Tzung-Bi Shih
