From: Arnd Bergmann <arnd@arndb.de>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Stefan Lippers-Hollmann <s.l-h@gmx.de>,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@codeaurora.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
netdev@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mateusz Kulikowski <mateusz.kulikowski@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Andrea Merello <andrea.merello@gmail.com>
Subject: Re: [PATCH 2/3] staging/rtl8192e: use s8 instead of char
Date: Fri, 22 Jul 2016 21:47:10 +0200 [thread overview]
Message-ID: <7894919.vMsHjmmMb1@wuerfel> (raw)
In-Reply-To: <wrfjoa5phop3.fsf@redhat.com>
On Friday, July 22, 2016 7:55:36 AM CEST Jes Sorensen wrote:
> Stefan Lippers-Hollmann <s.l-h@gmx.de> writes:
> > Hi
> >
> > On 2016-07-20, Arnd Bergmann wrote:
> >> On Wednesday, July 20, 2016 11:33:43 AM CEST Jes Sorensen wrote:
> >> > Arnd Bergmann <arnd@arndb.de> writes:
> >> > > On Wednesday, July 20, 2016 7:25:19 AM CEST Jes Sorensen wrote:
> >> > >> Arnd Bergmann <arnd@arndb.de> writes:
> > [...]
> >> Yes, I was just agreeing here that it's not worth doing that one.
> >> As far as I can see, the evolution of these devices is
> >>
> >> RTL81xxU (2008)
> >> RTL81xxSU (2009)
> >> RTL81xxCU (2010)
> >
> > There is also RTL81xxDU, apparently from 2011, a dualband device
> > coming in several variants (single MAC + single PHY, double MAC +
> > double PHY and double PHY); e.g. 0bda:8194 (single PHY + single MAC).
Right. In my list above I tried to have just the ones that seem
to each be 100% supersets of previous generations replacing the
earlier ones, which isn't true for RTL81xxDU as RTL81xxEU
reverts to single PHY.
> > While probably not overly common, it was/ is (hardware-wise) a pretty
> > interesting device due to its support for 5 GHz[1] - actually I hoped
> > it to be a (supported-) RTL8192CU variant when I bought it.
> > Unfortunately no driver[2] made it to staging or the proper kernel.
>
> I actually have one of those in my USB dongle box, but as you say, not
> overly common so not sure if/when I'll get to it.
>
> Adding 8192du support for 2.4GHz to rtl8xxxu probably wouldn't be too
> complicated.
My guess is that these devices have largely been replaced by
802.11ac devices on the market, and whoever has one of the old ones
probably bought it because of the 5GHz support, so adding 2.4GHz-only
support for it may not help all that much either.
Arnd
next prev parent reply other threads:[~2016-07-22 19:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 15:33 [PATCH 1/3] rtlwifi: don't add include path for rtl8188ee Arnd Bergmann
2016-07-19 15:33 ` [PATCH 2/3] staging/rtl8192e: use s8 instead of char Arnd Bergmann
2016-07-19 15:46 ` Jes Sorensen
2016-07-19 15:53 ` Arnd Bergmann
2016-07-19 16:05 ` Jes Sorensen
2016-07-20 8:25 ` Arnd Bergmann
2016-07-20 11:25 ` Jes Sorensen
2016-07-20 14:25 ` Larry Finger
2016-07-20 15:12 ` Arnd Bergmann
2016-07-20 15:33 ` Jes Sorensen
2016-07-20 16:00 ` Arnd Bergmann
2016-07-22 2:39 ` Stefan Lippers-Hollmann
2016-07-22 11:55 ` Jes Sorensen
2016-07-22 19:47 ` Arnd Bergmann [this message]
2016-07-22 20:51 ` Stefan Lippers-Hollmann
2016-07-19 15:33 ` [PATCH 3/3] staging/rtl8192u: " Arnd Bergmann
2016-07-19 15:47 ` Jes Sorensen
2016-07-19 18:17 ` [1/3] rtlwifi: don't add include path for rtl8188ee Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2016-07-20 15:06 [PATCH 2/3] staging/rtl8192e: use s8 instead of char Xose Vazquez Perez
2016-07-20 15:48 ` Christian Lamparter
2016-07-20 15:13 [PATCH 1/3] staging/rtl8192u: " Arnd Bergmann
2016-07-20 15:26 ` [PATCH 2/3] staging/rtl8192e: " Arnd Bergmann
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=7894919.vMsHjmmMb1@wuerfel \
--to=arnd@arndb.de \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=andrea.merello@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mateusz.kulikowski@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.l-h@gmx.de \
/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).