Hi Am 15.01.26 um 21:54 schrieb Julius Werner:
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?
Corebootdrm already depends on the CONFIG_GOOGLE_FRAMEBUFFER, which is standard behavior for all kernel drivers (i.e., drivers depending on architectural options). Having dependencies in the other direction creates a circular dependency, which Kconfig doesn't handle. But generally speaking, what's the point of having that framebuffer backend code then? I tried to remove it, but it is supposed to remain. But it would not serve a purpose other than creating the platform device for the actual driver. I'm confused about the reason for this design.
Best regards Thomas -- -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
