Grant Likely wrote: > On 10/25/07, Valentine Barshak <[EMAIL PROTECTED]> wrote: > > If it doesn't, it can be added during prom_init.c We're already doing > a bunch of efika fixups there anyway.
I want those to go away. Far, far away. http://www.powerdeveloper.org/platforms/efika/devicetree Not the most elegant solution right now, but it works (kinda, a few bugs to sort out). Note that Domen's ethernet driver plus a bunch of Sylvain's stuff if it is ever cleaned up (deep sleep etc.) will not work without these device tree changes. You should realise that if we plugged every tiny thing into prom_init.c we would double the size of the file just for Efika fixes. And that's dumb. Compatibility with old device trees should go away after there is a production firmware people can download - like the x86 hardware monitor drivers in lmsensors report "please upgrade your BIOS" if they have been disabled, users will happily update their BIOS to an updated version if it is available. For Efika, right now, it is not. And for Efika, right now, I fear the stupidity some of the device tree design (mandated by a text file..) means any new firmware update will have far more strings and reporting than it should ever truly need. Although you can restrict Linux kernels from running on firmwares below a certain version, we can't knowingly restrict the board firmware to only running Linux kernels above a certain version. Therefore, this is an exercise in not pissing people off, not really of any technical merit. We already had Pegasos keyboard support disappear because someone decided the device tree usage needed to be changed. Given the size of the fix in nvramrc, it's harmless, given that Pegasos is a dead platform, it's harmless. Efika is still in production. -- Matt Sealey <[EMAIL PROTECTED]> Genesi, Manager, Developer Relations _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev