> If I remember correctly, coreboot’s goal to only do minimal hardware > initialization originally meant, that the payload/OS does PCI > initialization.
FWIW, coreboot does do device initialization for things that are only needed by the payload in other cases too: we've been doing display and USB initialization that way for years. This only works in those cases where you need to do a lot of very platform-specific stuff to turn something on, but then after that it presents a very simple generic API (like a framebuffer or standardized host controller interface), but I think PCI also falls in that area. I think it's useful so that payloads don't all need to implement that super SoC-specific stuff individually. In general, I don't think we should be too strict about what coreboot should or shouldn't be in cases where someone just wants to add an optional feature that doesn't introduce a huge maintenance burden on the core framework. If someone doesn't like it they can just disable the Kconfig and do PCI init in the payload / the kernel / via node.js or whatever instead. This has clearly been useful on x86 platforms for years, so I don't see why Arm platforms shouldn't be allowed to do it as well. _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
