Rafal, Francis has a 4313. As support for that device is not yet in b43 you could consider not claiming it for now in bcma. Gr. AvS -----Original Message----- From: Rafał Miłecki [mailto:zajec5@xxxxxxxxx] Sent: dinsdag 13 september 2011 22:26 To: John W. Linville Cc: Francis Moreau; Arend Van Spriel; linux-wireless@xxxxxxxxxxxxxxx; gregkh@xxxxxxx Subject: Re: About the patch: "staging: brcm80211: only enable brcmsmac if bcma is not set" 2011/9/13 John W. Linville <linville@xxxxxxxxxxxxx>: > On Tue, Sep 13, 2011 at 09:03:13AM +0200, Francis Moreau wrote: >> 2011/9/12 Rafał Miłecki <zajec5@xxxxxxxxx>: > >> > 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ł ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
