From: Daniel Drake <dsd@gentoo.org>
To: Michael Wu <flamingice@sourmilk.net>
Cc: John Linville <linville@tuxdriver.com>,
netdev@vger.kernel.org, Ulrich Kunitz <kune@deine-taler.de>
Subject: Re: d80211-drivers pull request (week-48)
Date: Mon, 11 Dec 2006 20:07:32 -0500 [thread overview]
Message-ID: <457E00D4.7010201@gentoo.org> (raw)
In-Reply-To: <200612110101.58710.flamingice@sourmilk.net>
Michael Wu wrote:
> zd1211rw-d80211: Use ieee80211_tx_status
I've thought some more about this and I'm not so sure that this is the
right approach.
Can't devicescape be taught that the ZD1211 handles retries in hardware
and the stack doesn't need to worry about it?
What does devicescape do in response to not getting an ack? Does it
retransmit? If that is all then it doesn't need to be at stack level,
since the hardware handles that on its own, and we can configure that to
behave the same way as the stack would.
I think I remember reading that devicescape uses failed transmission
rate in the rate adjustment calculations. Even without this racy ack
system we can still achieve that - the device tells us every time it
retries a transmit, and then it sends a special interrupt at the end
saying that all retries failed.
Daniel
next prev parent reply other threads:[~2006-12-12 1:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 6:01 d80211-drivers pull request (week-48) Michael Wu
2006-12-12 1:07 ` Daniel Drake [this message]
2006-12-12 2:20 ` Michael Wu
2006-12-12 3:51 ` Daniel Drake
2006-12-12 4:28 ` Michael Wu
2006-12-12 23:39 ` Ulrich Kunitz
2006-12-13 2:35 ` Michael Wu
2006-12-12 9:35 ` Michael Buesch
2006-12-15 5:54 ` Simon Barber
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=457E00D4.7010201@gentoo.org \
--to=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--cc=netdev@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).