![]() | |||||||||||||
Messages in this thread |
On Thu, 5 Feb 2004, Benjamin Herrenschmidt wrote: > > I don't quite agree... There are cases for example (USB, Firewire) where > we could construct an OF path to be used by the bootloader setup without > having the OF information in the first place (for devices that weren't > plugged during boot typically). I do no intend to go that way for 2.6 > though. Ok. Fair enough. I think that I personally would be a lot happier with the situation if it wasn't that PCI had magic knowledge about OF in particular. In other words, you'd likely be able to sell me on an idea where the PCI layer just knows about "let the firmware install a few files here", but is totally firmware-agnostic per se. In other words, you migth just rename the "OF" functionality as "platform" functionality, and add dummy (empty) platform handlers for the other platforms (eg BIOS/EFI whatever). Maybe some day EFI will want to have a similar pointer.. So while I'd hate to have the PCI layer start having to learn details of all the platforms out there, I don't think it's necessarily wrong that the PCI layer knows about the _concept_ of a platform, as long as it doesn't get too specific. Would that suit your needs? Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 14:00 [W:0.356 / U:0.040 seconds] ©2003-2008 Jasper Spaans | |||||||||||||