Return-path: Received: from mail-qy0-f174.google.com ([209.85.216.174]:61006 "EHLO mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932506Ab1IMUZ6 convert rfc822-to-8bit (ORCPT ); Tue, 13 Sep 2011 16:25:58 -0400 Received: by qyk30 with SMTP id 30so3056689qyk.19 for ; Tue, 13 Sep 2011 13:25:57 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20110913132844.GB11772@tuxdriver.com> References: <20110913132844.GB11772@tuxdriver.com> Date: Tue, 13 Sep 2011 22:25:57 +0200 Message-ID: (sfid-20110913_222601_867216_2709F996) Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set" From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: "John W. Linville" Cc: Francis Moreau , Arend van Spriel , linux-wireless@vger.kernel.org, gregkh@suse.de Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 2011/9/13 John W. Linville : > On Tue, Sep 13, 2011 at 09:03:13AM +0200, Francis Moreau wrote: >> 2011/9/12 Rafał Miłecki : > >> > The real solution is to add bcma driver support in brcmsmac and ssb >> > driver support in brcmfmac. Then you can always use bcma and: >> > 1) If b43 will load and detect unsupported PHY, it will release the BCMA's core >> > 2) brcmsmac will be loaded to let it support the core >> > >> >> Thanks for the description. >> >> But what should be done for the time being (3.1-rc5) ? > > Turn-off CONFIG_B43_BCMA. Well, that won't prevent bcma from loading and taking the (PCI) device. brcmsmac still won't be able to grab that device. CONFIG_B43_BCMA doesn't affect bcma bus driver. There are 2 drivers requesting for the same PCI ids: bcma and brcmsmac. You may want to just blacklist bcma if you're going to use brcmsmac. -- Rafał