Please disregard my message below, sorry for the noise.
The facts are wrong, I'm still having those plug/unplug brightness
jumps. (no idea what coincidence took place yesterday.)
Sorry, Marcus
mcmer-open...@tor.at (Marcus MERIGHI), 2015.12.20 (Sun) 16:04 (CET):
> I am somewhat confused; there we
I am somewhat confused; there were two recent changes that might cause
the improvement:
- tedu@ 2015-12-16 acpi/dsdt.c
- kettenis@ 2015-12-17 acpi/acpithinkpad.c
since tedu@s commit was inspired by kettenis@ I reply to this thread.
mark.kette...@xs4all.nl (Mark Kettenis), 2015.12.16 (Wed) 19
> From: Christian Weisgerber
> Date: Thu, 17 Dec 2015 11:50:53 + (UTC)
>
> On 2015-12-16, Mark Kettenis wrote:
>
> > The downside of this diff is that number of levels is limited to 16
> > whereas we currently have much finer granularity. But I think that is
> > acceptable. The levels are
On 2015-12-16, Mark Kettenis wrote:
> The downside of this diff is that number of levels is limited to 16
> whereas we currently have much finer granularity. But I think that is
> acceptable. The levels are probably better calibrated and we now have
> proper coordination between the OS and the
On Wed, Dec 16, 2015 at 07:48:23PM +0100, Mark Kettenis wrote:
> Most, if not all, somewhat recent Thinkpads have some subtle issues
> with display brightness control. For example,if you change the
> display brightness using wsconsctl(8) or cbacklight(1), and later use
> the brightness control but
Most, if not all, somewhat recent Thinkpads have some subtle issues
with display brightness control. For example,if you change the
display brightness using wsconsctl(8) or cbacklight(1), and later use
the brightness control buttons on the keyboard, you're likely to see a
big jump in brightness. o
