From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754164AbcGVUwD (ORCPT ); Fri, 22 Jul 2016 16:52:03 -0400 Received: from mout.gmx.net ([212.227.15.15]:60049 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751195AbcGVUwA (ORCPT ); Fri, 22 Jul 2016 16:52:00 -0400 Date: Fri, 22 Jul 2016 22:51:35 +0200 From: Stefan Lippers-Hollmann To: Arnd Bergmann Cc: Jes Sorensen , linux-wireless@vger.kernel.org, Kalle Valo , Larry Finger , netdev@vger.kernel.org, Greg Kroah-Hartman , Mateusz Kulikowski , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, Andrea Merello Subject: Re: [PATCH 2/3] staging/rtl8192e: use s8 instead of char Message-ID: <20160722225135.2b2dd751@mir> In-Reply-To: <7894919.vMsHjmmMb1@wuerfel> References: <20160719153403.2967812-1-arnd@arndb.de> <20160722043922.0a878698@mir> <7894919.vMsHjmmMb1@wuerfel> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:4NVlhC/Q9Z/xk760qwzVuuPSKxUypXZts795CYt9CN1lEvnBiKj QtyMfQtqv7xdzo6ikYrh+GoYERzFMpJWlV7uWEVgXAQy720KkB1qrJbFShDnGbFXteAEVhg RSbIYb2n0UHlRYdUQngLpS2zV0nSVEu1JCSnAoFwoa69KbaqKh7N7d9oIMeiGlevRnpfyZw 3YL0lnCoFcJvNe1fYbwDg== X-UI-Out-Filterresults: notjunk:1;V01:K0:UUMhAtBeAwM=:ydT03rJBiFkNHuO9zJuNiP LqjmS0r3PlI98WwhZ3qZPYeBuEsCxe+54YRS1EehspnVmQzL/ho5aHb+ldU8s2C2llPa2JVdA WKhJDjGvbT5Hwr7Ctr4Wv3CSsR81OVNa8aXzXpi2aW7rcQ5leP/Y8p1L7nnI2miFusrjdvDOt gAQUs5niON9FwaGgB7MsHi0/0z6okuA1URYPmzUYMhg4/N0+BwX9varz+udE7an7tmcF0Uktu RcFUFGUHe8KN3hM78fhzx1+0c6nIrmsZyBoZXrjRIt6y5W2+dwH/1gNY02JDHDFYMnLOhfPtF EI2hseonPG4nBXyWNtlzNh2KnttpFqxOaiWFXVCspUHIAFzUIIb2yDhR3vZe+Ys7hWA0SBVRQ VFjpDGOlG8H4CDoDkM/2zzpsSC55gEir6QoLRobmfuGTn1Y+x0M+tHAsj7Nk79lJvlT6ju/n8 5jSSdE9VlCjHc7qmQjbZ9YKJZVDlwlO90QmUxkSpEht0G4Q+5eSayOqxb4z3dpUksGTeSEtH8 5B30KJMxcahOc4FszNPAVaO513fXdPXutv8LFxabi9eZINhVXTeCtpDrb1zOgmgtsGsWf3BPo nfac72M6jkXNbD2xs9ksWRGOpbIFsVOhbJkPGEy0OFE56guvfEmJa8s5EF444PBJ8ROhVp2/l c2QPYaeNsLlXZVN7xLGV0Bw5x2h5tL0EzWkR7fgKdgSXLb44iRTtM1o5fQqjhFeDkAaXlSon8 JaZWwOeE2o73Zv+7hNhBw7NJu8GdREL7KbuhfVqnccsifZvRSlqMDfmsU9sEzeO7oThWI0nJ5 bRfERMm Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On 2016-07-22, Arnd Bergmann wrote: > On Friday, July 22, 2016 7:55:36 AM CEST Jes Sorensen wrote: > > Stefan Lippers-Hollmann writes: > > > On 2016-07-20, Arnd Bergmann wrote: > > >> On Wednesday, July 20, 2016 11:33:43 AM CEST Jes Sorensen wrote: > > >> > Arnd Bergmann writes: > > >> > > On Wednesday, July 20, 2016 7:25:19 AM CEST Jes Sorensen wrote: > > >> > >> Arnd Bergmann writes: [...] > > > 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. Talking purely for myself, I've certainly bought the rtl8192du device because of its 5 GHz support, as I've made it a fairly hard policy for me not to buy 2.4 GHz only devices anymore. But this doesn't mean that a mainline driver only supporting 2.4 GHz for the time being would not be appreciated dearly, given that the current state of the device is pretty much being a doorstop[1] - especially considering that 5 GHz support might even become a possibility at a later time, when 802.11ac devices start demanding most of the functionality for potentially more common newer chipset generations. So even with my current personal policy of only buying 5 GHz capable devices, in practice you probably won't find 5 GHz only AP installations (aside from long range/ outdoor point-to-point connections), be it because of the plethora of existing 2.4 GHz only devices or just because of the longer indoor (walls) range of the 2.4 GHz band. In practice, by far most of my existing wireless devices don't support 5 GHz (the router does, of course) because of the reasons mentioned above, but replacing older devices takes its time. Regards Stefan Lippers-Hollmann [1] yes, I know about https://github.com/lwfinger/rtl8192du/ and even have a couple of clean-up patches pending[2] for the kernel-version branch, but those need some further testing. [2] http://aptosid.com/slh/rtl8192du/kernel-version/