On Tue, 15 Apr 2025, Lee Jones wrote:
> On Tue, 08 Apr 2025, Mario Limonciello wrote:
>
>> From: Mario Limonciello
>>
>> Currently userspace software systemd treats `brightness` and
>> `actual_brightness` identically due to a bug found in an out of tree
>> driver.
>>
>> This however causes prob
On Tue, 15 Apr 2025, Mario Limonciello wrote:
> On 4/15/2025 10:53 AM, Lee Jones wrote:
> > On Tue, 08 Apr 2025, Mario Limonciello wrote:
> >
> > > From: Mario Limonciello
> > >
> > > Currently userspace software systemd treats `brightness` and
> > > `actual_brightness` identically due to a bug
On 4/15/2025 10:53 AM, Lee Jones wrote:
On Tue, 08 Apr 2025, Mario Limonciello wrote:
From: Mario Limonciello
Currently userspace software systemd treats `brightness` and
`actual_brightness` identically due to a bug found in an out of tree
driver.
This however causes problems for in-tree dri
On Tue, 08 Apr 2025, Mario Limonciello wrote:
> From: Mario Limonciello
>
> Currently userspace software systemd treats `brightness` and
> `actual_brightness` identically due to a bug found in an out of tree
> driver.
>
> This however causes problems for in-tree drivers that use brightness
> to
From: Mario Limonciello
Currently userspace software systemd treats `brightness` and
`actual_brightness` identically due to a bug found in an out of tree
driver.
This however causes problems for in-tree drivers that use brightness
to report user requested `brightness` and `actual_brightness` to
