On 1/11/07, Stefan Reinauer <[EMAIL PROTECTED]> wrote:
This works fine for just passing the device tree, but it will fail for the next step of being able to use the firmware in the OS, and returning sanely to the firmware.
And why is it we need to do that, presently? And how, in a virtualized environment, for example, would you plan to support this calling into firmware? (I sort of know how IBM does it, I am wondering how OFW would plan to do it). We can standardize passing a device tree structure across a very wide range of environments. But supporting callbacks is necessarily going to be a much smaller range of environments. It sounds, however, like it will be possible to do both the callback and non-callback cases, so I think I'm fine with that anyway. I will wait for Segher's patch. thanks ron - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
