From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Phillip Potter <phil@philpotter.co.uk>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, Hans de Goede <hdegoede@redhat.com>,
Martin Kaiser <martin@kaiser.cx>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, Jes.Sorensen@gmail.com
Subject: Re: [PATCH] staging: r8188eu: delete driver
Date: Mon, 20 Mar 2023 21:31:07 +0200 [thread overview]
Message-ID: <5428d01b-ec02-df42-3272-a4dcfea2efd9@gmail.com> (raw)
In-Reply-To: <CAFLxGvwKaXviF=5OTtm+pPHwdtXTX6A2e_aRTUraOsxKOL3-4A@mail.gmail.com>
On 14/03/2023 10:06, Richard Weinberger wrote:
> On Sat, Mar 11, 2023 at 1:25 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>>>>> Also the rtl8xxxu driver supports way more devices, and is a fraction of
>>>>> the overall size, making this a much better overall solution.
>>>>>
>>>>> Thanks to the r8188eu developers and maintainers and reviewers over the
>>>>> years, your work allowed Linux users to use their hardware before the
>>>>> real driver was implemented properly.
>
> Both r8188eu and rtl8188eu had support for access point mode but
> rtl8xxxu has none AFAICT.
> Is there something in the pipes to have AP mode supported?
Indeed, rtl8xxxu only supports station mode. I have been thinking about
adding support for AP mode at some point.
prev parent reply other threads:[~2023-03-20 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 13:19 [PATCH] staging: r8188eu: delete driver Greg Kroah-Hartman
2023-03-08 13:26 ` Hans de Goede
2023-03-08 13:44 ` Greg Kroah-Hartman
2023-03-08 14:17 ` Martin Kaiser
2023-03-08 18:22 ` Larry Finger
2023-03-08 20:33 ` Philipp Hortmann
2023-03-08 22:36 ` Michael Straube
2023-03-10 19:08 ` Pavel Skripkin
2023-03-11 10:33 ` Phillip Potter
2023-03-11 12:19 ` Greg Kroah-Hartman
2023-03-14 8:06 ` Richard Weinberger
2023-03-20 19:31 ` Bitterblue Smith [this message]
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=5428d01b-ec02-df42-3272-a4dcfea2efd9@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=Jes.Sorensen@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=patches@lists.linux.dev \
--cc=phil@philpotter.co.uk \
--cc=richard.weinberger@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.