All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 2/3] cfg80211: add cellular base station regulatory hint support
Date: Tue, 10 Jul 2012 17:25:55 +0200	[thread overview]
Message-ID: <1341933955.4475.24.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1341613226-11774-3-git-send-email-rodrigue@qca.qualcomm.com>

On Fri, 2012-07-06 at 15:20 -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>
> 
> Cellular base stations can provide hints to cfg80211 about
> where they think we are. This can be done for example by on
> a cell phone.

by what? :)

> To enable these hints we simply allow them
> through as user regulatory hints but we allow userspace
> to clasify the hint. This option is only available for

if you're going to respin ... classify

> system integrators which are willing to enable

who are willing? not sure

> CONFIG_CFG80211_CERTIFICATION_ONUS.
> 
> The base station hints themselves will not be processsed

processed :)

> by the core unless at least one device on the system
> supports this feature.

So ... yeah I guess this is fine. we don't really want to distinguish
between the devices too much anyway. And I suspect that if you're in an
environment where you allow plugging in random wireless devices you
wouldn't enable this anyway.

>   *	DFS master operation on a known DFS region (NL80211_DFS_*),
>   *	dfs_region represents that region. Drivers can use this and the
>   *	@alpha2 to adjust their device's DFS parameters as required.
> + * @user_reg_hint_type: if the @initiator was of type
> + *	%NL80211_REGDOM_SET_BY_USER, this clasifies the type

classifies

> + *	of hint passed. This could be any of the %NL80211_USER_REG_HINT_*

could be any of the ... "values"?

>  	/* set up regulatory info */
> +	wiphy_regulatory_register(wiphy);
>  	regulatory_update(wiphy, NL80211_REGDOM_SET_BY_CORE);

might make sense to move the regulatory_update() call into the new
function, then it could become a static function?

> +++ b/net/wireless/nl80211.c
> @@ -294,6 +294,7 @@ static const struct nla_policy nl80211_policy[NL80211_ATTR_MAX+1] = {
>  	[NL80211_ATTR_NOACK_MAP] = { .type = NLA_U16 },
>  	[NL80211_ATTR_INACTIVITY_TIMEOUT] = { .type = NLA_U16 },
>  	[NL80211_ATTR_BG_SCAN_PERIOD] = { .type = NLA_U16 },
> +	[NL80211_ATTR_USER_REG_HINT_TYPE] = { .type = NLA_U8 },

I think u32 makes more sense, u8 doesn't actually save you anything
(same space in the netlink attributes, and you have to validate it
anyway)

> -	r = regulatory_hint_user(data);
> +	if (info->attrs[NL80211_ATTR_USER_REG_HINT_TYPE])
> +		user_reg_hint_type =
> +		  nla_get_u8(info->attrs[NL80211_ATTR_USER_REG_HINT_TYPE]);

need to validate that it's a valid value, otherwise I can pass "42" :-)

johannes


  reply	other threads:[~2012-07-10 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 22:20 [PATCH v3 0/3] wireless: certification onus and cell regulatory hint Luis R. Rodriguez
2012-07-06 22:20 ` [PATCH v3 1/3] cfg80211: add CONFIG_CFG80211_CERTIFICATION_ONUS Luis R. Rodriguez
2012-07-06 22:20 ` [PATCH v3 2/3] cfg80211: add cellular base station regulatory hint support Luis R. Rodriguez
2012-07-10 15:25   ` Johannes Berg [this message]
2012-07-10 17:18     ` Luis R. Rodriguez
2012-07-06 22:20 ` [PATCH v3 3/3] cfg80211: rename reg_device_remove() to wiphy_regulatory_deregister() 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=1341933955.4475.24.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 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.