[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080903212827.GB14620@khazad-dum.debian.net>
Date: Wed, 3 Sep 2008 18:28:27 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Steven King <sfking@...dc.com>, Tomas Carnecky <tom@...ervice.com>,
Zhang Rui <rui.zhang@...el.com>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, ibm-acpi-devel@...ts.sourceforge.net
Subject: Re: 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume
after?undocking
(Holger dropped from CC/To as requested by the mail-followup-to header).
On Wed, 03 Sep 2008, Holger Macht wrote:
> On Mon 01. Sep - 12:05:04, Steven King wrote:
> > On Monday 01 September 2008 5:16:44 Tomas Carnecky wrote:
> >
> > > I just tested suspend/resume with the CDROM drive removed (an empty
> > > bay). Suspend/resume now works just fine, regardless how I dock/undock
> > > the laptop.
> >
> > I'm seeing the exact same things as Tom. Also, in my dmesg I see:
> >
> > ACPI: \_SB_.PCI0.IDE0.PRIM.MSTR: found ejectable bay
> > ACPI: \_SB_.PCI0.IDE0.PRIM.MSTR: Adding notify handler
> > ACPI: Error installing bay notify handler
> >
> > is this significant?
>
> No, it's not. Bay driver is obsolete with 2.6.26's libata hotplug code.
Hardly so. We need to be able to query state and command the bay from
userspace. We need to support non-libata devices. We don't need, but want,
notifications that can be easily flagged by userspace as being related to
bay/dock ejections and insertions (for OSD).
What makes bay obsolete is the rework on the dock driver that adds all bay
functionality to dock.c... and that ain't even on 2.6.27, AFAIK.
--
"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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists