From: "Arend van Spriel" <arend@broadcom.com>
To: "Hauke Mehrtens" <hauke@hauke-m.de>
Cc: "Dan Carpenter" <dan.carpenter@oracle.com>,
brcm80211-dev-list@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: How to get BRCM to work?
Date: Wed, 6 Nov 2013 14:29:31 +0100 [thread overview]
Message-ID: <527A443B.9090500@broadcom.com> (raw)
In-Reply-To: <527A389E.9050701@hauke-m.de>
On 11/06/13 13:39, Hauke Mehrtens wrote:
> On 11/06/2013 10:44 AM, Arend van Spriel wrote:
>> On 11/05/2013 11:25 PM, Dan Carpenter wrote:
>>> It's working. I think it was just a problem with the random old
>>> linux-next kernel I was testing. Sorry for the noise.
>>>
>>> I do think it should be "select BCMA" instead of "depends on BCMA". Is
>>> there something I have missed?
>>
>> I agree that most users would be unaware that they need BCMA. However,
>> the usual problem with 'select' is that the dependencies of the selected
>> item are not selected. I believe Kconfig will fire off a warning for it,
>> but the aforementioned users may only raise an eyebrow and continue.
>>
>> If there are Kconfig wizards out there, please feel free to make any
>> suggestions.
>
> Currently CONFIG_BCMA does not select anything else, it just depends on
> CONFIG_BCMA_POSSIBLE, when CONFIG_BCMA is selected CONFIG_BCMA_HOST_PCI
> will be activated automatically, so for the case of a PCIe card it
> should work with "select BCMA" in brcmsmac, CONFIG_BCMA_POSSIBLE is set
> for all normal PCs.
I remember vaguely some issues with selecting GPIOLIB. Anyway, I guess I
should go for:
depends BCMA_POSSIBLE
select BCMA if BCMA_POSSIBLE
The first makes sure brcmsmac can only be selected on platforms where
BCMA is possible and the second for the BCMA selection. Does that make
sense?
Regards,
Arend
> In b43 we do the same with CONFIG_SSB and I do not know of any problems.
>
> Hauke
>
prev parent reply other threads:[~2013-11-06 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 11:51 How to get BRCM to work? Dan Carpenter
2013-11-04 12:00 ` Dan Carpenter
2013-11-04 12:04 ` Hauke Mehrtens
2013-11-04 13:07 ` Dan Carpenter
2013-11-04 15:05 ` Arend van Spriel
2013-11-05 22:25 ` Dan Carpenter
2013-11-06 9:44 ` Arend van Spriel
2013-11-06 12:39 ` Hauke Mehrtens
2013-11-06 13:29 ` Arend van Spriel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527A443B.9090500@broadcom.com \
--to=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.