From: "Nicolás Echániz" <nicoechaniz@codigosur.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc 1mbps in IBSS mode
Date: Thu, 12 Jul 2012 16:52:53 -0300 [thread overview]
Message-ID: <4FFF2B15.5070502@codigosur.org> (raw)
In-Reply-To: <20474.20627.928963.262924@gargle.gargle.HOWL>
On 07/09/2012 12:31 AM, Sujith Manoharan wrote:
> Guido Iribarren wrote:
>> I know nothing about the internal workings of the driver, but i get
>> the feeling that nodes are somehow not acknowledging supported speeds
>> of newly joined nodes, but instead only check other hosts speeds when
>> they join the IBSS cloud for the first time, and so it's limited to
>> nodes already present at the moment of the join.
>
> It looks like commit 6d810f10 changed the behavior.
>
> The station addition notification is now passed to the driver before the
> supported rates are updated for the peer (which happens via ieee80211_rx_bss_info()).
> Drivers which offload rate control to the firmware but depend on mac80211 for
> station management would be affected, I think.
Sujith, does this mean that the problem is outside the scope of the
ath9k_htc driver itself or could it be fixed?
we are doing some heavy use of hardware based on this driver for many
projects; any further debugging work you might need, we are more than
willing to help.
Cheers,
NicoEch?niz
WARNING: multiple messages have this Message-ID (diff)
From: "Nicolás Echániz" <nicoechaniz@codigosur.org>
To: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Cc: Guido Iribarren <guidoiribarren@buenosaireslibre.org>,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] ath9k_htc 1mbps in IBSS mode
Date: Thu, 12 Jul 2012 16:52:53 -0300 [thread overview]
Message-ID: <4FFF2B15.5070502@codigosur.org> (raw)
In-Reply-To: <20474.20627.928963.262924@gargle.gargle.HOWL>
On 07/09/2012 12:31 AM, Sujith Manoharan wrote:
> Guido Iribarren wrote:
>> I know nothing about the internal workings of the driver, but i get
>> the feeling that nodes are somehow not acknowledging supported speeds
>> of newly joined nodes, but instead only check other hosts speeds when
>> they join the IBSS cloud for the first time, and so it's limited to
>> nodes already present at the moment of the join.
>
> It looks like commit 6d810f10 changed the behavior.
>
> The station addition notification is now passed to the driver before the
> supported rates are updated for the peer (which happens via ieee80211_rx_bss_info()).
> Drivers which offload rate control to the firmware but depend on mac80211 for
> station management would be affected, I think.
Sujith, does this mean that the problem is outside the scope of the
ath9k_htc driver itself or could it be fixed?
we are doing some heavy use of hardware based on this driver for many
projects; any further debugging work you might need, we are more than
willing to help.
Cheers,
NicoEchániz
next prev parent reply other threads:[~2012-07-12 19:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 4:02 [ath9k-devel] ath9k_htc 1mbps in IBSS mode Nicolás Echániz
2012-06-11 6:28 ` Adrian Chadd
2012-06-11 12:21 ` Guido Iribarren
2012-07-05 1:53 ` Guido Iribarren
2012-07-09 3:31 ` Sujith Manoharan
2012-07-09 3:31 ` Sujith Manoharan
2012-07-12 19:52 ` Nicolás Echániz [this message]
2012-07-12 19:52 ` Nicolás Echániz
2012-07-15 5:39 ` Sujith Manoharan
2012-07-15 5:39 ` Sujith Manoharan
2012-07-15 8:28 ` Antonio Quartulli
2012-07-15 8:28 ` Antonio Quartulli
2012-07-22 14:52 ` Guido Iribarren
2012-07-23 17:14 ` Antonio Quartulli
2012-08-08 21:58 ` Antonio Quartulli
2012-08-08 21:58 ` Antonio Quartulli
2012-08-08 23:02 ` Antonio Quartulli
2012-08-08 23:02 ` Antonio Quartulli
2012-09-20 23:47 ` Gui Iribarren
2012-09-20 23:47 ` Gui Iribarren
-- strict thread matches above, loose matches on Subject: below --
2012-03-25 15:08 Guido Iribarren
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=4FFF2B15.5070502@codigosur.org \
--to=nicoechaniz@codigosur.org \
--cc=ath9k-devel@lists.ath9k.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 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.