From: Antonio Quartulli <ordex@autistici.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] mac80211: add sta_update_rates callback
Date: Thu, 9 Aug 2012 11:44:56 +0200 [thread overview]
Message-ID: <20120809094455.GH6767@ritirata.org> (raw)
In-Reply-To: <20120809093245.GG6767@ritirata.org>
[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]
On Thu, Aug 09, 2012 at 11:32:46AM +0200, Antonio Quartulli wrote:
> On Thu, Aug 09, 2012 at 08:14:57AM +0200, Johannes Berg wrote:
> > Also there's already an update call sta_rc_update() so I think you
> > should just define a new change flag for that?
>
> mh, at the very beginning I thought it was not correct what you said, but indeed
> we should be able to do the job in sta_rc_update().
>
> But then why does the ath9k_htc driver implement ath9k_htc_update_rate() to
> update the rate used to talk to the AP? Should it use sta_rc_update() as well?
Well, I am digging into the driver a bit more and I realised that the supported
rate set does not touch the RC at all. The supported rates are only stored in
the device (this is why there is another function for doing that in case of STA
mode) and then the RC will play its game from a different point.
For the reason above sta_rc_update() can't do what we want. At this point I
think we have two options:
1) mac80211 forces this change to be done by sta_rc_update() => ath9k has to
adapt it's implementation to follow the API
2) mac80211 uses another callback (sta_update_rates()) to refresh the supported
rates set.
I think that option 2) is probably the way to go, because the RC stuff is
usually not strictly related to the real device (e.g. ath9k has its own rc
routines shared among ath9k and ath9k_htc but they have different routins to set
the supported_rates set for a station.)
Cheers,
>
> Cheers,
>
>
> >
> > johannes
>
> --
> Antonio Quartulli
>
> ..each of us alone is worth nothing..
> Ernesto "Che" Guevara
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-09 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344474712-22561-1-git-send-email-ordex@autistici.org>
[not found] ` <1344492897.4494.1.camel@jlt3.sipsolutions.net>
2012-08-09 9:32 ` [PATCH 1/2] mac80211: add sta_update_rates callback Antonio Quartulli
2012-08-09 9:44 ` Antonio Quartulli [this message]
2012-08-20 11:27 ` Johannes Berg
2012-08-12 5:26 ` [ath9k-devel] " Sujith Manoharan
2012-08-12 5:31 ` Sujith Manoharan
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=20120809094455.GH6767@ritirata.org \
--to=ordex@autistici.org \
--cc=ath9k-devel@lists.ath9k.org \
--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).