From: Michael Buesch <mb@bu3sch.de>
To: David Miller <davem@davemloft.net>
Cc: linville@tuxdriver.com, jeff@garzik.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, dsd@gentoo.org,
kune@deine-taler.de
Subject: Re: Please pull 'z1211' branch of wireless-2.6
Date: Wed, 19 Sep 2007 21:23:16 +0200 [thread overview]
Message-ID: <200709192123.16884.mb@bu3sch.de> (raw)
In-Reply-To: <20070919.115903.75429061.davem@davemloft.net>
On Wednesday 19 September 2007 20:59:03 David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Wed, 19 Sep 2007 14:10:05 -0400
>
> > This patch adds z1211 (previously known as zd1211rw-mac80211),
> > a driver for Zydas ZD1211 hardware. This driver has proven very
> > robust -- Fedora 7 uses this driver and I don't think I have any open
> > bugzillas for it. Either the driver works well, or no one as using
> > it...given the common availability of the hardware, I have to presume
> > the former. :-)
> >
> > This driver is mostly a port of zd1211rw to the mac80211
> > infrastructure. In fact, most zd1211rw patches have been mirrored
> > directly to this driver for some time. I considered merely updating
> > the existing driver with this code, but I think it is more prudent to
> > include this as a separate driver just to avoid confusion. There is
> > some symbol clash between the two drivers, so I add a Kconfig hack
> > to ensure that only one or the other is built-in or that this one is
> > built as a module.
> >
> > The maintainers have identified some (IMHO minor) issues with the
> > mac80211 port of this driver. Some of them are summarized here:
> >
> > http://linuxwireless.org/en/users/Drivers/zd1211rw/mac80211Issues
> >
> > Still, I think we would be better-off having this driver upstream.
>
> Agreed, merged into net-2.6.24, thanks John.
John, please also note that the following patch is not merged, yet.
http://bu3sch.de/patches/wireless-dev/20070915-1740/patches/006-zd-fix-tx-status.patch
Without it ratecontrol does not work. It does neither scale the rate
up nor down. This patch fixes both.
I think it got lost in a (really unrelated to the actual bug) discussion
about whether it's required or not to report status in mac80211 drivers.
(It turned out that it _is_ required).
--
Greetings Michael.
next prev parent reply other threads:[~2007-09-19 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 18:10 Please pull 'z1211' branch of wireless-2.6 John W. Linville
2007-09-19 18:59 ` David Miller
2007-09-19 19:23 ` Michael Buesch [this message]
2007-09-19 19:56 ` David Miller
2007-09-19 20:12 ` David Miller
2007-09-19 22:08 ` Daniel Drake
2007-09-19 22:14 ` David Miller
2007-09-19 22:27 ` Daniel Drake
2007-09-19 22:32 ` David Miller
2007-09-20 13:47 ` John W. Linville
2007-09-20 14:28 ` Daniel Drake
2007-09-20 16:37 ` Larry Finger
2007-09-20 16:40 ` Johannes Berg
2007-09-22 9:48 ` Ulrich Kunitz
2007-09-22 12:11 ` Michael Buesch
2007-09-22 14:42 ` Ulrich Kunitz
2007-09-22 14:47 ` Michael Buesch
2007-09-19 22:12 ` Daniel Drake
2007-09-20 13:28 ` John W. Linville
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=200709192123.16884.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=davem@davemloft.net \
--cc=dsd@gentoo.org \
--cc=jeff@garzik.org \
--cc=kune@deine-taler.de \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.