WMI: Latest version (v7) was published on the ACPI mailing lists (I finally figured out my problems). This work has been ported to acer_acpi already (and not a moment too soon, since the Aspire 7520 has multiple PNP0C14 devices).
acer-wmi: Initial RFC (request for comment aka first try, please review) has been posted to the ACPI mailing list. For WMID users, they will see no change. For AMW0 v1 users, the Aspire 5020 EC quirks are enabled by default (since all such laptops reported so far have the same quirk). The biggest change for is AMW0 v2 users, who have been switched over to the WMID methods.
I can’t do this in acer_acpi as I suspect, based on earlier reports, that there may be some upstream ACPI bugs we need to flush out to get this working properly, and I can’t backport ACPI bugfixes into acer_acpi.
9 Responses to “WMI & acer-wmi news”
Post A Comment
You must be logged in to post a comment.
December 5th, 2007 at 9:39 pm
Wow, this means that we might get acer_acpi in 2.6.25 ? Great work man, keep it up !! Also, can you give us a link to your post on the ACPI mailing list, so that we can keep up with the updates ?
December 5th, 2007 at 9:43 pm
Not sure. My WMI work has yet to be accepted (and I have a few more changes lined up – mostly addressing comments to try and get acer-wmi to autoload if it’s built as a module).
WMI (v7)
acer-wmi (RFC, v1)
December 5th, 2007 at 11:00 pm
Thank you, now we can keep a track of the progress !!
Let’s hope it’s accepted into upstream kernel 2.6.25 !
December 20th, 2007 at 11:23 pm
Wow, to both of these mailing list posts there have been absolutely no follow-ups yet. Am I impatient or is something happening off the list ?
December 21st, 2007 at 2:57 am
I’m lazy updating. For the most part though, there is no progress to report. I did release some newer versions of the patchset though (Mail Archive is having a heart attack over them though, and completely messes up the ordering – apparently it doesn’t like patches sent from StGit).
A few changes so far, and I’ve also added a port of another WMI out-of-tree driver, tc1100-wmi (after porting it, it went from a few thousand lines of code, to a rather trivial thing of a few hundred).
As for behind the scenes stuff – I did e-mail the Linux ACPI maintainer asking him to please review these patches (about a week ago, I think). He said he would, but still no replies to date.
Current work is experimenting with trying to add rfkill support to acer-wmi, while I wait for more device detection data (besides you, I’ve only had back _one_ other report – maybe I should spam dmesg more – tends to get peoples attention).
December 21st, 2007 at 9:51 am
Aww that’s too bad, I do wish it gets in by 2.6.25
What do you think?
What is rfkill ? Is it used to disable wireless ? But there are already buttons to do that, right ? *scratches head*
Oh and whenever someone loads the module you should have one big huge flashing banner in the terminal that displays
“UNLESS YOU SEND BACK YOUR INFO, THIS MODULE WILL DESTROY YOUR LAPTOP”
or something to the tune of that
December 21st, 2007 at 2:32 pm
rfkill is the kernels backend for handling radio kill switches, like the wireless and bluetooth ones on Acer laptops.
Besides the ‘playing nice’ aspect of using this, AFAIK, there’s another kernel module, rfkill-input, that, when combined with rfkill, should make the wireless and bluetooth buttons ‘just work’ (for those people who bothered to map their keys properly). Although so far I’m struggling to get that working.
November 13th, 2008 at 6:13 am
Hi – How is it possible to enable this?
My CPU Freq Scaling is always at 100% / 1.86Ghz.
Thus battery life on the acer aspire 4315 is poor at best.
November 13th, 2008 at 8:21 pm
On supported Acer machines running recent kernels (2.6.25 and above) then acer-wmi will already be there and running out-of-the-box.
However, this driver has no effect on CPU frequency scaling or battery life – it’s just for enabling & disabling the wireless radio, bluetooth and a few extra addons.