On Fri, 07 Dec 2007, Thomas Renninger wrote: > I see the "danger" of applications misusing this as an interface and > implementing workarounds for unsupported ACPI parts and (this is the > real problem) stop working on the real problems or a proper > implementation. Exactly. Or causing shadow issues that are hell to debug... unless this this EC register interface taints the kernel the first time it is used for reads OR writes... > Especially because this option should be compiled in e.g. OpenSUSE > versions, for better remote debugging (comparing EC register values with > DSDT Embedded Controller variable implementations on a related problem > could help a lot, without the need of digging in the dark for weeks...). If it is something you can tell users to load explictly (load the "ec_debug" module, with the parameter "yes_dammit_do_load_it=1") or somesuch, maybe. > >From your comments above, I read out that you tend to accept such an > interface as suggested by Alexey? > Making it read-only by default, would mainly help debugging purposes and > should avoid any workaround implementations. Read-only is *much* better than read-write, but it is NOT completely safe. IMO, it would still need to be something that requires the user to explicitly enable. It can't just sit there active by default. It'd have to be something through which a stray open() or stat() wouldn't cause EC I/O. -- "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-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
