[systemd-bugs] [Bug 90689] New: [PATCH] Add support for alienware gfx amplifier

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90689

            Bug ID: 90689
           Summary: [PATCH] Add support for alienware gfx amplifier
           Product: systemd
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
          Assignee: systemd-bugs at lists.freedesktop.org
          Reporter: mario_limonciello at dell.com
        QA Contact: systemd-bugs at lists.freedesktop.org

Created attachment 116105
  --> https://bugs.freedesktop.org/attachment.cgi?id=116105&action=edit
patch adding these keycodes

Some Alienware notebooks and desktops support an external graphics
housing called the "Alienware Graphics Amplifier". It allows the usage
of a larger or more modern graphics card than your gaming PC would
already support.  In order to provide a good experience, systems that
support it can provide notification to the OS via the scancodes on the
the keyboard controller of events related to the cable.

The following 4 events are supported (and the presumed OS response):
* Cable plugged in (An app on the existing display or terminal would
tell the user to reboot the system to activate)
* Undock cable pressed (An app would let the user know to reboot the
system to complete undock process; also when supported by GFX driver,
driver can clean up and work without a reboot)
* Surprise removal of cable (System reboots).

For the cable plug events I've mapped over to prog1/prog2.  If there is a
better option for these, please adjust accordingly.

The surprise removal of the cable causes the GPU drivers to get in a very bad
state.  X continues to run,  but plugging the cable back in or restarting X to
use a different GPU doesn't fix it.
You can't tell the user to save their game status or anything else useful, so
it makes most sense to reboot or shutdown the machine.

I'm submitting a separate patch for the system reboot directly to the kernel
via an i8042 filter.  In the event this is running on a kernel without that
patch, sending KEY_POWER is the next best thing as it would shutdown if the
system DE was configured to do this.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150528/4c6a4b1d/attachment.html>