mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] staging: Add rtl8821ce PCIe WiFi driver
Date: Wed, 15 May 2019 21:06:44 +0800	[thread overview]
Message-ID: <63833AA2-AC8B-4EEA-AF36-EF2A9BFD4F9F@canonical.com> (raw)
In-Reply-To: <20190515123319.GA435@kroah.com>

at 20:33, Greg KH <gregkh@linuxfoundation.org> wrote:

> On Wed, May 15, 2019 at 07:54:58PM +0800, Kai-Heng Feng wrote:
>> at 19:40, Greg KH <gregkh@linuxfoundation.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?

“They” refers to Realtek.
It’s their plan so I can’t really answer that on behalf of Realtek.

>
>>>> 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?

Yes. They use one single driver to support different SoCs, different  
architectures and even different OSes.
That’s why it’s a mess.

> Why not use the ones we already have?

It’s virtually impossible because Realtek’s mega wifi driver uses tons of  
#ifdefs, only one chip can be selected to be supported at compile time.

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

Realtek plans to add the support in 2020, if everything goes well.
Meanwhile, many users of HP and Lenovo laptops are using out-of-tree  
driver, some of them are stuck to older kernels because they don’t know how  
to fix the driver. So I strongly think having this in kernel is beneficial  
to many users, even it’s only for a year.

Kai-Heng

>
> thanks,
>
> greg k-h



  reply	other threads:[~2019-05-15 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190515112401.15373-1-kai.heng.feng@canonical.com>
2019-05-15 11:40 ` Greg KH
2019-05-15 11:54   ` Kai-Heng Feng
2019-05-15 12:33     ` Greg KH
2019-05-15 13:06       ` Kai-Heng Feng [this message]
2019-05-15 15:58         ` Larry Finger
2019-05-15 16:39         ` Greg KH
2019-05-15 17:40           ` Kai-Heng Feng
2019-05-15 17:48             ` Greg KH
2019-05-15 17:46           ` Joe Perches

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=63833AA2-AC8B-4EEA-AF36-EF2A9BFD4F9F@canonical.com \
    --to=kai.heng.feng@canonical.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®