From: Larry Finger <Larry.Finger@lwfinger.net>
To: Greg KH <gregkh@linuxfoundation.org>, linux-wireless@vger.kernel.org
Subject: Re: Realtek 8821 wireless PCI driver?
Date: Wed, 22 Jan 2014 18:47:29 -0600 [thread overview]
Message-ID: <52E066A1.9010009@lwfinger.net> (raw)
In-Reply-To: <20140120193249.GA25707@kroah.com>
On 01/20/2014 01:32 PM, Greg KH wrote:
> Hi all,
>
> I have a box here with a Realtek 8821 wireless PCI device. We don't
> seem to have a driver upstream for it yet, but there's a huge tarball
> from Realtek on their site.
>
> Has anyone started picking the needed pieces out of the tarball to get
> this merged "properly", or does this need to be done yet?
>
> Hm, I wonder if I should just dump the tarball into staging for now, to
> get my box working, any objections to me doing that?
I have had contact with the Realtek developers regarding a Linux driver for the
RTL8821AE device with PCI ID 10ec:8821. On Dec 10, 2013, they indicated that
there were still 802.11ac problems, and they were not yet ready to release it to
me. I will write them again and check if the driver is now ready, and they just
forgot to send it to me. Once they are ready, they will also be sending me
sample devices.
What is the URL for the driver that you found? I did a quick search on their
site and did not find it.
To answer your question, I certainly would have no objections to your dumping
the driver into staging. I can fix it up there as easily as in my own private
stores. You will, of course, get a lot more intermediate patches, but I think
you have already anticipated that. The PCI group usually send me mac80211-based
drivers, thus the residence in staging may be short, but that is desirable.
Larry
next prev parent reply other threads:[~2014-01-23 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 19:32 Realtek 8821 wireless PCI driver? Greg KH
2014-01-23 0:47 ` Larry Finger [this message]
2014-01-23 2:12 ` Greg KH
2014-01-23 4:13 ` Larry Finger
2014-01-23 4:44 ` Greg KH
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=52E066A1.9010009@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@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 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).