Date: Fri, 19 Oct 2012 16:34:08 +0200 From: Alberto Villa <avilla@FreeBSD.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-acpi@freebsd.org, Juergen Lock <nox@jelal.kn-bremen.de>, mobile@freebsd.org Subject: Re: Dell acpi_video patch Message-ID: <CAJp7RHZcSWqsRHKjO-_iBj1Pb1thWR1fvan9mwtC5EaARz05qQ@mail.gmail.com> In-Reply-To: <201210181716.31486.jhb@freebsd.org> References: <20121005215316.GA38707@triton8.kn-bremen.de> <201210180858.35282.jhb@freebsd.org> <CAJp7RHZQKsP3LmFFsFA4kaR2w4ZUj_eH_Y-q6=yhRsu2XcnGPw@mail.gmail.com> <201210181716.31486.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 18, 2012 at 11:16 PM, John Baldwin <jhb@freebsd.org> wrote: > Ok, can you possibly hack acpi_video to output the values returned _DOD (in > hex) and the _ADR values (in hex) of your outputs? I've read the ACPI spec and checked my dump, now I see what you mean. Nonetheless, I think you have confused the _STD bit with the _BIOS one: 0x00010100, 0x00010118, 0x00010121 So acpi_video.c behaves just as expected. By the way, the GFX device has a _DOD method too, which returns 0x0400 (an LCD device)... -- Alberto Villa, FreeBSD committer <avilla@FreeBSD.org> http://people.FreeBSD.org/~avilla
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJp7RHZcSWqsRHKjO-_iBj1Pb1thWR1fvan9mwtC5EaARz05qQ>