On Tue, 2006-10-31 at 10:46 +0100, Nicolas DET wrote: > Benjamin Herrenschmidt wrote: > >> Ok. that's why I suggest to keep buggy (or none) firmware board in > >> platform specific code. > > > > Well, in that case, we have a well defined interface to set the sense > > code, via the device-tree, and that's much better than having platform > > code muck around the PIC hardware separately from the PIC driver don't > > you think ? > > > > Anyway, that's the way it works in Linux/powerpc so there is no need > > debating that for ever. Just be aware that at one point, there will be a > > set_type() implementation in this driver and that it will be called > > based on the polarity information in the device-tree so make sure you > > got it right. > > > > Ok. set_type() is scheduled for later on or should it be included right now? > What's next should be done to finally acked the driver?
Post the latest one and we'll see.. Ben _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
