From: Larry Finger <Larry.Finger@lwfinger.net>
To: santosh.adari@wipro.com
Cc: wlanfae@realtek.com, pj.chiang@realcomtec.com,
babu.vba@wipro.com, manjunathan.padua@wipro.com,
wireless <linux-wireless@vger.kernel.org>,
driverdevel <devel@driverdev.osuosl.org>
Subject: Re: RTL8712u driver information.
Date: Fri, 22 Jun 2012 11:13:52 -0500 [thread overview]
Message-ID: <4FE499C0.8010902@lwfinger.net> (raw)
In-Reply-To: <5379C41A9569B24380950BE8B32390D864245DB2@BLR-EC-MBX5.wipro.com>
On 06/22/2012 08:50 AM, santosh.adari@wipro.com wrote:
> Hi All,
>
> I am using realtek driver version “v2.6.6.0.20110401” for RTL8712 chipset with
> linux 2.6.29 kernel version. I have built realtek driver as module and using the
> driver.
>
> I observe in linux 3.2 version there is realtek driver version “v7_0.20100831”
> for RTL8712 chipset.
Messages of this type should *always* be addressed to a general mailing list,
and not only to module authors. Without such a general audience, you are asking
for private consulting, but not offering to pay for it. I have added the
wireless and driver-development mailing lists to the Cc's here.
>
> Queries:
>
> 1.which is the latest driver among these drivers?
Obviously, 20110401 is after 20100831. The version number inside the kernel is
meaningless. The Linux kernel is regularly updated without changing that version.
> 2.What is the difference between these version of drivers?
The kernel version is built into the kernel!
> 3.Is the driver in linux 3.2 taken from relatek and integrated to
> drivers/staging/ of linux 3.2 ?
The Realtek driver was added to drivers/staging in the kernel in August 2010 for
kernel 2.6.37 and was based on the latest version available at that time;
however, as the Realtek version did not work on 64-bit systems, there were many
changes. As Realtek has released later versions, the kernel driver has been
updated to include those changes. For a while, I was feeding additional changes
back to Realtek; however, those patches were ignored, thus I stopped.
To see what the differences are, you would need to carefully analyze the output
of a "diff" command, and the pertinent sections of the "git log" output. Other
than the kernel version working on 64-bit kernels, I do not know what they are.
Other changes also include fixes for oops, etc.
Larry
parent reply other threads:[~2012-06-22 16:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5379C41A9569B24380950BE8B32390D864245DB2@BLR-EC-MBX5.wipro.com>]
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=4FE499C0.8010902@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=babu.vba@wipro.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manjunathan.padua@wipro.com \
--cc=pj.chiang@realcomtec.com \
--cc=santosh.adari@wipro.com \
--cc=wlanfae@realtek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).