On Thu, 16 Sep 2010, Matthew Garrett wrote: > On Wed, Sep 08, 2010 at 09:21:03AM +0200, Robert de Rooy wrote: > > FYI, these newer series 3 "docks" no longer register themselves as a > > dock through ACPI. Instead they function more like port replicators. > > As such I think the HKEY event is just a way to detect a dock/undock > > event which can be used to trigger things like re-configuring the displays. > > Hm. We may want to create a proper dock class in the kernel to handle > this. HPs do something similar. If all the state we need to convey is "docked" and "undocked", EV_SW input events are enough. Otherwise, yes, a dock class would be welcome, with associated uevents (and the uevents should convey the docked/undocked information in-band). Maybe also generating the EV_SW. A dock class would let us have the devices inside the dock (or bay) represented through symlinks, which is quite convenient. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
