From mboxrd@z Thu Jan 1 00:00:00 1970 From: Holger Macht Subject: Re: CONFIG_IBM_BAY Date: Sun, 18 Mar 2007 19:55:30 +0100 Message-ID: <20070318185529.GA14885@homac2> References: <200703150206.05811.lenb@kernel.org> <20070315133900.GC26862@khazad-dum.debian.net> <20070315080644.c73db24a.kristen.c.accardi@intel.com> <20070315175505.GB6596@khazad-dum.debian.net> <20070315110156.09e80b99.kristen.c.accardi@intel.com> <20070315193123.GB14394@khazad-dum.debian.net> <20070315125037.3e82e0c4.kristen.c.accardi@intel.com> <45FCD062.3050001@gmail.com> <20070318082751.GA28591@homac2> <20070318183652.GB29422@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20070318183652.GB29422@khazad-dum.debian.net> Sender: linux-acpi-owner@vger.kernel.org To: Henrique de Moraes Holschuh Cc: Kristen Carlson Accardi , Len Brown , linux-acpi@vger.kernel.org, ibm-acpi-devel@lists.sourceforge.net, linux-ide@vger.kernel.org List-Id: linux-ide@vger.kernel.org On Sun 18. Mar - 15:36:52, Henrique de Moraes Holschuh wrote: > On Sun, 18 Mar 2007, Holger Macht wrote: > > those ThinkPads where it is needed. Afterwards it does the corresponding > > dock/undock request on ibm_acpi. And this works reliably good what I can > > see from the feedback I already got. But for this to work, userspace would > > It should work with the generic bay device too, but I have no ideas about > dock. But you'll need to deal with udev with the new bay device, something > I am not too happy about. These things are ACPI events, they should remain > so unless all other ACPI events are going to become uevents. It doesn't work, I've already tried. The bay driver only emits an event if you really try to remove the bay, but not on docking/undocking. Regards, Holger