lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491DB048.3090308@tuffmail.co.uk>
Date:	Fri, 14 Nov 2008 17:07:20 +0000
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-pci@...r.kernel.org
Subject: Re: Add option to passively listen for PCIE hotplug events

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
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ