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 avi...@freebsd.org
http://people.FreeBSD.org
;f=include/acpi/video.h;h=61109f2609fc3ee446ec43e242875b28ae719344;hb=HEAD
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=drivers/acpi/video.c;h=f94d4c818fc74dc9a076e8f67fe98d7bc6620a61;hb=HEAD
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org
_DOD and _ADR you were probably talking about). Or
am I missing the point?
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org/~avilla
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
, it wasn't about my laptop, but a general consideration; also
spec 5.0 lists only 0x0110, so it's better to stick to the spec as you
say. By the way, I think the name of devices is not used anywhere
(apart for an X.Org piece of code which I'm going to patch), so it's
not important.
--
Alberto Villa, FreeBSD
On Sat, Oct 20, 2012 at 12:21 AM, Alberto Villa avi...@freebsd.org wrote:
I know, I was saying that you probably confused bit 31 with bit 16, so
the patch you proposed (about bit 31 being set in _DOD but not in
_ADR) was not correct. ;)
You assumption, actually. The patch you committed
: 1
hw.acpi.video.out1.active: 1
hw.acpi.video.out1.brightness: 100
hw.acpi.video.out1.fullpower: 100
hw.acpi.video.out1.economy: 50
hw.acpi.video.out1.levels: 100 50 0 10 20 30 40 50 60 70 80 90 100
hw.acpi.video.out2.active: 1
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http
On Mon, Oct 15, 2012 at 5:12 PM, John Baldwin j...@freebsd.org wrote:
Interesting. Can you get an acpidump?
Sure:
http://people.FreeBSD.org/~avilla/files/avilla.asl.gz
I'd be glad to solve my problems with ACPI!
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org
them recognised
correctly, or is it fault of a buggy ACPI table?
--
Alberto Villa, FreeBSD committer avi...@freebsd.org
http://people.FreeBSD.org/~avilla
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
