2011/5/3 Larry Finger <Larry.Finger@xxxxxxxxxxxx>: > On 05/03/2011 03:38 PM, Gábor Stefanik wrote: >> >> 2011/5/3 Larry Finger<Larry.Finger@xxxxxxxxxxxx>: >>> >>> On 05/03/2011 03:19 PM, Gábor Stefanik wrote: >>>> >>>> On Tue, May 3, 2011 at 6:45 PM, Larry Finger<Larry.Finger@xxxxxxxxxxxx> >>>> 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? > It just doesn't use mac80211, which is why it needs to be replaced. > > Larry > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
