From: Larry Finger <Larry.Finger@lwfinger.net>
To: anjalik@iwavesystems.com
Cc: backports@vger.kernel.org
Subject: Re: Realtek RTL8192DU Driver and Android LOllipop
Date: Wed, 11 Nov 2015 10:55:31 -0600 [thread overview]
Message-ID: <56437303.6090901@lwfinger.net> (raw)
In-Reply-To: <20151111063247.203429dxmv42uelb@iwavesystems.com>
On 11/11/2015 05:32 AM, anjalik@iwavesystems.com 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 "wol" part is for Wake On Lan. You need to configure the source specially to
use that feature, which I have not tested. I expect that you only need
rtl8192dufw.bin.
The firmware files came from the embedded data in the Realtek standard driver.
When submitting a driver for inclusion in the kernel, having embedded firmware
is frowned upon, thus the reason for extracting it. If you use the driver
version after the firmware was removed, then you need the firmware in the
standard path.
Larry
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-11-11 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 10:49 Realtek RTL8192DU Driver and Android LOllipop anjalik
2015-11-09 16:23 ` Larry Finger
2015-11-11 11:32 ` anjalik
2015-11-11 16:55 ` Larry Finger [this message]
2015-11-11 17:15 ` Larry Finger
2015-11-12 5:40 ` anjalik
2015-11-28 6:58 ` anjalik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56437303.6090901@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=anjalik@iwavesystems.com \
--cc=backports@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.