Hi Ike, æ åï2011-03-03 æ 11:17 +0800ïIke Panhc æåï > Hi, > > Here[1] is the output of wmidump for ideapad s10-3 and s12-via and there is no > WMI device of ideapad B550 and Y530. > > [1] http://pastebin.ubuntu.com/574793/ > > For now, ideapad-laptop handles the VPC2004 devices that can be found in most of > the ideapads (maybe all, but I can not sure). In my opinion, I do not think to > handle WMI in ideapad-laptop is reasonable unless we have an extra function on > ideapads and we can only control it with WMI driver. > Yes, I just simply check the Ideapad S12's DSDT that was dumped by Ville-Pekka Vaino, it also declare VPC2004 devices in EC block. And, per Vaino's mail, he said ideapad-laptop handle the killswitches better on Ideapad S12. Did you have any plan to add the module alias for all known machines that were support VPC2004 devices? Thank's Joey Lee > On 03/03/2011 05:09 AM, Carlos Corbacho wrote: > > On Wednesday 02 Mar 2011 08:53:55 Joey Lee wrote: > >> æ äï2011-01-03 æ 20:49 +0000ïMatthew Garrett æåï > >> > >>> It looks like this GUID is present in a surprisingly wide range of > >>> devices (eg, http://pastebin.com/8BY0Dg64 from a Vaio...), which means > >>> that it's probably not a safe assumption that reading from the EC will > >>> give us reasonable results. Do the Acer drivers definitely do that, > >>> rather than there being some SMI that returns the data? > >> > >> The AMW0 in acer-wmi not just used by acer machines: > >> > >> #define AMW0_GUID1 "67C3371D-95A3-4C37-BB61-DD47B491DAAB" > >> > >> It was also included in Lenovo Ideapad S12 and Vaio machines' DSDT. For > >> Lenovo Ideapad, that will be better handle by ideapad-laptop driver. > > > > They might not be - Matthew's original question still stands. The old AMW0 was > > just a funny wrapper for direct BIOS calls - maybe we just need a different > > call here? > > > > What does Acer do - are they poking the EC directly, or is the call to AMW0 > > just different for these machines? > > > >> Could we just direct add those model to the blacklist in acer-wmi > >> driver? or we direct check dmi in acer-wmi for only support Acer > >> machines that were included AMW0 in DSDT? > > > > Interesting. If we can't autodetect whether it's a dummy interface or not, > > then, we should change acer-wmi to whitelist what it does support - Acer, > > Fujistu Siemens and Medion - rather than trying to blacklist every vendor that > > crops up. > > > > -Carlos > > -- > > To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
