linux-kernel - Re: [PATCH 3/4] dell-wmi: Add information about other WMI event codes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Jun 2016 16:12:39 +0200
From:	Pali Rohár <pali.rohar@...il.com>
To:	Mario_Limonciello@...l.com
Cc:	gabriele.mzt@...il.com, mjg59@...f.ucam.org, dvhart@...radead.org,
	kernel@...pniu.pl, luto@...nel.org, alex.hung@...onical.com,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] dell-wmi: Add information about other WMI event codes

On Wednesday 22 June 2016 13:40:57 Mario_Limonciello@...l.com wrote:
> > > You aren't seeing this on the DSDT of your Latitude right?
> > 
> > Yes, I do not see it on Latitude.
> 
> Thanks, the usage of this scan code is specific to consumer BIOSes.
> 
> > 
> > > Gabriele,
> > >
> > > Your machine is from the year before XPS switched over to running the
> > > Dell business client (eg Latitude, Precision, Optiplex) BIOS.
> > >
> > > The EC in that machine does have support for "Battery Health" via that
> > > scancode.  On Windows it's used for relaying battery information to an
> > > application called Quick Set.
> > 
> > Do you have some details when it is send to OS? And how to read that that
> > "battery health"?
> 
> When a battery is removed or inserted this event is supposed to be received
> by quickset over WMI and then Quickset will re-read battery information.

So event is sent only if battery is removed or inserted?

> For Linux I don’t think this is necessary and a NOOP is appropriate.
> 
> There is also a second place that some older laptops had a battery "hotkey"
> that would also emit 0xE00E.  This was also picked up by quickset and would
> show battery information.
> 
> This shouldn't be blocked by kernel, I'd expect if someone wants to bind this
> to another application from userspace they should be able to.

Great! Can I send patch after which 0xe00e will be send to input layer as
event KEY_BATTERY?

-- 
Pali Rohár
pali.rohar@...il.com