From: Christian Lamparter <chunkeey@web.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: [RFC][PATCH 1/5] p54: broken out vdcf code
Date: Thu, 9 Oct 2008 18:53:01 +0200 [thread overview]
Message-ID: <200810091853.02076.chunkeey@web.de> (raw)
In-Reply-To: <48EE2139.102@lwfinger.net>
On Thursday 09 October 2008 17:20:25 Larry Finger wrote:
> 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));
Well, I took this idea from stlc45xx. But now, after some digging in the specs about WMM...
I came to the conclusion that this is superfluous. I'll revert back to the original __le16 aifs,
in the next RFC/RFT round... But now, we should better fix the code for big-endian machines.
I tried to use qemu to emulate a PPC machine, but it's painfully slow and the QEMU's USB
loop through code doesn't work as advertised (yet?).
Regards,
Chr
prev parent reply other threads:[~2008-10-09 16:49 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
2008-10-09 16:53 ` Christian Lamparter [this message]
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=200810091853.02076.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--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).