On Sun, 07 Jun 2009, Marcel Holtmann wrote: > > I don't think we should expect userspace to know whether or not a device > > has a persistent state. Yes, it _could_ maintain whitelists, but why > > should it have to if the driver already knows? > > If you want that, then the best approach seems an extra sysfs attribute > for this. It is not intrusive on the event API and lets udev etc. have > these information, too. I have no problems with either approach. As long as the information of which devices have restored their initial state from NVS is available to userspace, it is enough. Do note that this information also needs to be available for resume (state should be checkpointed to NVS on sleep, and restored from NVS on resume. I believe tpacpi does this, but if it doesn't, I will fix it eventually). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
