From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Please pull 'upstream' branch of rt2x00
Date: Sun, 16 Sep 2007 14:17:39 +0200 [thread overview]
Message-ID: <200709161417.40727.IvDoorn@gmail.com> (raw)
Hi John,
It has taken some time to finally release this,
but it contains quite a lot of bugfixes of variating impact.
Overall the stability has been greatly improved,
although there are still some nasty bugs in there.
Note that even after this update rt2x00 in wireless-dev will still not work
for encrypted networks. This is because rt2x00 depends on the encryption
patches by Johannes which are pending for wireless-dev inclusion
(Most notably the patch that fixes the IEEE80211_HW_WEP_INCLUDE_IV
behavior is required to make it work again).
Ivo
---
The following changes since commit e6d77b902151278df6a670b460a32e7cc6b75e9e:
Luis R. Rodriguez (1):
Merge branch 'ath5k' into everything
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git/ upstream
Ivo van Doorn (24):
rt2x00: Remove firmware not-NULL check
rt2x00: Don't check for IEEE80211_TXCTL_REQ_TX_STATUS
rt2x00: Cleanup rxdone
rt2x00: Don't allow configuration calls when uninitialized
rt2x00: Fix rt61pci and rt73usb beacon handling
rt2x00: Recalculate link quality
rt2x00: Cleanup entry->flags
rt2x00: Reduce LNA flags
rt2x00: Rework RT61 and RT73 Antenna handling
rt2x00: Rename DEVICE_SUPPORT_ATIM to REQUIRE_BEACON_RING
rt2x00: Remove rt2x00mac_reset()
rt2x00: Fix system freeze on device removal
rt2x00: Reduce magic value writing to device
rt2x00: New USB ID's for rt73usb and rt2500usb
rt2x00: Beacon ring entries should have QID_MGMT
rt2x00: Fix DEV_RATEBIT_ definitions
rt2x00: Fix rfkill handling
rt2x00: Merge allocation/free register components
rt2x00: macro's shouldn't use hidden arguments
rt2x00: Fix channel initialization
rt2x00: Add better CONFIG_PM checks
rt2x00: Add start/stop handlers
rt2x00: Add additional bit to MAX_FRAME_UNIT
rt2x00: Release rt2x00 2.0.8
drivers/net/wireless/rt2x00/rt2400pci.c | 37 +-
drivers/net/wireless/rt2x00/rt2500pci.c | 83 +++--
drivers/net/wireless/rt2x00/rt2500pci.h | 40 ++-
drivers/net/wireless/rt2x00/rt2500usb.c | 208 ++++++++--
drivers/net/wireless/rt2x00/rt2500usb.h | 39 ++-
drivers/net/wireless/rt2x00/rt2x00.h | 47 ++-
drivers/net/wireless/rt2x00/rt2x00config.c | 12 +-
drivers/net/wireless/rt2x00/rt2x00debug.c | 26 +-
drivers/net/wireless/rt2x00/rt2x00dev.c | 308 ++++++--------
drivers/net/wireless/rt2x00/rt2x00firmware.c | 6 +-
drivers/net/wireless/rt2x00/rt2x00lib.h | 4 +-
drivers/net/wireless/rt2x00/rt2x00mac.c | 111 ++++--
drivers/net/wireless/rt2x00/rt2x00pci.c | 127 ++----
drivers/net/wireless/rt2x00/rt2x00pci.h | 3 +
drivers/net/wireless/rt2x00/rt2x00reg.h | 27 +-
drivers/net/wireless/rt2x00/rt2x00rfkill.c | 6 +-
drivers/net/wireless/rt2x00/rt2x00ring.h | 29 +-
drivers/net/wireless/rt2x00/rt2x00usb.c | 235 +++--------
drivers/net/wireless/rt2x00/rt2x00usb.h | 9 +-
drivers/net/wireless/rt2x00/rt61pci.c | 617 ++++++++++++++++++--------
drivers/net/wireless/rt2x00/rt61pci.h | 87 ++++-
drivers/net/wireless/rt2x00/rt73usb.c | 471 +++++++++++++-------
drivers/net/wireless/rt2x00/rt73usb.h | 65 +++-
23 files changed, 1615 insertions(+), 982 deletions(-)
next reply other threads:[~2007-09-16 12:07 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 12:17 Ivo van Doorn [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-20 9:52 Please pull 'upstream' branch of rt2x00 Ivo van Doorn
2008-12-02 17:19 Ivo van Doorn
2008-10-29 16:16 Ivo van Doorn
2008-08-29 19:03 Ivo van Doorn
2008-08-04 14:36 Ivo van Doorn
2008-07-19 14:15 Ivo van Doorn
2008-07-18 18:43 Ivo van Doorn
2008-07-19 13:55 ` Ivo van Doorn
2008-06-16 17:58 Ivo van Doorn
2008-06-08 21:41 Ivo van Doorn
2008-05-10 11:37 Ivo van Doorn
2008-05-10 12:48 ` drago01
2008-05-10 13:06 ` Ivo van Doorn
2008-05-10 13:15 ` drago01
2008-05-05 15:23 Ivo van Doorn
2008-05-02 21:04 Scott White
2008-05-02 21:25 ` Ivo van Doorn
2008-05-03 6:19 ` Mattias Nissler
2008-05-03 9:58 ` Ivo van Doorn
2008-05-03 10:18 ` Mattias Nissler
2008-05-03 15:02 ` Ivo van Doorn
2008-05-03 15:27 ` Johannes Berg
2008-05-03 15:38 ` Mattias Nissler
2008-05-03 16:56 ` Ivo van Doorn
2008-05-03 19:29 ` Scott White
2008-05-05 17:31 ` John W. Linville
2008-04-21 17:06 Ivo van Doorn
2008-05-01 8:29 ` Ivo van Doorn
2008-03-09 21:37 Ivo van Doorn
2008-02-25 22:20 Ivo van Doorn
2008-02-17 16:30 Ivo van Doorn
2008-02-10 21:46 Ivo van Doorn
2008-02-03 14:41 Ivo van Doorn
2008-01-06 22:37 Ivo van Doorn
2007-11-27 20:46 Ivo van Doorn
2007-11-27 20:54 ` Ivo van Doorn
2007-11-29 22:26 ` John W. Linville
2007-11-30 9:51 ` Ivo van Doorn
2007-10-27 11:34 Ivo van Doorn
2007-10-13 14:27 Ivo van Doorn
2007-10-06 12:19 Ivo van Doorn
2007-09-25 18:52 Ivo van Doorn
2007-08-19 18:18 Ivo van Doorn
2007-08-02 15:45 Ivo van Doorn
2007-07-31 18:36 Ivo van Doorn
2007-08-01 17:05 ` Ivo van Doorn
2007-07-25 20:49 Ivo van Doorn
2007-07-20 8:11 Ivo van Doorn
2007-07-20 8:13 ` Ivo van Doorn
2007-06-19 18:18 Ivo van Doorn
2007-06-03 12:25 Ivo van Doorn
2007-05-07 14:44 Ivo van Doorn
2007-04-28 20:45 Ivo van Doorn
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=200709161417.40727.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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).