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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140315160545.GA6689@amd.pavel.ucw.cz>
Date:	Sat, 15 Mar 2014 17:05:45 +0100
From:	Pavel Machek <pavel@....cz>
To:	Lan Tianyu <tianyu.lan@...el.com>
Cc:	Stefan Lippers-Hollmann <s.L-H@....de>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Ilia Mirkin <imirkin@...m.mit.edu>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 3.14-rc: /proc/acpi/battery gone?

Hi!

> >>>They have attempted to use the sysfs api, but apparently that
> >>>integration was done with an older version of that API. There's also
> >>>some attempt to get it to work with upower, but I couldn't figure out
> >>>how to make that work either on my (up-to-date gentoo) box. (TBH I
> >>>didn't spend more than an hour or two on it, so it may not be
> >>>impossible.)
> >>
> >>Tianyu, can you please have a look at this?
> >
> >Disclaimer, I've never used wmbattery so far.
> >
> >The current upstream version (2.42, released in early december 2013)
> >of wmbattery[1] no longer reads from /proc/acpi/ at all. Apparently
> >it changed to using upower by default, with non-default fall-backs for
> >reading from sysfs.
> >
> >The only change required for building upower with wmbattery 2.42
> >appears to be a new build-dependency on libupower-glib-dev (at least
> >on Debian, built from the upower source package). Given that this
> >version is present in Debian testing and unstable, I'd assume that it's
> >supposed to work using upower, although I haven't confirmed that myself.
> >
> >Judging from the Gentoo ebuild, you probably just have to add
> >"sys-power/upower" to the RDEPEND variable and make sure to build
> >wmbattery 2.42; this is untested.
> >
> 
> Hi Stefan:
> 	I just glance wmbattery code. I find the code in the acpi.c is
> already using the new sysfs battery interfaces, right?
> 
> ...
> 
> #define SYSFS_PATH "/sys/class/power_supply"
> 
> ...
> char *acpi_labels[] = {
> 	"uevent",
> 	"status",
> 	"BAT",
> 	"AC",
> 	"POWER_SUPPLY_CAPACITY=",
> 	"POWER_SUPPLY_??????_FULL_DESIGN=", /* CHARGE or ENERGY */
> 	"POWER_SUPPLY_PRESENT=",
> 	"POWER_SUPPLY_??????_NOW=",
> 	"POWER_SUPPLY_CURRENT_NOW=",
> 	"POWER_SUPPLY_STATUS=",
> #if ACPI_THERMAL
> 	"thermal_zone",
> #endif
> 	"POWER_SUPPLY_ONLINE=",
> 	"POWER_SUPPLY_??????_FULL=",
> 	NULL
> };

New kernel should work with old userspace... and clearly it does not.

Do you have test patch for a revert?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ