> IDK. My take would have been to provide the coreboot table under > /sys/firmware; similar to DT. And then walk over it and create devices > for the known entries.
We have established userspace infrastructure relying on the current sysfs layout (at least the `cbmem-XXXXXXXX` nodes), so while you may be right that there may have been better approaches to do this to begin with, I would much prefer if we can stick with what's there now. > I have a new iteration of the series that creates a coreboot-framebuffer > platform device for at the same place that currently creates the > simple-framebuffer device (in framebuffer_probe()). So we can leave most > of the code it as. There are also a number of bugs that this is going to > fix. I'll post it soon. Sounds good, thanks!
