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]
Message-ID: <20190515123319.GA435@kroah.com>
Date:   Wed, 15 May 2019 14:33:19 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc:     devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
        Larry Finger <Larry.Finger@...inger.net>
Subject: Re: [PATCH] staging: Add rtl8821ce PCIe WiFi driver

On Wed, May 15, 2019 at 07:54:58PM +0800, Kai-Heng Feng wrote:
> at 19:40, Greg KH <gregkh@...uxfoundation.org> wrote:
> 
> > On Wed, May 15, 2019 at 07:24:01PM +0800, Kai-Heng Feng wrote:
> > > The rtl8821ce can be found on many HP and Lenovo laptops.
> > > Users have been using out-of-tree module for a while,
> > > 
> > > The new Realtek WiFi driver, rtw88, will support rtl8821ce in 2020 or
> > > later.
> > 
> > Where is that driver, and why is it going to take so long to get merged?
> 
> rtw88 is in 5.2 now, but it doesn’t support 8821ce yet.
> 
> They plan to add the support in 2020.

Who is "they" and what is needed to support this device and why wait a
full year?

> > > 296 files changed, 206166 insertions(+)
> > 
> > Ugh, why do we keep having to add the whole mess for every single one of
> > these devices?
> 
> Because Realtek devices are unfortunately ubiquitous so the support is
> better come from kernel.

That's not the issue here.  The issue is that we keep adding the same
huge driver files to the kernel tree, over and over, with no real change
at all.  We have seen almost all of these files in other realtek
drivers, right?  Why not use the ones we already have?

But better yet, why not add proper support for this hardware and not use
a staging driver?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ