Commit Graph

12 Commits

Author SHA1 Message Date
Larry Finger
1fcfef2e07 Remove rtw_yield_os()
This wrapper is just a call to yield().

Link: https://lore.kernel.org/r/20210805192644.15978-1-Larry.Finger@lwfinger.net
2021-10-11 10:44:02 +02:00
Larry Finger
51e1f13a91 Remove all calls to _rtw_spinlock_free()
This routine is empty, thus all calls to it can be removed.

Link: https://lore.kernel.org/r/20210805183717.23007-4-Larry.Finger@lwfinger.net
2021-10-11 10:44:02 +02:00
Larry Finger
d7c3737cd5 Remove wrappers for atomic operations
These wrappers were useful when this driver had the hooks for Windows,
but are no longer needed.

Link: https://lore.kernel.org/r/20210802192721.23110-4-Larry.Finger@lwfinger.net
2021-10-11 10:44:02 +02:00
Greg Kroah-Hartman
ac1790da7c remove rtw_mfree2d() function
It is just a wrapper around kfree(), so remove it and just call kfree()
instead.

Adaptation of: https://lore.kernel.org/r/20210730092417.1014392-7-gregkh@linuxfoundation.org
2021-10-11 10:44:01 +02:00
yagoplx
e527c271c9 Fix typo in MTPC 2020-06-19 15:16:02 -03:00
yagoplx/y
666bfeb0f0 Add AP info, Add Compile-Time Transmit Power Fixing & Boost
Turns out these devices can serve as really decent access points.
Adding txpower control info as well. See my other PR.

This is in a separate PR because the readme instructed to do so.

Update README.md

Move my lines more to the bottom

 Implement simple transmit power boost and fixed setting

Source: 80b9bc47b3

Turns out the "higher levels" of this driver are not actually able to affect the device's physical power output, like via cfg80211, yet.
After some extensive testing I finally found the code responsible for setting the device's power and added some compile-time
tunables to influence it. For example here we give the transmit power index a tiny boost of two, which can be changed by the user via the source.

This is as far as my skills go so if you want to try and make this accessible to iw and iwconfig please give it a go.
Note that this will take an index between 1 (min power the device can put out) and 63 (max power the device can put out). I have no idea what these values actually translate to in dBm, but setting the override to max, 63, on my rtl card really gave range a boost.

Add AP and TXPOWER CONTROL info

Turns out these devices can serve as really decent access points.
Adding txpower control info as well. See my other PR.

This is in a separate PR because the readme instructed to do so.

Update README.md

Move my lines more to the bottom

 Implement simple transmit power boost and fixed setting

Source: 80b9bc47b3

Turns out the "higher levels" of this driver are not actually able to affect the device's physical power output, like via cfg80211, yet.
After some extensive testing I finally found the code responsible for setting the device's power and added some compile-time
tunables to influence it. For example here we give the transmit power index a tiny boost of two, which can be changed by the user via the source.

This is as far as my skills go so if you want to try and make this accessible to iw and iwconfig please give it a go.
Note that this will take an index between 1 (min power the device can put out) and 63 (max power the device can put out). I have no idea what these values actually translate to in dBm, but setting the override to max, 63, on my rtl card really gave range a boost.

Add AP and TXPOWER CONTROL info

Turns out these devices can serve as really decent access points.
Adding txpower control info as well. See my other PR.

This is in a separate PR because the readme instructed to do so.

Update README.md

Move my lines more to the bottom

 Implement simple transmit power boost and fixed setting

Source: 80b9bc47b3

Turns out the "higher levels" of this driver are not actually able to affect the device's physical power output, like via cfg80211, yet.
After some extensive testing I finally found the code responsible for setting the device's power and added some compile-time
tunables to influence it. For example here we give the transmit power index a tiny boost of two, which can be changed by the user via the source.

This is as far as my skills go so if you want to try and make this accessible to iw and iwconfig please give it a go.
Note that this will take an index between 1 (min power the device can put out) and 63 (max power the device can put out). I have no idea what these values actually translate to in dBm, but setting the override to max, 63, on my rtl card really gave range a boost.
2020-06-18 18:04:01 -03:00
Carlos Garces
1d807f14d8 Add version v5.6.4 2019-11-13 22:12:20 +01:00
Maxim Buzdalov
30ba4de6ef Enable power management (hopefully).
I mean, it does not crash, but I have no hardware to tell
whether the output power actually changes.
2019-08-22 02:02:40 +03:00
masterzorag
8162bfd881 silence two RT_TRACE
they are flooding logs, keep them commented for now
2017-05-27 15:03:28 +02:00
CGarces
3d6c7de21a Updated to 4.4.1 2017-05-11 20:49:39 +02:00
CGarces
9dde4572b4 Updated to v4.3.8_12406.20140929 2017-05-11 20:38:48 +02:00
Magnus Bergmark
1387cf623d
The official RTL8192EU linux driver from D-Link Australia
Version information: 20140812_rtl8192EU_linux_v4.3.1.1_11320
  2014-08-12
  version 4.3.1.1_11320
Source:
  ftp://files.dlink.com.au/products/DWA-131/REV_E/Drivers/DWA-131_Linux_driver_v4.3.1.1.zip

This version does not currently work on newer kernels, but it does
contain USB ID 2001:3319, which a lot of other repos in GitHub does not.
2015-08-18 21:03:11 +02:00