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  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:   Thu, 22 Jul 2021 15:28:06 +0200
From:   Greg KH <>
To:     Phillip Potter <>
Cc:     Larry Finger <>,
        Dan Carpenter <>,
        Linux Kernel Mailing List <>,, Fabio Aiuto <>
Subject: Re: [PATCH resend] staging: rtl8188eu: move all source files from
 core subdirectory

On Thu, Jul 22, 2021 at 11:44:10AM +0100, Phillip Potter wrote:
> On Wed, 21 Jul 2021 at 20:18, Larry Finger <> wrote:
> >
> > On 7/21/21 1:28 PM, Dan Carpenter wrote:
> > > You're obviously not a Realtek employee, but what are they doing for
> > > wireless drivers these days?
> >
> > You are correct in that I am not a Realtek employee, nor do I have any knowledge
> > of the internals of any of their chips. I do have a close working arrangement
> > with the head of their PCI driver development, and I have gotten free samples of
> > some of their chips. I am a volunteer that is interested in providing drivers
> > for the devices in new laptops with wireless chips that do not yet have a Linux
> > driver in the kernel. I also provide relatively modern drivers for older USB
> > devices through GitHub repos.
> >
> >  From what I know, the PCI group at Realtek is mainly working on new 802.11ac
> > devices, but are leaving some hooks for the USB and SDIO equivalents of those
> > chips (RTL8822BE, RTL8822CE, RTL8821CE, RTL8723DE, and RTL8852AE). These drivers
> > are either in the drivers/net/wireless tree of the kernel, or are under review
> > for such inclusion.
> >
> > I have no current contact with the USB part of their driver development.
> >
> > Larry
> >
> >
> Dear Larry,
> Thank you for this info, it's very useful. Are you saying that in its
> current state the GitHub driver would not even be accepted into
> staging in your opinion? I am happy to continue improving it, but in
> my mind this should probably be done publicly, within the kernel tree.
> Not sure what others think but if there is general consensus then I
> can submit this new version to staging and integrate within build
> framework etc, then we can start improving it and getting it ready to
> move beyond that. Sounds like your driver is further along the path,
> and we should be using it, but I'm interested in what others think of
> course.

If the code looks "better", I have no objection to just adding it to
drivers/staging/ and deleting the existing one here, so that everyone
can work on this together in one single place.

Larry, any objection to that?


greg k-h

Powered by blists - more mailing lists