From: Holger Macht <hmacht@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Steven King <sfking@fdwdc.com>,
Tomas Carnecky <tom@dbservice.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after?undocking
Date: Fri, 5 Sep 2008 11:00:13 +0200 [thread overview]
Message-ID: <20080905090013.GC6891@homac> (raw)
In-Reply-To: <20080903212827.GB14620@khazad-dum.debian.net>
On Wed 03. Sep - 18:28:27, Henrique de Moraes Holschuh wrote:
> (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.
Maybe the statement was a little bit harsh, it's just that you won't need
bay in conjunction with libata, because it can't install the notification
handler because that was already done by libata.
Regards,
Holger
next prev parent reply other threads:[~2008-09-05 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 22:35 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 3:17 ` Zhang Rui
2008-09-01 10:50 ` Tomas Carnecky
[not found] ` <48BBC8FC.1020809-ix/z9KG6G0Jl57MIdRCFDg@public.gmane.org>
2008-09-01 11:28 ` Henrique de Moraes Holschuh
2008-09-01 12:16 ` Tomas Carnecky
2008-09-01 18:34 ` Matthew Garrett
2008-09-01 19:05 ` Steven King
[not found] ` <200809011205.05253.sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
2008-09-03 14:45 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after?undocking Holger Macht
2008-09-03 15:04 ` Tomas Carnecky
2008-09-07 22:39 ` Jeremy Fitzhardinge
2008-09-03 21:28 ` Henrique de Moraes Holschuh
2008-09-05 9:00 ` Holger Macht [this message]
2008-09-08 22:17 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 11:34 ` Matthew Garrett
2008-09-01 18:21 ` Steven King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080905090013.GC6891@homac \
--to=hmacht@suse.de \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfking@fdwdc.com \
--cc=tom@dbservice.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox