Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36708 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752351AbbHaXn6 (ORCPT ); Mon, 31 Aug 2015 19:43:58 -0400 From: Jes Sorensen To: Larry Finger Cc: linux-wireless@vger.kernel.org, kvalo@codeaurora.org, johannes@sipsolutions.net Subject: Re: [PATCH 1/1] New driver: rtl8xxxu (mac80211) References: <1440883083-32498-1-git-send-email-Jes.Sorensen@redhat.com> <1440883083-32498-2-git-send-email-Jes.Sorensen@redhat.com> <55E289A3.6030001@lwfinger.net> <55E39707.60101@lwfinger.net> <55E476A0.4080601@lwfinger.net> Date: Mon, 31 Aug 2015 19:43:57 -0400 In-Reply-To: <55E476A0.4080601@lwfinger.net> (Larry Finger's message of "Mon, 31 Aug 2015 10:45:36 -0500") Message-ID: (sfid-20150901_014401_816613_A4A68566) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-wireless-owner@vger.kernel.org List-ID: Larry Finger writes: > On 08/30/2015 09:39 PM, Jes Sorensen wrote: >> Larry Finger writes: >>> On 08/30/2015 01:41 PM, Jes Sorensen wrote: >>>>>> +{USB_DEVICE_AND_INTERFACE_INFO(USB_VENDOR_ID_REALTEK, 0x817e, 0xff, >>>>> 0xff, 0xff), >>>>>> + .driver_info = (unsigned long)&rtl8192cu_fops}, >>>>> >>>>> I have tested a device with USB ID 0x0bda (USB_VENDOR_ID_REALTEK):0x817e. >>>> >>>> Were you happy with the results, or did it cause problems? Ie. did you >>>> try on x86 or on PPC32? >>> >>> As covered in the other mail, it works very well at G rates. >> >> I see - I am a little confused, it works well on G rates but not on N >> rates, or was this due to the AP used? > > The AP is AC1200. It supports full N rates on other devices. You only manage to make it work on G rates against this AP? Urgh, I don't like that at all. I thought you reported 30+Mbps performances though?, thats more than you get on G. >>>> I don't think any of this is showstopper material for inclusion right >>>> now, albeit I do want to address them. >>> >>> The scheduling while atomic problems do need to be fixed, and I am >>> still working on the failure to get a wifi device on PPC. >> >> It's already fixed :) > > A full debug=0x3fff showed me one problem on the PPC. I will be > testing a patch later today. Interesting, let me know what you find. Cheers, Jes