- 06 Feb, 2012 16 commits
-
-
Stanislaw Gruszka authored
Synchronize code with Ralink driver: 2011_0719_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.3_DPO Based on functions: RT33xx_ChipSwitchChannel RT30xx_ChipSwitchChannel Acked-by:
Gertjan van Wingerde <gwingerde@gmail.com> Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Stanislaw Gruszka authored
Synchronize code with Ralink driver: 2011_0719_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.3_DPO Based on functions: RT33xx_ChipSwitchChannel RT30xx_ChipSwitchChannel RT33xx_Init Signed-off-by:
-
Stanislaw Gruszka authored
Synchronize code with Ralink driver: 2011_0719_RT3070_RT3370_RT5370_RT5372_Linux_STA_V2.5.0.3_DPO (functions: RT33xx_ChipSwitchChannel() and RT30xx_ChipSwitchChannel()) Acked-by:
-
Masanari Iida authored
Correct spelling in "suppported" to "supported" in drivers/net/wireless/ipw2x00/libipw_rx.c Signed-off-by:
Masanari Iida <standby24x7@gmail.com> Reviewed-by:
Jesper Juhl <jj@chaosbits.net> Signed-off-by:
-
Johannes Berg authored
This is the second part of the auth/assoc redesign, the mac80211 part. This moves the auth/assoc code out of the work abstraction and into the MLME, so that we don't flip channels all the time etc. The only downside is that when we are associated, we need to drop the association in order to create a connection to another AP, but for most drivers this is actually desirable and the ability to do was never used by any applications. If we want to implement resource reservation with FT-OTA, we'd probably best do it with explicit R-O-C in wpa_s. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
-
Johannes Berg authored
This is needed by mac80211 to keep a reference to a BSS alive for the auth process. Remove the old version of cfg80211_ref_bss() since it's not actually used. Signed-off-by:
-
Johannes Berg authored
To track authenticated state seems to have been a design mistake in cfg80211. It is possible to have out of band authentication (FT), tracking multiple authentications caused more problems than it ever helped, and the implementation in mac80211 is too complex. Remove all this complexity, and let userspace do whatever it wants to, mac80211 can deal with that just fine. Association is still tracked of course, but authentication no longer is. Local auth state changes are thus no longer of value, so ignore them completely. This will also help implement SAE -- asking the driver to do an authentication is now almost equivalent to sending an authentication frame, with the exception of shared key authentication which is still handled completely. Signed-off-by:
-
Johannes Berg authored
The dummy STA support was added because I didn't want to change the driver API at the time. Now that we have state transitions triggering station add/remove in the driver, we only call add once a station reaches ASSOCIATED, so we can remove the dummy station stuff again. While at it, tighten the RX check and accept only port control (EAP) frames from the AP station if it's not associated yet -- in other cases there's no race. Signed-off-by:
-
Johannes Berg authored
Instead of maintaining separate sta_add/sta_remove callsites, implement it in sta_state when the driver has no sta_state implementation. The only behavioural change this should cause is in secure mesh mode: with this the station entries will only be created after the stations are set to AUTH. Given which drivers support mesh, this seems to not be a problem. Signed-off-by:
-
Johannes Berg authored
(based on Eliad's patch) Add a callback to notify the low-level driver whenever the state of a station changes. The driver is only notified when the station is actually in the mac80211 hash table, not for pre-insert state transitions. To allow the driver to replace sta_add/remove calls with this, call extra transitions with the NOTEXIST state. This callback can fail, so we need to be careful in handling it when a station is inserted, particularly in the IBSS case where we still keep the station entry around for mac80211 purposes. Signed-off-by:
Eliad Peller <eliad@wizery.com> Signed-off-by:
-
Johannes Berg authored
This will be used by drivers later if they need to have stations inserted all the time, in mac80211 has no purpose, is never used and sta_state starts out in NONE. Signed-off-by:
-
Johannes Berg authored
If a station couldn't be uploaded to the driver but is still kept (only in IBSS mode) we still shouldn't try to program the keys for it into hardware; fix this bug by skipping the key upload in this case. Signed-off-by:
-
Johannes Berg authored
Setting keys and updating TKIP keys must use the BSS sdata (not AP_VLAN), so we translate. Move the translation into driver-ops wrappers instead of having it inline in the code to simplify the normal code flow. The same can be done for sta_add/remove which already does the translation in the wrapper. Signed-off-by:
-
Johannes Berg authored
Move the station state modification right before insert, this just makes the current code more readable (you can tell that it's before insertion looking at a single screenful of code) right now, but some upcoming changes will require this. Signed-off-by:
-
-
-
- 02 Feb, 2012 24 commits
-
-
Amit Beka authored
Added a check on the direct register access. Checks that the address is in the lower ragnge (0x0-0x2000), which belongs to CSR, HBUS and FH registers. Signed-off-by:
Amit Beka <amit.beka@intel.com> Signed-off-by:
Wey-Yi W Guy <wey-yi.w.guy@intel.com>
-
Johannes Berg authored
smatch correctly complains: iwl-trans-pcie.c +1528 iwl_trans_pcie_start_hw(50) warn: 'trans->irq' was not released on error Fix it. Signed-off-by:
-
Don Fry authored
The routines dealing with the ucode are spread through several files. Move them all to the same file and create a iwl-ucode.h file with the ucode file definitions. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Don Fry authored
There is nothing device specific in the initialization of the bcast_sta_id so move it to the common inititalization routine. Signed-off-by:
-
Don Fry authored
change a comment to be a little more clear Signed-off-by:
-
Emmanuel Grumbach authored
The message was misleading when a queue is deactivated. The fifo number is irrelevant then, so don't print it. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
This trans_ops->stop_hw leaves the RFKILL interrupt enabled, we can call that one instead of enable_rfkill_int. By that, we reduce the numbers of acceesses to the NIC from the upper layers. Signed-off-by:
-
Emmanuel Grumbach authored
The HW revision is now read by the transport layer in its allocation. Signed-off-by:
-
Emmanuel Grumbach authored
Get this information from the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Get this information from the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Get this information from the transport layer which is now in charge of the APM too. Signed-off-by:
-
Emmanuel Grumbach authored
This handler was called from the transport layer only. Merge it to the transport's apm_init. Signed-off-by:
-
Emmanuel Grumbach authored
Now there is only one transport function that launch a specific fw: trans_ops->start_fw. This one replaces trans_ops->start_device and trans_ops->kick_nic. The code that actually loads the fw to the device has been moved to the transport specific code. Signed-off-by:
-
Emmanuel Grumbach authored
This is another clean up of the proble flow. Signed-off-by:
-
Emmanuel Grumbach authored
This handler stops the HW and puts it in low power state. It will allow to clean up the flows in the upper layers. Signed-off-by:
-
Emmanuel Grumbach authored
This is transport related Signed-off-by:
-
Emmanuel Grumbach authored
Kill the trans_ops->prepare_card_hw which is now useless. Signed-off-by:
-
Emmanuel Grumbach authored
This handler will become thicker, reflect its real role now. Signed-off-by:
-
Emmanuel Grumbach authored
This is transport related Signed-off-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Emmanuel Grumbach authored
From now on, the transport layer in charge of providing access to the device. So change all the driver to give a pointer to the transport to all the low level functions that actually access the device. Signed-off-by:
-
Emmanuel Grumbach authored
Most of the accesses to the registers are done from the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
All the bus configuration is now done in the transport allocation fucntion. Signed-off-by:
-
Emmanuel Grumbach authored
Change the way we alloc the transport on the way. Since the transport is allocated from a bus specific area, we can give the bus specific parameters (i.e. pci_dev for PCI) to the transport. This will be useful when the bus layer will be killed. Signed-off-by:
-
