All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Winkler <tomas.winkler@intel.com>
To: linville@tuxdriver.com, johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, Tomas Winkler <tomas.winkler@intel.com>
Subject: [RFC] mac80211: add rate to ieee80211_tx_status
Date: Sun,  3 Feb 2008 22:15:05 +0200	[thread overview]
Message-ID: <12020697053277-git-send-email-tomas.winkler@intel.com> (raw)

This patch adds rate to ieee80211_tx_status.
Downscaling in iwl4965 is done in FW. Rate scaling algorithm
needs to know at which rate the packet was actually transmitted
Patch 'cfg80211 API for channels/bitrates' removed the placeholder
for this information that was present in ieee80211_tx_control.

Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
---

This fix or something similar is required for bringing iwlwifi back to life.
Please comments, suggestions 
Thanks

 include/net/mac80211.h |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 460da54..a700ea6 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -342,6 +342,7 @@ enum ieee80211_tx_status_flags {
  *
  * @control: a copy of the &struct ieee80211_tx_control passed to the driver
  *	in the tx() callback.
+ * @rate: rate at which the packet was actually transmitted
  * @flags: transmit status flags, defined above
  * @retry_count: number of retries
  * @excessive_retries: set to 1 if the frame was retried many times
@@ -356,6 +357,7 @@ enum ieee80211_tx_status_flags {
  */
 struct ieee80211_tx_status {
 	struct ieee80211_tx_control control;
+	struct ieee80211_rate rate;
 	u8 flags;
 	u8 retry_count;
 	bool excessive_retries;
-- 
1.5.2.2


             reply	other threads:[~2008-02-03 20:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 20:15 Tomas Winkler [this message]
2008-02-04  8:46 ` [RFC] mac80211: add rate to ieee80211_tx_status Johannes Berg
2008-02-04  9:53   ` Tomas Winkler
     [not found]     ` <6231174111099834440@unknownmsgid>
2008-02-04 10:27       ` Tomas Winkler
     [not found]         ` <-6799378017406559341@unknownmsgid>
2008-02-04 11:05           ` Tomas Winkler
     [not found]             ` <-4694429725714512287@unknownmsgid>
2008-02-04 11:21               ` Tomas Winkler
     [not found]                 ` <-2417195033053015320@unknownmsgid>
2008-02-04 11:26                   ` Tomas Winkler
2008-02-04 11:30                     ` Tomas Winkler
     [not found]                       ` <5358276387473684738@unknownmsgid>
2008-02-04 11:57                         ` Tomas Winkler
     [not found]                           ` <5605009721259660313@unknownmsgid>
2008-02-04 13:35                             ` Tomas Winkler
     [not found]                           ` <49711.::ffff:91.5.56.63.1202126931.squirrel@secure.sipsolutions.net>
2008-02-04 13:53                             ` Felix Fietkau
     [not found]                               ` <-5971017268625562167@unknownmsgid>
2008-02-04 14:21                                 ` Tomas Winkler
     [not found]                                   ` <-7767648866191425885@unknownmsgid>
2008-02-04 15:13                                     ` Tomas Winkler
2008-02-04 15:24                                       ` Felix Fietkau
2008-02-04 18:36                                         ` Tomas Winkler
2008-02-04 18:39                                           ` Felix Fietkau
2008-02-04 19:03                                             ` Tomas Winkler
2008-02-04 19:05                                               ` Tomas Winkler
2008-02-05 21:23                                                 ` Stefano Brivio
2008-02-05 23:15                                                   ` Tomas Winkler
2008-02-06 14:13                                                     ` Johannes Berg
2008-02-04 19:07                                               ` Felix Fietkau

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=12020697053277-git-send-email-tomas.winkler@intel.com \
    --to=tomas.winkler@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.