svn commit: r360025 - head/sys/dev/acpica

[Warner Losh]

On Fri, Apr 17, 2020 at 9:54 AM Colin Percival <cperciva at freebsd.org> wrote:

> On 2020-04-16 23:26, Alexey Dokuchaev wrote:
> > On Thu, Apr 16, 2020 at 03:12:15PM -0700, Colin Percival wrote:
> >> On 2020-04-16 15:05, Oliver Pinter wrote:
> >>> On Thursday, April 16, 2020, Colin Percival <cperciva at freebsd.org
> >>> <mailto:cperciva at freebsd.org>> wrote:
> >>>     Log:
> >>>       Alert devd when acpi_video brightness changes
> >>>
> >>> Please add this to release notes!
> >>
> >> I considered that, but so far I don't have any evidence that other
> >> systems exist with the same half-working ACPI.  Unless you're aware of
> >> people who are seeing the same "hw.apci.video.lcd0.brightness changes
> >> but thebacklight doesn't" syndrome?
> >
> > So this is more like a work-around for the problem which lies elsewhere:
> > something is missing in acpi_video(4) or perhaps we need a (nonexistent)
> > acpi_dell(4)?  In this case, shouldn't it be disabled by default, or at
> > least be toggable since as you say, evidently just a minority of systems
> > exist with the same half-working ACPI?
>
> Having occasional extra messages coming through devctl(4) is harmless; by
> default devd will just drop them on the floor since there isn't anything
> configured to do with them.
>
> In an upcoming change to the graphics/intel-backlight port (if/when someone
> merges my patch into their github repo...) I'll be providing a
> configuration
> file which can be copied into /usr/local/etc/devd/ in order to hook these
> messages up to the intel-backlight utility.
>
> So... yes, for practical purposes this is disabled by default.
>

There's no harm to these, so I agree... there may also be some novel uses :)

Warner


> --
> Colin Percival
> Security Officer Emeritus, FreeBSD | The power to serve
> Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
>