Hi,

I'm resending this, as SourceForge apparently dropped my reply, after

2011-02-24 15:10:42 1Psbty-0002KY-H9 <= wf...@niif.hu U=wferi P=local S=2175 
id=8762s9bk0t....@tac.ki.iif.hu
2011-02-24 15:10:51 1Psbty-0002KY-H9 => ibm-acpi-devel@lists.sourceforge.net 
R=dnslookup T=remote_smtp H=mx.sourceforge.net [216.34.181.68] 
X=TLS1.0:RSA_AES_256_CBC_SHA1:32 
DN="serialNumber=qX-f4C214rA08JCmMJ0mDr07yxudlxrj,C=US,ST=California,L=Mountain 
View,O=Geeknet\, Inc.,CN=*.sourceforge.net"
2011-02-24 15:10:51 1Psbty-0002KY-H9 Completed

While looking up the mailing list archives, I found the compatibility
table on http://ibm-acpi.sourceforge.net/.  R50e has several question
marks, let's see if I can fill those in:
 video:      see this thread :)
 brightness: works fine, see 
http://sourceforge.net/mailarchive/message.php?msg_id=23972102
             (I only wonder why it's reset to full brightness when I
             quit my X session...)
 volume:     works fine, I think the subtlety mentioned in the last
             message of the above thread is already fixed.  The ALSA
             control readback works fine as well.
 fan:        worked when I tested it some time ago (can retest if needed)

Back to the topic, please find my original reply below.  Not that it's
particularly important...

Thanks,
Feri.

Ferenc Wagner <wf...@niif.hu> writes:

> Henrique de Moraes Holschuh <h...@hmh.eng.br> writes:
>
>> On Wed, 23 Feb 2011, Ferenc Wagner wrote:
>>
>>> at the same time, however, /proc/acpi/ibm/video indicates that only the
>>> lcd (LVDS1) output is active:
>>
>> Ignore that thing entirely.  I think I will just drop it when /proc is gone,
>
> By the time /proc is gone, you won't have anything left to drop under
> it.  :)
>
>> there is no sane sysfs interface for video output switching
>
> Does it make sense to separate it from the graphics driver, btw?
>
>> and it doesn't work right half the time anyway.
>
> Heh, it certainly worked for me some time ago (before the advent of
> KMS).  I didn't test it now, xrandr seems to be the preferred interface
> to video output switching (at least under X).
>
>> It certainly doesn't work at all when combined with xrandr.
>
> OK, so I don't care.  And what's the current best practice for video
> output switching?  Get acpid translate hotkey input events to xrandr
> calls?  Somewhat hairy, as $DISPLAY isn't available, but certainly
> doable.  Or use some separate desktop daemon?  Or mask the key off and
> get the platform firmware do the job?  Or just start up a specialized
> application for doing the switch?
>
> As a side note, acpid gave me some grief lately: when I closed the lid,
> it issued (through Debian's acpi-support package) an xset dpms force off
> command, switching off the VGA monitor, too...  Took some time to find.

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel

Reply via email to