Date: Mon, 29 Feb 2016 09:45:15 -0800 From: Tom Sparks <tom@ycombinator.com> To: Alexandr Matveev <timon@timon.net.nz> Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI Dock/Undock events? Message-ID: <CABLy0qQO2U9nMZi0V7iiwW88ZOgAG=T4Qcyj50bVG2_K45hhdw@mail.gmail.com> In-Reply-To: <56D1514A.3060909@timon.net.nz> References: <CABLy0qT=qCaPnkbP8CP5acm6cQLP7tAU0pxMWLm2S9%2BLH6R4aQ@mail.gmail.com> <56D1514A.3060909@timon.net.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Sadly, that module doesn't seem to work with my system. --- snip --- # kldstat |grep dock 17 1 0xffffffff81d02000 20da acpi_dock.ko # sysctl sysctl dev.acpi_dock.0.status sysctl: unknown oid 'dev.acpi_dock.0.status' --- snip --- I am running 10.2-STABLE on a Thinkpad T520 with a standard dock. I have a T530 with -HEAD on it, I'll try there too. On Fri, Feb 26, 2016 at 11:33 PM, Alexandr Matveev <timon@timon.net.nz> wrote: > On 26.02.2016 23:37, Tom Sparks wrote: > > I'm trying to find information about whether acpi_ibm has info on > > dock/undock events or status; It looks like the answer is no. > > This would be pretty handy to have available. > > > > Before I start trying to figure out how to add this, just wanted to check > > and see if anyone else had worked on this. > > > Hello, > > Look at acpi_dock kernel module > > # kldload acpi_dock > $ sysctl dev.acpi_dock.0.status > dev.acpi_dock.0.status: 0 > > $ egrep 'define.*STATUS' /usr/src/sys/dev/acpica/acpi_dock.c > #define ACPI_DOCK_STATUS_UNKNOWN -1 > #define ACPI_DOCK_STATUS_UNDOCKED 0 > #define ACPI_DOCK_STATUS_DOCKED 1 > > -- > Aleksandr Matveev > > -- Tom Sparks Systems Engineer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABLy0qQO2U9nMZi0V7iiwW88ZOgAG=T4Qcyj50bVG2_K45hhdw>