From: Stefan Seyfried <seife@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: 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: Mon, 6 Nov 2006 20:13:51 +0100 [thread overview]
Message-ID: <20061106191351.GA1642@suse.de> (raw)
In-Reply-To: <20061106132903.GA25257@khazad-dum.debian.net>
On Mon, Nov 06, 2006 at 11:29:03AM -0200, Henrique de Moraes Holschuh wrote:
> > > > There is a bug here in that acpiphp shouldn't even be used on the X60 -
> > > > it has no hotpluggable slots.
>
> What about the internal mini PCI express slots (where the Intel 3945ABG
> device and EVDO wwwan cards are plugged)?
These are not in the media bay. I'd also guess that they are not
hotpluggable.
> Also, ThinkWiki lists this machine as one that has a CardBus slot. A photo
The cardbus slot is also not in the media bay and AFAIK not handled by
acpiphp.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
next prev parent reply other threads:[~2006-11-06 19:14 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 [this message]
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
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=20061106191351.GA1642@suse.de \
--to=seife@suse.de \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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