Return-path: Received: from mail-vw0-f42.google.com ([209.85.212.42]:45576 "EHLO mail-vw0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752457Ab1INHAN convert rfc822-to-8bit (ORCPT ); Wed, 14 Sep 2011 03:00:13 -0400 Received: by vwl1 with SMTP id 1so2173474vwl.1 for ; Wed, 14 Sep 2011 00:00:12 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20110913132844.GB11772@tuxdriver.com> Date: Wed, 14 Sep 2011 08:53:39 +0200 Message-ID: (sfid-20110914_090018_128689_D6D73F56) Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set" From: Francis Moreau To: =?ISO-8859-2?Q?Rafa=B3_Mi=B3ecki?= Cc: "John W. Linville" , 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 Rafał Miłecki : > 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. > Will it work if bcma is builtin in the kernel (not configured as module) ? Thanks -- Francis