From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-staging@lists.linux.dev
Subject: Re: kernel BUG in new r8188eu
Date: Mon, 2 Aug 2021 09:40:42 -0500 [thread overview]
Message-ID: <dad0fc63-5419-ac38-3c23-110e4063bbe6@lwfinger.net> (raw)
In-Reply-To: <147993920.vpeT8VCmXh@localhost.localdomain>
On 8/2/21 6:45 AM, Fabio M. De Francesco wrote:
> The following link points to a device that seems to be supported by this
> driver. It is just $4.99, but I'm not sure whether or not they ship to Europe
> (I suppose you're here):
>
> https://www.amazon.com/gp/product/B00L28AN88/ref=ox_sc_act_title_1
>
> About this item:
> * Chipset:RTL8188EU
> * Standard: IEEE 802.11n,IEEE 802.11g, IEEE 802.11b
> * Supports 64/128 bit WEP, WPA encryption
>
> Otherwise, I think that the following uses the same chip as the above.
> However, it costs a little more and, above all else, I'm not really sure if it
> works with r8188eu, since they write that the chip is a Realtek RTL8188EUS
> (please note that final "EUS"):
The RTL8188EUS chips use the same driver as RTL8188EU. In fact, the one I am
using is the EUS variety.
Larry
next prev parent reply other threads:[~2021-08-02 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 19:59 kernel BUG in new r8188eu Larry Finger
2021-07-31 5:37 ` Greg Kroah-Hartman
2021-07-31 16:18 ` Larry Finger
2021-07-31 18:53 ` Fabio Aiuto
2021-07-31 21:54 ` Larry Finger
2021-08-01 6:31 ` Greg Kroah-Hartman
2021-08-01 20:15 ` Larry Finger
2021-08-02 10:36 ` Greg Kroah-Hartman
2021-08-02 11:45 ` Fabio M. De Francesco
2021-08-02 14:38 ` Greg Kroah-Hartman
2021-08-02 14:40 ` Larry Finger [this message]
2021-08-02 15:46 ` Greg Kroah-Hartman
2021-08-02 14:49 ` Larry Finger
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=dad0fc63-5419-ac38-3c23-110e4063bbe6@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=fmdefrancesco@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).