From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <linux-acpi@vger.kernel.org>
Subject: Re: acpiphp makes noise on every lid close/open
Date: Fri, 17 Nov 2006 15:46:27 +0000 [thread overview]
Message-ID: <20061117154627.GA1544@srcf.ucam.org> (raw)
In-Reply-To: <20061117153717.GU14886@vasa.acc.umu.se>
On Fri, Nov 17, 2006 at 04:37:17PM +0100, David Weinehall wrote:
> The fact that the dock starts to beep annoyingly. It has a button that
> you should press before undocking, and wait for a green light to light
> up before removing the laptop. If you remove the computer without
> doing so, the dock starts beeping, and it doesn't stop (AFAIK, haven't
> managed to stand the beeping for more than 30 seconds or so) until you
> replug the laptop.
Ah, hm. Interesting. Maybe it does want OS support, then. Have you tried
it in the Leading Brand OS?
> My guess is that there is some wait to trigger an undock event from
> software as well, and that it would be nice to send that signal to the
> dock before suspending...
You possibly don't want to do that if there's a mounted bay device in
the dock.
We really need to determine some sort of policy when it comes to mounted
devices that will potentially be removed by the user over
suspend/resume. Do we support this configuration (by not killing the
mount point), or do we prevent users from shooting themselves in the
foot?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-11-17 15:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 11:56 acpiphp makes noise on every lid close/open Pavel Machek
2006-11-03 1:54 ` Kristen Carlson Accardi
2006-11-05 23:29 ` David Weinehall
2006-11-06 8:19 ` Stefan Seyfried
2006-11-06 9:21 ` Pavel Machek
2006-11-06 13:29 ` Henrique de Moraes Holschuh
2006-11-06 17:32 ` Tomasz Torcz
2006-11-06 19:13 ` Stefan Seyfried
2006-11-06 19:47 ` Henrique de Moraes Holschuh
2006-11-07 20:44 ` David Weinehall
2006-11-07 21:44 ` Kristen Carlson Accardi
2006-11-17 10:22 ` David Weinehall
2006-11-17 15:13 ` Matthew Garrett
2006-11-17 15:15 ` Pavel Machek
2006-11-17 15:37 ` David Weinehall
2006-11-17 15:46 ` Matthew Garrett [this message]
2006-11-17 16:08 ` David Weinehall
2006-11-17 16:31 ` Matthew Garrett
2006-11-17 18:18 ` David Weinehall
2006-11-17 18:35 ` Matthew Garrett
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=20061117154627.GA1544@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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