Drivers for the rtl8192eu chipset for wireless adapters (D-Link DWA-131 rev E1 included!)
Go to file
2016-08-01 20:40:06 +02:00
core The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
hal Fix file_path symbol conflict with Linux 4.3 2015-11-10 23:04:30 +01:00
include Fix "void value not ignored as it ought to be" errors 2015-11-10 23:06:48 +01:00
os_dep Add TP-Link devices 2016-07-11 16:13:44 -05:00
platform The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
clean The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
ifcfg-wlan0 The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
Kconfig The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
Makefile Update Makefile 2016-01-17 20:31:38 +03:00
README.md Fix speling eror 2016-08-01 20:40:06 +02:00
runwpa The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00
wlan0dhcp The official RTL8192EU linux driver from D-Link Australia 2015-08-18 21:03:11 +02:00

rtl8192eu linux drivers

The official drivers for D-Link DWA-131 Rev E, with patches to keep it working on newer kernels. Also works on Rosewill RNX-N180UBE v2 N300 Wireless Adapter.

NOTE: This is just a "mirror". I have no knowledge about this code or how it works. Expect no support from me or any contributors here. I just think GitHub is a nicer way of keeping track of this than random forum posts and precompiled binaries being sent by email. I don't want someone else to have to spend 5 days of googling and compiling with random patches until it works.

Source for the official drivers

Official drivers were downloaded from D-Link Australia. D-Link USA and the european countries I checked only lists revision A and B. Australia lists all three.

In addition, you can find the contents of this version in the initial commit of this repo: 1387cf623d54bc2caec533e72ee18ef3b6a1db29

Patches

You can see the applied patches, their sources and/or motivation by looking at the commits. The master branch will mostly be kept clean with a single commit per patch, except for Pull Requests. You can review commit by commit and then record the SHA in order to get a safe reference to use. As long as the SHA stays the same you know that what you get has been reviewed by you.

Note that updates to this README will show up as separate commits. I will not mix changes to this file with changes to the code in case you want to mirror this without the README.

Submitting patches

  1. Fork repo
  2. Do your patch in a topic branch
  3. Open a pull request on GH, or send it by email to Magnus Bergmark <magnus.bergmark@gmail.com>.
  4. I'll squash your commits when everything checks out and add it to master.

The original code is copyrighted, but I don't know by whom. The driver download does not contain license information; please open an issue if you are the copyright holder.

Most C files are licensed under GNU General Public License (GPL), version 2.