From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: eeepc-laptop: bugreport Date: Sun, 15 Nov 2009 16:14:58 +0000 Message-ID: <20091115161458.GA1653@srcf.ucam.org> References: <71cd59b00911140641i1502e95bt81d87db848feaf0@mail.gmail.com> <71cd59b00911150139i5d7377cawda04a17e5e50d05e@mail.gmail.com> <4AFFF7B8.2070508@tuffmail.co.uk> <20091115160201.GC1019@srcf.ucam.org> <4B00283C.3040807@tuffmail.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:51437 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753226AbZKOQOy (ORCPT ); Sun, 15 Nov 2009 11:14:54 -0500 Content-Disposition: inline In-Reply-To: <4B00283C.3040807@tuffmail.co.uk> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alan Jenkins Cc: andrej.gelenberg@udo.edu, Corentin Chary , linux acpi , acpi4asus-user@lists.sourceforge.net On Sun, Nov 15, 2009 at 04:11:40PM +0000, Alan Jenkins wrote: > We don't really look at the device though. What we look at is the value > of WLDG. > > Stray notifications on either of the _other_ 2 pcie ports would then > cause us to toggle them based on WLDG. > > I see a _Lxx handler in my DSDT which looks like it notifies on _all_ > the pcie ports. So I think it's a bit tricky. We could be smarter about that. WLDG is handy but not required - at the most basic level we could do a pci configuration space access and see if we get back 0xff or a value. -- Matthew Garrett | mjg59@srcf.ucam.org