於 一，2012-01-09 於 22:15 +0000，Carlos Corbacho 提到： > On Monday 09 Jan 2012 18:00:24 joeyli wrote: > > I just checked and found I also have no AMW0_GUID2 machines on my hand, > > now. > > I have some questions about AMW0_GUID2: > > > > + Why we enabled wireless capability in acer-wim if a non-acer machine has > > AMW0_GUID2 ? > > IIRC, there were some bug reports on non-Acer hardware (I don't think this > involved Acer hardware, but this was some time ago...) where the wireless > detection wasn't working with this, but if we forced it on, it worked fine. > Yes, in acer-wmi supported some non-acer machine by quirk and read EC register. That means we need find out EC register reflect to wifi RF state if we are lucky. Unfortunately, direct enable wireless capability causes some non-acer machines' wireless rfkill always disabled. e.g. Lenovo E520 https://bugzilla.redhat.com/show_bug.cgi?id=674353 If we don't check the wireless capability, then they need manually add acer-wmi to backlist. On some lenovo machines, ideapad-laptop driver should support by lenovo's ACPI method. > > + I saw there have some magic number when you access AMW0_GUID1 (e.g. > > 0x9610, eax, ebx, ecx) Could you please kindly teach me how can grab those > > value for AMW0_GUID2? Does there have any useful dump or report log can > > provide by hardware owner? > > Probably not. For AMW0_GUID1, I got the stuff by using the Windows Kernel > Debugger remotely to see what my laptop was doing when changing things in > Windows - unfortunately that relied on a firewire port on the laptop, which I > suspect most people don't have. > Thanks for your teach, but I never used Windows Kernel Debugger, if have good chance, I will try. Most of the state, bug reporter already removed OEM(Acer/Lenovo...) specific Windows and hard to remote debug the machine. > The real problem is that I know almost nothing about AMW0_GUID2 - either what > it's used for or what it actually does, nor how hardware detection works with > it present (if at all). > > -Carlos > I also don't have any information about AMW0_GUID2, almost all modern Acer machine already removed AMW0_GUID2. My humbly request is: Please kindly accept this patch to acer-wmi, it can leave the wireless rfkill state control by BIOS or other platform driver, and don't need manually add acer-wmi to blacklist. Thanks a lot! Joey Lee -- 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
