Remove empty functions from ieee80211.h
Use values from linux/ieee80211.h
port 12a17d72f7948148b80c0dfa72ea983da33464ba
port a9d8763889737b7e0f83956e093bd48190876044
port 872cfb096d3a009709b56f23f5280a359bbe58e2
port a4bc0fa9ec51008bb494943ec98b4ad836e3a216
port 13e00f8ebded278a7887d98ad65ceabc24f3776a
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.
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.
