From: Larry Finger <Larry.Finger@lwfinger.net>
To: Gauss Frank <gaussfrank@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-wireless@vger.kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jerry chuang <wlanfae@realtek.com>,
Florian Schilhabel <florian.c.schilhabel@googlemail.com>
Subject: Re: Hi,Linus Torvalds. There's a problem in r8192u driver in Linux new kernel.
Date: Thu, 12 Aug 2010 11:36:11 -0500 [thread overview]
Message-ID: <4C6422FB.8040204@lwfinger.net> (raw)
In-Reply-To: <AANLkTin3qXSbuWejTGJzz6cO6fycK4HqU4gn4gF1wEdp@mail.gmail.com>
Gauss,
What is the USB ID for your device. The reason I'm asking is that Florian and I
have been working on porting a new vendor driver for the 8192u devices. The plan
is to submit this to staging. At the moment, it has been tested with big- and
little-endian, and 32- and 64-bit systems. Everything is working except for
suspend and resume.
If your device is one of those that Realtek says works with this driver, and you
are willing to build a kernel from scratch, I will send you the URL for a git
tree containing it. That will have to be done privately as I'm still waiting for
Realtek to approve the copyright statements in the code. It is GPL'ed, so I do
not expect any difficulties, but their lawyers have to sign off.
Larry
next prev parent reply other threads:[~2010-08-12 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=1NaRKc8QrQBGwU+c_17D86_Cqu9MopR_rso0H@mail.gmail.com>
2010-08-12 16:06 ` Hi,Linus Torvalds. There's a problem in r8192u driver in Linux new kernel Linus Torvalds
2010-08-12 16:19 ` Greg KH
[not found] ` <76C6BFFEAAA24679B55CBB186C084833@cnfaec24b87a3f>
2010-08-20 0:15 ` Greg KH
2010-08-20 2:58 ` Larry Finger
2010-08-20 3:31 ` Greg KH
2010-08-12 16:36 ` Larry Finger [this message]
2010-09-18 4:58 ` Paul Thomas
[not found] ` <AANLkTi=SL_tCO4k071KZxawch90NqdnGFMaqy_uqPTHA@mail.gmail.com>
2010-09-18 20:18 ` Paul Thomas
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=4C6422FB.8040204@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bzolnier@gmail.com \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gaussfrank@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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).