linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Walter Goldens <goldenstranger@yahoo.com>,
	John W Linville <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	chaoming_li@realsil.com.cn
Subject: Re: [PATCH 00/12] rtlwifi: rtl8192se: Merge new driver
Date: Tue, 03 May 2011 16:35:06 -0500	[thread overview]
Message-ID: <4DC0750A.50806@lwfinger.net> (raw)
In-Reply-To: <BANLkTim89BHU-0P6TkepLgDBPNfEhiaB-w@mail.gmail.com>

On 05/03/2011 04:09 PM, Gábor Stefanik wrote:
> 2011/5/3 Larry Finger<Larry.Finger@lwfinger.net>:
>> On 05/03/2011 03:38 PM, Gábor Stefanik wrote:
>>>
>>> 2011/5/3 Larry Finger<Larry.Finger@lwfinger.net>:
>>>>
>>>> On 05/03/2011 03:19 PM, Gábor Stefanik wrote:
>>>>>
>>>>> On Tue, May 3, 2011 at 6:45 PM, Larry Finger<Larry.Finger@lwfinger.net>
>>>>>   wrote:
>>>>>>
>>>>>> On 05/03/2011 10:59 AM, Walter Goldens wrote:
>>>>>>>
>>>>>>>> This set of patches introduces a driver for the RTL8192SE PCI
>>>>>>>> devices.
>>>>>>>
>>>>>>> Any estimates on the *SU driver? :)
>>>>>>
>>>>>> Now that rtl8192se is submitted, I will start work on the driver for
>>>>>> the
>>>>>> RTL8192DE devices. After that will be the RTL8191SU. It has lower
>>>>>> priority
>>>>>> because r8712u from staging handles those devices. It is not based on
>>>>>> mac80211, but it works.
>>>>>
>>>>> Again, may I remind you that the preferred behavior in the Linux world
>>>>> is release-early, release-often? :-)
>>>>
>>>> That I know, but "code first" still applies. If the comparison between
>>>> rtl8192ce and rtl8192cu has any validity for the rtl8192s varieties,
>>>> roughly
>>>> half of this driver will be shared. In addition, we do have all the USB
>>>> plumbing in place, but we are still talking about a few thousand lines of
>>>> code. At last contact, Realtek has no interest in this project, thus I
>>>> will
>>>> be on my own.
>>>>
>>>> Larry
>>>
>>> I do not mean immediately submitting everything for inclusion -
>>> however, a publicly accessible Git tree would be nice. A non-rtlwifi,
>>> badly coded but functional and GPL-compatible driver is still better
>>> than having to use ndiswrapper/load a binary blob.
>>
>> We are in better shape than having to use ndiswrapper or any non-GPL code.
>> The r8712u driver in staging is for the RTL8192SU, and it works perfectly
>> well.
>
> What about RTL8192DE?

I'm working on that one today. If all goes well, it might make 2.6.40, but that 
may be a little tight on time. Publish early and often does apply here.

Larry

  reply	other threads:[~2011-05-03 21:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 14:47 [PATCH 00/12] rtlwifi: rtl8192se: Merge new driver Larry Finger
2011-05-03 15:01 ` Borislav Petkov
2011-05-03 20:03   ` Larry Finger
2011-05-04 17:01     ` Borislav Petkov
2011-05-04 17:20       ` Larry Finger
2011-05-04 18:06         ` Borislav Petkov
2011-05-04 19:15           ` Larry Finger
2011-05-03 15:59 ` Walter Goldens
2011-05-03 16:45   ` Larry Finger
2011-05-03 20:19     ` Gábor Stefanik
2011-05-03 20:33       ` Larry Finger
2011-05-03 20:38         ` Gábor Stefanik
2011-05-03 20:56           ` Larry Finger
2011-05-03 21:09             ` Gábor Stefanik
2011-05-03 21:35               ` Larry Finger [this message]
2011-06-21 12:49             ` r8712u driver for the rtl8192su chip Ali Bahar
2011-06-21 22:08               ` Larry Finger
2011-06-22  1:00                 ` Ali Bahar
2011-06-22  2:03                   ` Julian Calaby
2011-06-22  2:12                     ` Gábor Stefanik
2011-06-22  2:46                       ` Ali Bahar
2011-06-22  2:39                     ` Ali Bahar
2011-06-22  2:34                   ` Larry Finger
2011-06-22  2:56                     ` Ali Bahar
2011-06-22  3:09                       ` Larry Finger
2011-06-22  3:17                         ` Ali Bahar
2011-06-27  7:23                         ` Ali Bahar
2011-07-02 17:09                           ` Larry Finger
2011-07-03  1:06                             ` Ali Bahar
2011-07-03  1:24                               ` Larry Finger
2011-07-03  1:47                                 ` Ali Bahar
2011-07-15 17:11                               ` [PATCH 0/2] staging: r8712u: Most return-values changed from -1 to Ali Bahar
2011-07-15 17:11                                 ` [PATCH 1/2] staging: r8712u: Most return-values changed from -1 to proper errno macros Ali Bahar
2011-07-15 21:00                                   ` Larry Finger
2011-07-16  3:21                                     ` Ali Bahar
2011-07-16  9:23                                       ` Kalle Valo
2011-07-16 10:50                                         ` Ali Bahar
2011-07-16 11:44                                           ` Kalle Valo
2011-07-16 11:55                                             ` Ali Bahar
2011-07-15 17:11                                 ` [PATCH 2/2] staging: r8712u: checkpatch errors: trailing whitespace on 2 lines Ali Bahar

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=4DC0750A.50806@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=chaoming_li@realsil.com.cn \
    --cc=goldenstranger@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netrolller.3d@gmail.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).