From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: Christian Lamparter <chunkeey@googlemail.com>,
linux-wireless@vger.kernel.org
Subject: Re: ar9170-fw II
Date: Tue, 11 May 2010 18:02:03 -0400 [thread overview]
Message-ID: <4BE9D3DB.7040005@dlasys.net> (raw)
In-Reply-To: <201005021452.01101.chunkeey@googlemail.com>
On 05/02/2010 08:52 AM, Christian Lamparter wrote:
> Well, then you have two more good reasons why to use carl9170:
> * carl9170 has the ability to store additional per-frame data.
> In fact, if you don't need to have a different retry rates
> you could realloc the 3 * 32 bit "rr" (as in retry rate)
> array in the carl9170_tx_superdesc and _carl9170_tx_superdesc
> struct (see wlan.h) for your purposes (storage for your time values).
>
> And if you fetched all the data, everything will be sent
> with an ordinary tx status feedback report to the application
> (add the timer fields into carl9170_tx_status and _carl9170_tx_status
> struct - see fwcmd.h)
cmd.h __check() tests for sizeof(carl9170_tx_status) != 2
is there an assumption somewhere that carl9170_tx_status == 2 ?
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.587.7774 dhlii@dlasys.net http://www.dlasys.net
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2010-05-11 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 10:19 ar9170-fw II David H. Lynch Jr.
2010-05-01 17:19 ` Christian Lamparter
2010-05-01 18:23 ` David H. Lynch Jr.
2010-05-01 20:45 ` Christian Lamparter
2010-05-02 7:47 ` Benoit Papillault
2010-05-02 11:14 ` David H. Lynch Jr.
2010-05-02 12:52 ` Christian Lamparter
2010-05-02 13:47 ` David H. Lynch Jr.
2010-05-05 18:41 ` carl9170 1.0.5.1 David H. Lynch Jr.
2010-05-05 19:59 ` 2.6.34-rc6 pci bridge problems Christian Lamparter
2010-05-06 15:09 ` Bjorn Helgaas
2010-05-07 15:46 ` Bjorn Helgaas
2010-05-06 0:11 ` carl9170 1.0.5.1 Luis R. Rodriguez
2010-05-11 22:02 ` David H. Lynch Jr. [this message]
2010-05-11 23:27 ` ar9170-fw II Christian Lamparter
2010-05-21 7:50 ` carl9170 1.0.6 David H. Lynch Jr.
2010-05-21 21:35 ` carl9170 1.0.6 carl9170_tx_superdesc David H. Lynch Jr.
2010-05-21 22:55 ` Christian Lamparter
2010-05-22 1:09 ` David H. Lynch Jr.
2010-05-22 19:13 ` carl9170 1.0.9 David H. Lynch Jr.
2010-05-23 1:34 ` Christian Lamparter
2010-05-23 5:30 ` David H. Lynch Jr.
2010-05-23 6:30 ` carl9170 1.0.9.1 David H. Lynch Jr.
2010-05-03 21:39 ` ar9170-fw II Luis R. Rodriguez
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=4BE9D3DB.7040005@dlasys.net \
--to=dhlii@dlasys.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.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).