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?
- [PATCH v2 00/12] drm, coreboot: Add DRM coreboot driver Thomas Zimmermann
- [PATCH v2 02/12] firmware: google: framebuffer: Do ... Thomas Zimmermann
- Re: [PATCH v2 02/12] firmware: google: framebuf... Tzung-Bi Shih
- [PATCH v2 05/12] firmware: google: framebuffer: Fix... 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: ... Julius Werner
- Re: [PATCH v2 05/12] firmware: goo... Thomas Zimmermann
- Re: [PATCH v2 05/12] firmware: google: framebuf... Tzung-Bi Shih
- [PATCH v2 03/12] firmware: google: framebuffer: Ini... Thomas Zimmermann
- Re: [PATCH v2 03/12] firmware: google: framebuf... Tzung-Bi Shih
- [PATCH v2 10/12] drm/sysfb: Generalize pixel-format... Thomas Zimmermann
- [PATCH v2 01/12] firmware: google: framebuffer: Do ... Thomas Zimmermann
- Re: [PATCH v2 01/12] firmware: google: framebuf... Tzung-Bi Shih
- [PATCH v2 04/12] firmware: google: framebuffer: Tie... Thomas Zimmermann
