From: Zhu Yi <yi.zhu@intel.com>
To: linux-wireless@vger.kernel.org
Cc: "John W.Linville" <linville@tuxdriver.com>,
Jeff Garzik <jgarzik@pobox.com>
Subject: [PATCH V2] Add iwlwifi wireless drivers
Date: Mon, 27 Aug 2007 13:20:12 +0800 [thread overview]
Message-ID: <1188192012.13078.177.camel@debian.sh.intel.com> (raw)
Hi,
This is the second version of the patch (still against 2.6.23-rc3) adds
the mac80211 based wireless drivers for the Intel PRO/Wireless
3945ABG/BG Network Connection and Intel Wireless WiFi Link AGN (4965)
adapters. You can find it from:
http://intellinuxwireless.org/iwlwifi/v5-Add-iwlwifi-wireless-drivers.patch
I list the changes against the first version I submitted to the list on
8/17 in case you have reviewed the previous version and only want to see
the diff. You can find the overall patch here:
http://intellinuxwireless.org/iwlwifi/iwlwifi-v4_to_v5.patch
and the broken out patches here:
http://intellinuxwireless.org/iwlwifi/patches/iwlwifi-v5-v4-patches/
Ben M Cahill (5):
iwlwifi: remove unused 3945-only struct from 4965 build
iwlwifi: move all uCode API structs into iwl-command.h
iwlwifi: replace iwl_scanstart_notification with
iwl_scanreq_notification
iwlwifi: add struct iwl_card_state_cmd as documentation
iwlwifi: add BSM_DRAM_INST_LOAD definition
Johannes Berg (1):
iwlwifi: remove atheros turbo modes
Johannes Engel (1):
iwlwifi: fix iwl-3945-rs.c typo
Mohamed Abbas (3):
iwlwifi: fix rs_get_best_rate to pick up the right rate
iwlwifi: fix 11n connection problem
iwlwifi: fix aggregation problem
Tomas Winkler (11):
iwlwifi: adding queues_num module parameter
iwlwifi: iwl_get_sta_id AP mode fix
iwlwifi: EEPROM band 5 endianity fix
iwlwifi: AP mode beacon update
iwlwifi: kill iwl_rate union
iwlwifi: simplifying reclaim flow
iwlwifi: removing while loop from iwl_print_hex_dump
iwlwifi: typo fix for CONFIG_IWLWIFI_SPECTRUM_MEASUREMENY
iwlwifi: remove unused code
iwlwifi: rate scaling - up scaling fix
iwlwifi: rate scale quality command fix
Zhu Yi (10):
iwlwifi: replace lock_flags into simpler flags
iwlwifi: split priv->hcmd_lock from priv->lock to protect hcmd
queue
iwlwifi: iwl_mac_set_key cleanup
iwlwifi: fix priv->hcmd_lock uninitialized problem
iwlwifi: Update version iwl-base.c stamp to 0.1.9
iwlwifi: fix iwl_grab_restricted_access return code
iwlwifi: Update version iwl-base.c stamp to 0.1.10
iwlwifi: add a parameter to functions
iwl_rate_control_[un]register
iwlwifi: Update version iwl-base.c stamp to 0.1.11
iwlwifi: fix iwl_send_cmd_async return value bug
next reply other threads:[~2007-08-27 5:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 5:20 Zhu Yi [this message]
2007-08-27 13:10 ` [PATCH V2] Add iwlwifi wireless drivers Christoph Hellwig
2007-08-28 7:25 ` Zhu Yi
2007-08-28 8:50 ` Johannes Berg
2007-08-28 9:07 ` Zhu Yi
2007-08-28 9:28 ` Johannes Berg
2007-08-28 12:28 ` Christoph Hellwig
2007-08-28 13:37 ` Tomas Winkler
2007-08-31 20:55 ` John W. Linville
2007-08-31 22:03 ` Johannes Berg
2007-09-01 10:04 ` Johannes Berg
2007-09-04 2:25 ` Zhu Yi
2007-09-04 14:13 ` Johannes Berg
2007-09-06 1:32 ` Ian Schram
2007-09-06 2:20 ` Larry Finger
2007-09-06 12:00 ` Johannes Berg
2007-09-06 14:04 ` Tomas Winkler
2007-09-06 14:14 ` Johannes Berg
2007-09-06 14:31 ` Tomas Winkler
2007-09-06 14:40 ` Johannes Berg
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=1188192012.13078.177.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).