netdev - Re: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and connecting

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 PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Aug 2014 17:47:58 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	"Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>, brudley@...adcom.com,
	Franky Lin <frankyl@...adcom.com>, meuleman@...adcom.com,
	linville@...driver.com, pieterpg@...adcom.com, dekim@...adcom.com,
	mcgrof@...not-panic.com, antonio@...n-mesh.com,
	johannes.berg@...el.com, linux-wireless@...r.kernel.org,
	brcm80211-dev-list@...adcom.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org
Subject: Re: [PATCH] brcmfmac: prevent watchdog from interfering with
	scanning and connecting

On Thu, Jun 19, 2014 at 06:37:56PM +0200, Arend van Spriel wrote:
> On 19-06-14 18:28, Fu, Zhonghui wrote:
>> I have tried brcmfmac driver with "CONFIG_PM_RUNTIME is not set", and scanning and connecting  always succeeded. This means that CONFIG_PM_RUNTIME should not be set if we use SDIO WiFi device driven by brcmfmac driver, right?
>
> Depends which kernel you are using. In 3.16-rc1 the sdio interrupt issue  
> has been fixed so you should be fine to use CONFIG_PM_RUNTIME. Here is  
> the commit

I have to say that scanning with the 4329 device seems utterly useless,
whereas 4330 works fine.  Apart from the broadcom chip, the rest of the
hardware is identical.

-- 
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html