From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 2/2] mac80211: Support ht-cap over-rides.
Date: Mon, 07 Nov 2011 18:06:43 +0100 [thread overview]
Message-ID: <1320685603.3993.51.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EB8051D.5010704@candelatech.com>
On Mon, 2011-11-07 at 08:19 -0800, Ben Greear wrote:
> > Why is this not just a static const that you fill manually? There's
> > nothing that's not constant here. So e.g.
> >
> > static const struct ieee80211_ht_cap mac80211_ht_capa_mod_mask = {
> > .ampdu_params_info = IEEE80211_HT_AMPDU_PARM_FACTOR |
> > IEEE80211_HT_AMPDU_PARM_DENSITY,
> > .mcs = {
> > .rx_mask = { 0xff, 0xff, 0xff, 0xff, 0xff,
> > 0xff, 0xff, 0xff, 0xff, 0xff, },
> > },
> > /* etc */
> > };
>
> Well, you suggested a pointer in the wiphy struct that was null
> for non mac80211 interfaces. I'm not sure how to distinguish between
> mac80211 and other wiphys when reporting the capabilities if I use
> this global static. I also like that the non-static logic lets
> us tweak this for individual drivers if that becomes an issue.
Right. So if you assign this pointer in alloc_hw() then the driver can
still override it before register_hw(). I don't see at all why it needs
to be dynamically allocated.
johannes
next prev parent reply other threads:[~2011-11-07 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 20:10 [PATCH v4 1/2] wireless: Support ht-capabilities over-rides greearb
2011-11-04 20:10 ` [PATCH v4 2/2] mac80211: Support ht-cap over-rides greearb
2011-11-07 9:13 ` Johannes Berg
2011-11-07 16:19 ` Ben Greear
2011-11-07 17:06 ` Johannes Berg [this message]
2011-11-04 21:03 ` [PATCH v4 1/2] wireless: Support ht-capabilities over-rides Johannes Berg
2011-11-07 9:06 ` Johannes Berg
2011-11-07 16:27 ` Ben Greear
2011-11-07 17:02 ` Johannes Berg
2011-11-07 17:40 ` Ben Greear
2011-11-07 17:42 ` Johannes Berg
2011-11-07 17:45 ` Ben Greear
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=1320685603.3993.51.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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 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).