From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-pci@vger.kernel.org
Subject: Re: Add option to passively listen for PCIE hotplug events
Date: Fri, 14 Nov 2008 17:07:20 +0000 [thread overview]
Message-ID: <491DB048.3090308@tuffmail.co.uk> (raw)
In-Reply-To: <20081114161631.GA28234@srcf.ucam.org>
Matthew Garrett wrote:
> On Sun, Nov 09, 2008 at 04:08:54PM +0000, Alan Jenkins wrote:
>
>
>> Bump. In case you're still slightly confused, I've found out why. It
>> skips the slot power check because POWER_CTRL(ctrl) == 0. (See "Power
>> Controller" in the debug output below).
>>
>
> Ok. I'm beginning to think that this approach is misguided. The Aspire
> One should be handled by the acpiphp changes I've posted. The Eee makes
> significantly less sense to me. It runs XP, so it can't depend on native
> PCIe hotplugging. It sends ACPI notifications when the kill state
> changes but there's no topological relationship between the device that
> receives them and the device that needs to be hotplugged.
>
> What I'm actually beginning to suspect is that this should be handled by
> eee-laptop. Can you give the following patch a go, without any pciehp
> code loaded?
>
>
Will do.
Note that Xandros say the newest model EeePC (S101) 'is now using a
"normal" kill of the antenna, which is easier to work with'.
http://sourceforge.net/mailarchive/message.php?msg_name=48D6AC5E.70502%40xandros.com
So if you're unlucky, the current eeepc-laptop worked perfectly on the
S101, and now it will simply refuse to load :). But it's probably safer
that way. At least the 701 runs quite adequately without eeepc-laptop.
I guess it can be fixed when someone interested gets their hands on an S101.
Thanks
Alan
next prev parent reply other threads:[~2008-11-14 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bspwK-420-11@gated-at.bofh.it>
[not found] ` <bujnh-2fr-5@gated-at.bofh.it>
[not found] ` <bujwT-2Ew-5@gated-at.bofh.it>
[not found] ` <buml1-6du-3@gated-at.bofh.it>
2008-11-04 11:29 ` Add option to passively listen for PCIE hotplug events Alan Jenkins
2008-11-04 12:47 ` Matthew Garrett
2008-11-04 13:32 ` Matthew Garrett
2008-11-04 14:26 ` Alan Jenkins
2008-11-04 14:33 ` Matthew Garrett
2008-11-04 15:01 ` Alan Jenkins
2008-11-04 15:11 ` Matthew Garrett
2008-11-04 15:44 ` Alan Jenkins
2008-11-04 15:57 ` Matthew Garrett
2008-11-04 16:22 ` Alan Jenkins
2008-11-09 16:08 ` Alan Jenkins
2008-11-12 23:34 ` Matthew Garrett
2008-11-14 16:16 ` Matthew Garrett
2008-11-14 17:07 ` Alan Jenkins [this message]
2008-11-14 17:12 ` Matthew Garrett
2008-11-14 17:27 ` Alan Jenkins
2008-11-14 17: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=491DB048.3090308@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.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