From owner-freebsd-wireless@FreeBSD.ORG Mon Mar 19 18:22:32 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDED91065675 for ; Mon, 19 Mar 2012 18:22:32 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 701468FC16 for ; Mon, 19 Mar 2012 18:22:32 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so6323606bkc.13 for ; Mon, 19 Mar 2012 11:22:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id :x-gm-message-state; bh=nSl7Z9iuF4eabJFGTMbDG4Flc3OopQYj+nRNk/tqOF0=; b=phfbXHvDIKfy/7KDcxZ49SQ7NWBWXT+ve9NuaFi9PcrX10w25bypCIlF7vlbujtDh6 CL2iZ4V6zn/ta0NYkAeKfM1ku9Khi/+FO+VA2CV8fr9JgbTvbhs4xPruleh4KYg5jR3E xUlBot7ibXPluqvfGfkXSyZGWUMzaL74LIZyhFqJajFi2Rfva710ObkGGjU3seyopis8 7k136XCKhWy2X01VErMkrmxsCeX3Dfhj1O3h5xLcnQBXejenDT2VScRN6eyW5/AhJ+3x RGdJCnSerHWq9ztkVVLrk+rakBWxj6heJQdqHVxfHVvPJcJfGZ+9vboScryJRPGeXlA1 537w== Received: by 10.204.136.200 with SMTP id s8mr4794402bkt.97.1332181351177; Mon, 19 Mar 2012 11:22:31 -0700 (PDT) Received: from amy.lab.techwires.net (dslb-088-067-222-211.pools.arcor-ip.net. [88.67.222.211]) by mx.google.com with ESMTPS id u14sm27339457bkp.2.2012.03.19.11.22.29 (version=SSLv3 cipher=OTHER); Mon, 19 Mar 2012 11:22:30 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: Kevin Oberman Date: Mon, 19 Mar 2012 19:22:44 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: <201203171232.42515.bschmidt@freebsd.org> <20120319.042250.74754884.iwasaki@jp.FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203191922.44628.bschmidt@freebsd.org> X-Gm-Message-State: ALoCoQk1eaCOA6evR7yadE2HD+bLK88rOSyqMnMs+5fkrN/HGL+/5hIWp3fxjK7lSEkRWhUQXOso Cc: freebsd-wireless@freebsd.org Subject: Re: [patch] iwi(4) suspend/resume broken X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 19 Mar 2012 18:22:33 -0000 On Sunday 18 March 2012 21:42:22 Kevin Oberman wrote: > On Sun, Mar 18, 2012 at 12:22 PM, Mitsuru IWASAKI > wrote: > > Hi, > > > > From: Bernhard Schmidt > >> Well, I came up with attached diff. It works fine on iwn and wpi > >> too basically, wpi has a bit of an issue with the scan after resume, > >> I see probe resquest/response on air but the device doesn't pick > >> em up sometimes.. still debugging. > >> > >> Anyways, I'm pretty sure that if you are doing the same for ipw/iwi > >> it will just work fine. The ieee80211_resume_all/suspend_all calls > >> will ensure that the appropriate stop/init driver functions are called. > > > > Great! I did the same thing for iwi(4), tested several times and it > > works just fine. > > > > Please commit the attached patches if you like it. > > And the patch for iwn. (I don't have a wpi, but I assume that one, as > well. I'd hope it's MFCed for 9.1. I'm beginning to feel a tiny bit > hopeful that I'll be able to susped and resume my laptop again someday > soon. Are there any issue swith suspend/resume on iwn currently? The diff does pretty much the same as what is already in the tree, just the timing/call graph is slightly different. If you're saying that there is an issue then it's just hidden with diff applied. -- Bernhard