From: Daniel Drake <dsd@gentoo.org>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Ulrich Kunitz <kune@deine-taler.de>,
netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>,
Luis Rodriguez <mcgrof@gmail.com>
Subject: Re: zd1211 ported to Devicescape stack
Date: Sat, 02 Dec 2006 10:58:13 -0500 [thread overview]
Message-ID: <4571A295.4030700@gentoo.org> (raw)
In-Reply-To: <200612020316.50965.flamingice@sourmilk.net>
Michael Wu wrote:
> Hi,
> I have finished a port of the zd1211 driver to the Devicescape 802.11 stack.
Yeah!! thanks so much for doing this.
Are you willing to maintain this in terms of porting upcoming patches to
it? I think I also speak for Ulrich when I say that at the moment we are
more concerned about getting our work into mainline and don't have time
to maintain a ported driver, but we will be happy to switch immediately
as soon as devicescape is declared ready for mainline inclusion.
> - The original driver does not seem to check if a frame has been successfully
> TXed (as in RXed an ACK), so the port does not properly report to the stack
> whether or not a TX succeeded.
Indeed, the situation is that silence means transmission succeeded, and
we get a retry_failed interrupt if it didn't.
> - d80211 doesn't tell us the size of the next fragment, so that part of the
> hardware TX header isn't set anymore. This might be fixed in the future.
Even though ieee80211 appeared to have the infrastructure to do so, I
don't think it was ever passing us multiple fragments. So this is no big
deal.
> - The LED link status isn't too reliable - I haven't found a way to reliably
> tell if the upper layer thinks it is associated, and I don't know how to use
> the LED api. Not too worried about this issue though.
Watch out, the single most common bug report for zd1211rw (vs vendor
driver) was that the LED didn't blink until recently :)
Thanks!
Daniel
next prev parent reply other threads:[~2006-12-02 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 8:16 zd1211 ported to Devicescape stack Michael Wu
2006-12-02 13:25 ` Ulrich Kunitz
2006-12-02 14:54 ` Michael Wu
2006-12-02 15:58 ` Daniel Drake [this message]
2006-12-02 17:57 ` Ulrich Kunitz
2006-12-02 18:32 ` Michael Wu
2006-12-02 18:55 ` Daniel Drake
2006-12-02 19:53 ` Ulrich Kunitz
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=4571A295.4030700@gentoo.org \
--to=dsd@gentoo.org \
--cc=flamingice@sourmilk.net \
--cc=kune@deine-taler.de \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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).