linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [wireless-next PATCH 1/5] mac80211: Support forcing station to disable 11n.
Date: Wed, 02 Nov 2011 23:04:22 -0700	[thread overview]
Message-ID: <4EB22EE6.3030100@candelatech.com> (raw)
In-Reply-To: <1320256263.7846.3.camel@jlt3.sipsolutions.net>

On 11/02/2011 10:51 AM, Johannes Berg wrote:
> On Wed, 2011-11-02 at 09:34 -0700, Ben Greear wrote:
>
>>> You misunderstood -- I said fullmac drivers, not differences between
>>> ath9k, iwlwifi etc. Other cfg80211 drivers, not other mac80211 drivers.
>>
>> Can you at least point me to some existing code that does a similar
>> check?  I have no idea of what a fullmac driver even does.  I can test
>> and eventually somewhat understand the paths for ath9k, but I have no
>> ability to test fullmac (as far as I know).
>
> Well ideally you have two patches -- one for cfg80211, and one for
> mac80211. Then you can test the cfg80211 one w/o mac80211 patches, so it
> behaves as though it didn't support it, and with the mac80211 patch it
> sets the flag to support it. Just think about drivers like ath6kl.

I think I made at least most of the other changes you were asking
for, but I'm still baffled about what to do about fullmac drivers.

Based on the comment above, if I simply left out the mac80211 stuff
then the new values passed in to the associate/connect logic will just
be ignored.

So, I suppose the fullmac drivers will just silently ignore the new
variables as well.  I looked, but didn't figure out where fullmac
connects into the cfg80211 logic.  If I can find it, then I could
add explicit checks for the new variables and return failure if
they are set..but I'm not sure that is any better than just silently
ignoring them anyway.

Anyway, hopefully the 3 v3 patches are closer to what you are
looking for.  They seem to test out fine for me, though I never
see AMSDU go to max value.  Maybe ath9k just doesn't support
that by default, as I didn't see it on the stock wireless-testing
code either...or maybe my AP or something else is weird.

I'll post the hostap patches when the kernel side is resolved.
They are a lot smaller now that everything goes through
the connect/associate logic.

Thanks,
Ben


>
> johannes


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2011-11-03  6:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  5:11 [wireless-next PATCH 1/5] mac80211: Support forcing station to disable 11n greearb
2011-10-28  5:11 ` [wireless-next PATCH 2/5] wifi: Support disabling ht40 greearb
2011-10-28  8:09   ` Johannes Berg
2011-10-28 16:25     ` Ben Greear
2011-10-28  5:11 ` [wireless-next PATCH 3/5] wifi: Allow overriding some HT information greearb
2011-10-28  8:12   ` Johannes Berg
2011-10-28 16:33     ` Ben Greear
2011-11-02  8:13       ` Johannes Berg
2011-11-02 16:59         ` Ben Greear
2011-11-02 17:49           ` Johannes Berg
2011-11-02 18:03             ` Ben Greear
2011-11-03  8:32               ` Johannes Berg
2011-10-28  5:11 ` [wireless-next PATCH 4/5] wifi: Warn if cannot add station debugfs entries greearb
2011-10-28  8:13   ` Johannes Berg
2011-10-28 16:13     ` Ben Greear
2011-10-28  5:11 ` [wireless-next PATCH 5/5] wifi-debugfs: Fix AMSDU rate printout greearb
2011-10-28  8:13   ` Johannes Berg
2011-11-17 17:49   ` Ben Greear
2011-11-17 18:03     ` John W. Linville
2011-10-28  5:15 ` [wireless-next PATCH 1/5] mac80211: Support forcing station to disable 11n Ben Greear
2011-10-28  8:08 ` Johannes Berg
2011-10-28 16:24   ` Ben Greear
2011-11-02  7:56     ` Johannes Berg
2011-11-02 16:37       ` Ben Greear
2011-10-28 18:55   ` Ben Greear
2011-11-02  7:53     ` Johannes Berg
2011-11-02 16:34       ` Ben Greear
2011-11-02 17:51         ` Johannes Berg
2011-11-03  6:04           ` Ben Greear [this message]
2011-11-03  8:30             ` Johannes Berg
2011-11-03 18:17               ` Ben Greear
2011-11-04 14:42                 ` Johannes Berg
2011-11-04 16:11                   ` Ben Greear
2011-11-04 16:17                     ` Johannes Berg

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=4EB22EE6.3030100@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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).