netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Wu <flamingice@sourmilk.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Ulrich Kunitz <kune@deine-taler.de>,
	netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>,
	"Luis Rodriguez" <mcgrof@gmail.com>
Subject: zd1211 ported to Devicescape stack
Date: Sat, 2 Dec 2006 03:16:46 -0500	[thread overview]
Message-ID: <200612020316.50965.flamingice@sourmilk.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1626 bytes --]

Hi,
	I have finished a port of the zd1211 driver to the Devicescape 802.11 stack. 
Due to the size of the patch, the patch that copies the zd1211 directory to 
the d80211 directory has been omitted, but can be found at my git repo. 
(git://git.kernel.org/pub/scm/linux/kernel/git/mwu/d80211-drivers.git up) The 
two other patches relevant to porting the driver are bzip2ed and attached due 
to size concerns.

This port works fairly well in STA mode, with adhoc and monitor modes to come 
in the future. I tried to minimize changes to the structure of the driver and 
code whenever possible to make it easier to port patches from the softmac 
based zd1211 driver to this driver. However:

	- 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.
	-Because d80211 does not have complete regulatory domains support yet, the 
associated code was trimmed to the bare minimum of reading the region code. 
It should be a trivial patch to add regulatory domains support once the 
infrastructure is in place in d80211.
	- 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.
	- 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.

I will push this to wireless-dev soon if there are no major problems.

Thanks,
-Michael Wu

[-- Attachment #1.2: zd1211-kconfig.bz2 --]
[-- Type: application/x-bzip2, Size: 1229 bytes --]

[-- Attachment #1.3: zd1211-port-to-d80211.bz2 --]
[-- Type: application/x-bzip2, Size: 13210 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-12-02  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02  8:16 Michael Wu [this message]
2006-12-02 13:25 ` zd1211 ported to Devicescape stack Ulrich Kunitz
2006-12-02 14:54   ` Michael Wu
2006-12-02 15:58 ` Daniel Drake
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=200612020316.50965.flamingice@sourmilk.net \
    --to=flamingice@sourmilk.net \
    --cc=dsd@gentoo.org \
    --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).