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: <200809061120.00224.arvidjaar@mail.ru>
Date:	Sat, 6 Sep 2008 11:19:59 +0400
From:	Andrey Borzenkov <arvidjaar@...l.ru>
To:	toshiba_acpi@...ebeam.org
Cc:	linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: ACPI video.c brightness handler conflicts with toshiba_acpi

On Saturday 06 September 2008, Andrey Borzenkov wrote:
> I have now two different devices that refer to the same hardware:
> 
> lrwxrwxrwx 1 root root 0 2008-09-06 11:04 acpi_video0 -> ../../devices/virtual/backlight/acpi_video0/
> lrwxrwxrwx 1 root root 0 2008-09-06 11:04 toshiba -> ../../devices/virtual/backlight/toshiba/
> 
> Unfortunately, due to ACPI implementation the acpi_video0 one is much
> inferior (as it provides only effectively two levels instead of 8);
> and user level tools are apparently quite confused which one to select.
> 
> Is there any mechanism that would allow tochiba_acpi to claim brightness
> for internal LCD screen that video would not attempt to grab it too?
> 
> Of course manually disabling brightness handling in video is always possible,

Actually it is not. brightness_switch_enabled only disables event handling;
it still resets actual brightness on loading and creates sysfs files to
confuse user space.

> still is nice for this to be handled automatically.
> 



Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ