From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 17:05:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 929557C6 for ; Sat, 12 Jan 2013 17:05:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1A596B3 for ; Sat, 12 Jan 2013 17:05:43 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id hn14so452763wib.3 for ; Sat, 12 Jan 2013 09:05:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6aQ9gDvxtNu7gaEtqxwBP54BVNJf2ev3JhRTzL/SN+Y=; b=TKC4+a7J2egiORLdMUN+J0kSouMuxj6yla+NzzAVIDN1aXtxCbAhxQ7e8tQ53etHiB 0DmUyCRLJMunTKGDDA3j+SOCujDGqZMx3VZ4Iw/d+jdfrYeiShopZCKkRT6Xptld5daw PxTB+MSE4ppPbbmAzLqCGqYHuL/c5TFFfpzEPwtC8JAy/roQxupSz95Urm8wyKuPcKSH Ut/Z26tiw6RfVUHc5q4XFnnb0xOPalxeKvjK9idOzodYYhD4M4kreJrjOfX1ynnOfzwf hSF2PUwpmov0NU7H6mzatYsPdOy8lvJ9u5IT4YGrEzZ7u5r0rhbKXTjM8IxZljf8E+/x RakQ== MIME-Version: 1.0 X-Received: by 10.180.72.146 with SMTP id d18mr4570590wiv.33.1358010337148; Sat, 12 Jan 2013 09:05:37 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 09:05:37 -0800 (PST) In-Reply-To: <20130112170707.GL67643@zxy.spb.ru> References: <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 09:05:37 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2013 17:05:44 -0000 We can't patch pci space if they're all 0xffffffff, that means nothing is there. That's the point; the card hasn't come back on from suspend. So we need to do something _before_ it suspends. We can't do anything to the card after it resumes; we can only do stuff to the PCI bus. Adrian On 12 January 2013 09:07, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote: > >> I don't know the first thing about ACPI, I'm sorry. > > OK, what about "patching" pci config space? Remove indication of > support D3 state? or system don't suspend after this complete? > (sorry for dumb question). > >> Perhaps ask on the freebsd acpi list? >> >> >> >> Adrian >> >> On 12 January 2013 08:52, Slawa Olhovchenkov wrote: >> > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: >> > >> >> On 12 January 2013 08:37, Slawa Olhovchenkov wrote: >> >> > On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote: >> >> > >> >> >> .. right, try flipping the rf kill switch off/on after suspend, dump >> >> >> the config registers. >> >> > >> >> > don't react -- 255 times 'ff' >> >> >> >> Okay. Well, I'll see if there's anything that I can do with the PCI >> >> glue inside the AR9220, but if it's broken under Windows... >> > >> > Perhaps if ACPI not found vendor wifi card (intel) not powered slot on >> > resume? I am don't know how chek this is acpidump...