From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@web.de>, Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC][PATCH 1/5] p54: broken out vdcf code
Date: Thu, 09 Oct 2008 08:20:25 -0700 [thread overview]
Message-ID: <48EE2139.102@lwfinger.net> (raw)
In-Reply-To: <200810050238.28100.chunkeey@web.de>
Christian Lamparter wrote:
> Broken out the vdcf's code into another patch, as it caused problems in the last RFC.
This patch has the following insertion as a replacement:
+struct p54_tx_vdcf_queues {
+ u8 aifs;
+ u8 padding;
+ __le16 cwmin;
+ __le16 cwmax;
+ __le16 txop;
+} __attribute__ ((packed));
Previously, aifs was of type __le16. With this change, the macro
P54_SET_QUEUE must be changed as follows:
#define P54_SET_QUEUE(queue, ai_fs, cw_min, cw_max, _txop) \
do { \
- queue.aifs = cpu_to_le16(ai_fs); \
+ queue.aifs = ai_fs; \
queue.cwmin = cpu_to_le16(cw_min); \
queue.cwmax = cpu_to_le16(cw_max); \
queue.txop = cpu_to_le16(_txop); \
To further emphasize that the second parameter is u8, I also suggest
the following changes in the macro invocation:
- P54_SET_QUEUE(priv->qos_params[0], 0x0002, 0x0003, 0x0007, 47);
- P54_SET_QUEUE(priv->qos_params[1], 0x0002, 0x0007, 0x000f, 94);
- P54_SET_QUEUE(priv->qos_params[2], 0x0003, 0x000f, 0x03ff, 0);
- P54_SET_QUEUE(priv->qos_params[3], 0x0007, 0x000f, 0x03ff, 0);
+ P54_SET_QUEUE(priv->qos_params[0], 0x02, 0x0003, 0x0007, 47);
+ P54_SET_QUEUE(priv->qos_params[1], 0x02, 0x0007, 0x000f, 94);
+ P54_SET_QUEUE(priv->qos_params[2], 0x03, 0x000f, 0x03ff, 0);
+ P54_SET_QUEUE(priv->qos_params[3], 0x07, 0x000f, 0x03ff, 0);
Larry
next prev parent reply other threads:[~2008-10-09 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 0:38 [RFC][PATCH 1/5] p54: broken out vdcf code Christian Lamparter
2008-10-09 15:20 ` Larry Finger [this message]
2008-10-09 16:53 ` Christian Lamparter
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=48EE2139.102@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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).