All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mohammed Shafi <mshajakhan@atheros.com>
To: Sujith <m.sujith@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [RFC] ath9k_htc : Update txrate status to mac80211
Date: Thu, 16 Dec 2010 17:38:14 +0530	[thread overview]
Message-ID: <4D0A012E.3090408@atheros.com> (raw)
In-Reply-To: <19721.65246.410283.55163@gargle.gargle.HOWL>

On Thursday 16 December 2010 05:28 PM, Sujith wrote:
> Mohammed Shafi Shajakhan wrote:
>    
>> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>
>> In ath9k htc txrate status is not updated to mac80211 as rate control is
>> handled in firmware.This workaround will obtain the txrate which was
>> supposed to be for debug statistics and updates it to mac80211 using
>> a rate control look up table.
>>      
> Well, we can't match the TXRATE event with any transmitted frame,
> so we would end up sending bogus and most likely, stale, information to mac80211.
>    
Hi Sujith,
             Thanks for your reply.Yes we cannot cleanly send the actual 
status to mac80211.
This patch just takes care for displaying the txrate and appropriately 
sets mac80211 rate control flags,but completely ignores long retries.I 
had tested it  , except retries the MCS index , txrate in userspace 
matches with the txrate reported in debug statistics.
     Is there chance of any possible fix for this ?
> Sujith
> .
>
>    

  reply	other threads:[~2010-12-16 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 11:39 [RFC] ath9k_htc : Update txrate status to mac80211 Mohammed Shafi Shajakhan
2010-12-16 11:58 ` Sujith
2010-12-16 12:08   ` Mohammed Shafi [this message]
2010-12-16 12:23     ` Sujith
2010-12-16 12:45       ` Mohammed Shafi

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=4D0A012E.3090408@atheros.com \
    --to=mshajakhan@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m.sujith@gmail.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.