netdev - Re: [RFC/RFT 00/27] Updates for the rtlwifi family of drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Feb 2013 21:04:42 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Joe Perches <joe@...ches.com>
CC:	linville@...driver.com, linux-wireless@...r.kernel.org,
	netdev@...r.kernel.org, jcheung@...e.com, machen@...e.com,
	mmarek@...e.cz
Subject: Re: [RFC/RFT 00/27] Updates for the rtlwifi family of drivers

On 02/25/2013 08:22 PM, Joe Perches wrote:
> On Mon, 2013-02-25 at 18:13 -0600, Larry Finger wrote:
>> This set of patches upgrades drivers rtlwifi, rtl8192c, rtl8192ce, rtl8192se,
>> and rtl8723ae to the state of the vendor driver issued on 2013.02.07. In
>> addition, a new driver for the RTL8188EE chip is added to the kernel.
>>
>> Note: These patches do not upgrade rtl8192de. Those changes will be sent
>> later.
>
> rtl8188e isn't very kernel stylish.
> Looking at it briefly, in fact it's kind of ugly.
>
> Could/should it go into staging?

It is uglier than I had hoped. I was not quite ready to push it yet, but I got 
some pressure from outside, non-Realtek, sources that a kernel version was 
needed. They will, in fact, start their integration from the RFC/RFT version.

The main problem with having it in staging is that we will either have to 
include headers from drivers/net/wireless/rtlwifi/, or duplicate them in the 
drivers/staging/rtl8188ee/ directory where keeping them compatible will be a 
hassle. Neither solution sounds optimum to me.

Larry

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html