Hi,
I am currently working with the firmware copied to the
"system/lib/firmware/rtlwifi/" path in the target SD card. So from
your mail I understood that the firmware must not be omitted .(but
still wondering how it worked without the firmware in my initial
testing.)
Thank you for the explanation provided for the querries.
Thanks & Regards,
Anjali.
Quoting Larry Finger <Larry.Finger@xxxxxxxxxxxx>:
On 11/11/2015 05:32 AM, anjalik@xxxxxxxxxxxxxxxx wrote:
Hi,
Thanks for the quick response. The driver is working fine. I
tested Open, WEP
mode and WPA2 is yet to be tested since iwpriv is not working as it is
deprecated. I would like to ask a query regarding the firmware
1.Which is the firmware to be used ,rtl8192dufw.bin or rtl8192dufw_wol.bin ?
I guess the firmware is rtl8192dufw.bin or do both the binaries
together take
care of firmware functionalities.?
In the previous driver which I used,the firmware image was embedded
one. Even
without using the above binaries , everything is working fine. Is it really
required to copy these binaries under system/lib/firmware path.?
I am using Dual Band USB 2.O Wi-Fi Adaptor with RTL8192DU chipset.
The firmware with "wol" in its name is for Wake-On-Lan operation.
The feature requires special configuration, and I have not tested
it. At startup, the driver will load one or the other. If WOL is not
enabled, only the regular firmware will be used. I extracted both
versions before I eliminated the embedded data.
Adding a driver with embedded firmware to the standard kernel is
frowned upon due to the several thousand lines of data. That is the
reason that I extracted the firmware, and converted the driver to
use external firmware. If your version of the driver has been
converted, then you need at least the standard firmware in the
/lib/firmware/ tree.
Larry
--
To unsubscribe from this list: send the line "unsubscribe backports" in
