- 29 Feb, 2008 40 commits
-
-
Ivo van Doorn authored
Don't wildly pass any number for num_rates to rt2x00lib, instead pass which type of rates are supported (CCK, OFDM). Same for num_modes but then for the 2GHZ and 5GHZ band. This makes the interface look much nicer and makes extending it later easier. Signed-off-by:
Ivo van Doorn <IvDoorn@gmail.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Ivo van Doorn authored
The dscape stack was renamed to mac80211 a long time ago, we are long overdue with fixing all comments to reflect this. Signed-off-by:
-
Ivo van Doorn authored
Specifications indicate the TSF registers are read-only, so there is no point in writing 0 to those registers. As far as I know there isn't another way to reset the TSF registers. So removing these callbacks will notify mac80211 about the lack of support. Signed-off-by:
-
Ivo van Doorn authored
As Adam Baker reported the DMA address for the descriptor base was incorrectly initialized in the PCI drivers. Instead of the DMA base for the descriptor, the DMA base for the data was passed resulting in a broken TX/RX state for PCI drivers. Signed-off-by:
-
Ivo van Doorn authored
The ACK_CTS frame is a control frame, this means dropping the frame depends on the FIF_CONTROL flag for filtering. This also fixes an obvious typo in register definition. Signed-off-by:
-
Ivo van Doorn authored
This adds a new flag for the skb_frame_desc structure which is used to tag rts/cts frames that are generated by the driver. Through the tag we can recognize frames we have generated ourselves, so we don't report their tx status to mac80211. This patch is based on the original patch by Mattias Nissler <mattias.nissler@gmx.de>. Signed-off-by:
-
Ivo van Doorn authored
mac80211 sends the txpower to use during config(), we already store it in the rt2x00_dev structure. When writing the descriptor correctly initialize the txpower field with this value to make sure all frames are send out with the correct tx power. Signed-off-by:
-
Ivo van Doorn authored
Signed-off-by:
-
Ivo van Doorn authored
When the radio is being disabled we should also kill the guardian urb which could still be pending in the device. Signed-off-by:
-
Ivo van Doorn authored
Simplify the way rt2x00 assigns new objects to the rt2x00lib module. This saves a few if statements and overall does this looks much nicer. Signed-off-by:
-
Ivo van Doorn authored
As Adam Baker reported the queue->qid was not initialized correctly. The QID_AC_BE was assigned to the RX ring. This will move the queue initialization into a seperate function and makes sure that all queues are initialized directly with the correct qids. Signed-off-by:
-
Ivo van Doorn authored
skbdesc->data_len was not initialized correctly in rt2x00pci, rt2x00usb, rt2500usb and rt73usb. The value was set to queue->data_size which means that the incorrect frame size was pased to the upper layers. Correctly base the value on either the skb->len, or the rx frame size passed to the driver by the device. Signed-off-by:
-
Ivo van Doorn authored
The second eeprom recovery message is about the RSSI offset for ieee802.11 A. Signed-off-by:
-
Ivo van Doorn authored
Rename "frame" folder to "queue" folder, add extra file to this folder which contains statistics about all hardware queues. This will help debugging and spotting problems in the queue indexing system. Signed-off-by:
-
Ivo van Doorn authored
Call rt2x00_config_intf() outside of the spinlock context since the call will sleep for USB drivers. By using the ieee80211_if_conf values as arguments we make keep access tp rt2x00_intf thread safe even without the lock. Signed-off-by:
-
Ivo van Doorn authored
The csr_cache and csr_addr pointers are both the same size and they are never used both by the same driver. This makes them a nice candidate for an union. We could merge into 1 pointer, but that would either upset sparse, or require a lot of __force casts. Signed-off-by:
-
Ivo van Doorn authored
Select CONFIG_NEW_LEDS before selecting the other LED config options. This fixes a link error when NEW_LEDS was disabled. Signed-off-by:
-
Adam Baker authored
When calculating the offset to add to the queue entry base to get the individual entry's private data area the base address must be treated as a char * not a struct queue_entry so we can do byte oriented pointer arithmetic with it. Signed-off-by:
Adam Baker <linux@baker-net.org.uk> Signed-off-by:
-
Ivo van Doorn authored
Remove the last remnants of the MGMT ring initialization from rt61pci.ko Signed-off-by:
-
Ivo van Doorn authored
Remove the debug messages regarding initialization from EEPROM. The values are vendor specific, and are not really needed for debug purposes. If they ever become usefull we still have access to them through debugfs which also prints the exact same values... Signed-off-by:
-
Ivo van Doorn authored
Be more strict when using the queue_entry_priv_pci_rx and queue_entry_priv_pci_tx structures. Only use a particular type that matches the queue type. When freeing the DMA the priv_tx->data and priv_tx->dma was used. This is incorrect since the start of the DMA was in fact the priv_tx->desc pointer. Instead of recalculating the dma_addr_t for the DMA start this patch will swap the data and descriptor part of the allocated memory. Signed-off-by:
-
Randy Dunlap authored
Michael Büker <m.bueker@berlin.de> reports that the RT2x00 drivers are not indented as they should be, so use proper dependencies to make them be indented as expected. Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Ack-by:
-
Matthias Kaehlcke authored
The semaphore wpa_sem is used as mutex, convert it to the mutex API Signed-off-by:
Matthias Kaehlcke <matthias@kaehlcke.net> Acked-by:
Luis R. Rodriguez <mcgrof@winlab.rutgers.edu> Signed-off-by:
-
Matthias Kaehlcke authored
The semaphore stats_sem is used as mutex, convert it to the mutex API Signed-off-by:
-
Matthias Kaehlcke authored
The semaphore acl->sem is used as mutex, convert it to the mutex API Signed-off-by:
-
Marcin Slusarz authored
replace all: little_endian_variable = cpu_to_leX(leX_to_cpu(little_endian_variable) + expression_in_cpu_byteorder); with: leX_add_cpu(&little_endian_variable, expression_in_cpu_byteorder); generated with semantic patch Signed-off-by:
Marcin Slusarz <marcin.slusarz@gmail.com> Cc: Zhu Yi <yi.zhu@intel.com> Signed-off-by:
Reinette Chatre <reinette.chatre@intel.com> Signed-off-by:
-
Daniel Drake authored
Most wireless drivers load their firmware at interface open time, which generally occurs after the filesystem is available. However, the ipw drivers load their firmware at probe time because firmware is required to read the device MAC address. When built-in, probe happens before the filesystem is available, hence device init will only complete successfully if the user has made special arrangements (including firmware plus a loader in the initramfs). Note all this in the kconfig help text for both drivers. Signed-off-by:
Daniel Drake <dsd@gentoo.org> Signed-off-by:
-
Christian Lamparter authored
This trival one-liner changes the QoS initialization values to match IEEE 802.11e defaults. Signed-off-by:
Christian Lamparter <chunkeey@web.de> Acked-by:
Johannes Berg <johannes@sipsolutions.net> Signed-off-by:
-
Michael Buesch authored
We must not clear the FIF_BCN_PRBRESP_PROMISC bit in the new_flags. The zd-driver does support sending beacons and probe responses to the host. What the flag does is say "Send me all beacons and probe responses". And we actually do that. We always do that, so we ignore the case when the bit is disabled. But that is fine. But we must not clear the flag, as that tells mac80211 that we do not support passing beacons and probe responses to the stack. And that's not true. Signed-off-by:
Michael Buesch <mb@bu3sch.de> Acked-by:
-
Javier Cardona authored
Trial and error reveals that CR_ZD1211B_TX_PWR_CTL* do not affect the transmission power. Instead these registers seem to control the contention windows limits for different QoS access categories. Signed-off-by:
Javier Cardona <javier@cozybit.com> Signed-off-by:
-
Tomas Winkler authored
This patch removes twice defined CSR register. It was confusing Signed-off-by:
Tomas Winkler <tomas.winkler@intel.com> Signed-off-by:
-
Johannes Berg authored
This doesn't really need to be a full int variable since it's just a flag to indicate a PS-poll is in progress. Signed-off-by:
-
Johannes Berg authored
Having the full RX timestamp in beacons is necessary for IBSS merge to work properly so extend the 16-bit timestamp to the full 64 bits for beacon frames (as well as when monitor mode is active.) Signed-off-by:
Stefano Brivio <stefano.brivio@polimi.it> Signed-off-by:
-
Johannes Berg authored
This fixes packet transmission of packets without RTS/CTS. Signed-off-by:
-
Bruno Randolf authored
enable IBSS cell merging. if an IBSS beacon with the same channel, same ESSID and a TSF higher than the local TSF (mactime) is received, we have to join its BSSID. while this might not be immediately apparent from reading the 802.11 standard it is compliant and necessary to make IBSS mode functional in many cases. most drivers have a similar behaviour. * move the relevant code section (previously only containing debug code) down to the end of the function, so we can reuse the bss structure. * we have to compare the mactime (TSF at the time of packet receive) rather than the current TSF. since mactime is defined as the time the first data symbol arrived we add the time until byte 24 where the timestamp resides, since this is how the beacon timestamp is defined. as some some drivers are not able to give a reliable mactime we fall back to use the current TSF, which will be enough to catch most (but not all) cases where an IBSS merge is necessary. * in IBSS mode we want to allow beacons to override probe response info so we can correctly do merges. * we don't only configure beacons based on scan results, so change that message. * to enable this we have to let all beacons thru in IBSS mode, even if they have a different BSSID. Signed-off-by:
Bruno Randolf <bruno@thinktube.com> Acked-by:
-
Bruno Randolf authored
this moves ieee80211_sta_join_ibss() up for the next patch (ibss merge). Signed-off-by:
-
Bruno Randolf authored
define mactime as the time when the first data symbol arrived at the HW. the old definition was questionable because 802.11 defines timestamp only for beacon and probe response frames, and there it means the timestamp field. a stricter definition of mactime is necessary for correct merging of IBSS. note that it is up to the driver to convert whatever its hardware returns to this definition. unfortunately we don't know for example when atheros hardware takes its rx timestamp exactly :( Signed-off-by:
-
Reinette Chatre authored
iwl_rx_card_state_notif is named iwl3945_rx_card_state_notif and iwl4965_rx_card_state_notif in the two iwlwifi drivers. Signed-off-by:
-
Jiri Slaby authored
At least type check the ATH5K_TRACE paramter on !ATH5K_DEBUG configs. Signed-off-by:
Jiri Slaby <jirislaby@gmail.com> Cc: Nick Kossifidis <mickflemm@gmail.com> Acked-by:
-
S.Çağlar Onur authored
The functions time_before, time_before_eq, time_after, and time_after_eq are more robust for comparing jiffies against other values. So following patch implements usage of the time_after() macro, defined at linux/jiffies.h, which deals with wrapping correctly Cc: linux-wireless@vger.kernel.org Signed-off-by:
S.Çağlar Onur <caglar@pardus.org.tr> Signed-off-by:
-
