From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
kvalo@qca.qualcomm.com, arend@broadcom.com, henry@logout.com,
senthilb@qca.qualcomm.com
Subject: Re: [PATCH 4/4] cfg80211: add cellular base station regulatory hint support
Date: Fri, 06 Jul 2012 16:11:59 +0200 [thread overview]
Message-ID: <1341583919.16893.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6XmbAu+xkLHYaBt=z6zdxXME5cOoANUd_3yEr+va_jb8g@mail.gmail.com> (sfid-20120706_160608_656782_E1FD7845)
On Fri, 2012-07-06 at 07:05 -0700, Luis R. Rodriguez wrote:
> That, but also it means there are two hops for a device to use the
> cell base station hint: onus option, and then the feature flag, which
> could be wrapped itself around a driver specific kconfig option.
> Reason for the feature flag is devices may need a firmware update in
> order for them to work properly.
>
> As for the onus and the cell base station hint though, it is true
> though that the onus option would alone enable the core cell base
> station hints, so the onus option itself would be flipping a switch
> for a feature. I could extend the patch to include a core specific
> base station hint kconfig option, because as you say there is no
> specific switch to select the feature right now for the core.
I guess the question is -- what does that code really enable, if the
driver doesn't also set the feature flag? If it doesn't mean anything
without the flag I think we don't need the extra core option?
johannes
next prev parent reply other threads:[~2012-07-06 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 23:15 [PATCH 0/4] wireless: certification onus and cell regulatory hint Luis R. Rodriguez
2012-07-03 23:15 ` [PATCH 1/4] cfg80211: add CONFIG_CFG80211_CERTIFICATION_ONUS Luis R. Rodriguez
2012-07-03 23:15 ` [PATCH 2/4] ath5k: replace modparam_all_channels with CONFIG_ATH5K_TEST_CHANNELS Luis R. Rodriguez
2012-07-03 23:15 ` [PATCH 3/4] ath9k: make CONFIG_ATH9K_DFS_CERTIFIED depend on CFG80211_CERTIFICATION_ONUS Luis R. Rodriguez
2012-07-03 23:15 ` [PATCH 4/4] cfg80211: add cellular base station regulatory hint support Luis R. Rodriguez
2012-07-04 9:42 ` Johannes Berg
2012-07-04 16:26 ` Luis R. Rodriguez
2012-07-05 7:45 ` Johannes Berg
2012-07-05 16:48 ` Luis R. Rodriguez
2012-07-06 6:39 ` Johannes Berg
2012-07-06 14:05 ` Luis R. Rodriguez
2012-07-06 14:11 ` Johannes Berg [this message]
2012-07-06 15:47 ` Luis R. Rodriguez
2012-07-06 15:51 ` Johannes Berg
2012-07-06 16:07 ` Luis R. Rodriguez
2012-07-06 16:15 ` Johannes Berg
2012-07-06 16:31 ` Luis R. Rodriguez
2012-07-06 16:53 ` Luis R. Rodriguez
2012-07-06 22:09 ` Luis R. Rodriguez
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=1341583919.16893.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=henry@logout.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).