On Mon, Nov 23, 2009 at 5:24 PM, Len Brown <lenb@xxxxxxxxxx> wrote: > On Sat, 21 Nov 2009, Matthew Garrett wrote: > >> On Sat, Nov 21, 2009 at 10:22:45PM +0100, Corentin Chary wrote: >> >> > I think we could add that patch to 2.6.32, then revert it in 2.6.33 (or later) >> > when a eeepc-wmi driver (or wmi support inside eeepc-laptop) is available. >> > And I don't think such a driver (patch) will be available before 2.6.32. >> > >> > That means that owner of 1000h and 1005ha won't be able to use eeepc-laptop >> > (camera, rfkill, hotkeys) without adding acpi_osi="Linux" manually in 2.6.32. >> > >> > I know this is not a long term solution. >> >> The reason I'm not keen is that hardware vendors seem to continue >> believing that Linux claims to be Linux - it's almost understandable for >> Asus when they're shipping 2.6.remotely_exploitable on their hardware, >> but Lenovo are still doing it for no obvious reason. I'm worried that >> even doing a single release with this defined will result in Asus >> pulling the same trick at some point in the future. > > I agree with Matthew that this is distasteful -- particularly > since the models in question came out well after upstream Linux > stopped setting OSI(Linux) (2.6.32). > > However, I think the fact that this DMI is specific to the 1000h and > 1005ha makes it less scary. I added 1000h and 1005h because I only get reports for these, but I think this will affect all models with Windows 7 support :/ I'm currently trying to get the hardware, but don't think I can get it before 2.6.32 release... -- Corentin Chary http://xf.iksaif.net -- 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
