From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Drunk Cat <natserver2@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: alfa awus036nhr v2 and module rtl8xxxu
Date: Tue, 09 Feb 2016 21:00:06 -0500 [thread overview]
Message-ID: <wrfjlh6tb9zt.fsf@redhat.com> (raw)
In-Reply-To: <56BA8E5D.5090402@lwfinger.net> (Larry Finger's message of "Tue, 9 Feb 2016 19:11:57 -0600")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 02/09/2016 03:00 PM, Jes Sorensen wrote:
>> Jes Sorensen <Jes.Sorensen@redhat.com> writes:
>>> Larry Finger <Larry.Finger@lwfinger.net> writes:
>>>> I can confirm what Drunk Cat sees. There is something different about
>>>> the RTL8192RU as using the iwconfig utility shows no APs in the
>>>> scan. I hope to get to debugging the problem soon.
>>>
>>> OK - thats unfortunate. Most likely the wrong antenna path is being
>>> enabled for it, or something like that.
>>>
>>> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
>>> to look at it, if you don't nail it before.
>>
>> One more time with the actual patch ...
>
> No help. The name of the patch makes it sound as if it is for a 1T2R
> device. The RTL8188RU is 1x1.
Darn, I didn't have an 8188RU near me when I discovered that bug and so
I wasn't sure if it was 1T2R or 1T1R. All my other 1T1R parts work
fine with the current code.
Cheers,
Jes
next prev parent reply other threads:[~2016-02-10 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 23:36 alfa awus036nhr v2 and module rtl8xxxu Drunk Cat
2016-02-04 16:45 ` Jes Sorensen
2016-02-04 17:39 ` Larry Finger
2016-02-04 17:41 ` Jes Sorensen
2016-02-05 16:43 ` Larry Finger
2016-02-09 20:59 ` Jes Sorensen
2016-02-09 21:00 ` Jes Sorensen
2016-02-10 1:11 ` Larry Finger
2016-02-10 2:00 ` Jes Sorensen [this message]
[not found] ` <CAOhKHAXH-PCyWQSpuuZ=-6BnE0PeDks-4p9A3G_86OHLfEdU=w@mail.gmail.com>
2016-02-10 15:49 ` Larry Finger
2016-02-28 23:01 ` Jes Sorensen
2016-02-29 6:57 ` Larry Finger
2016-02-29 12:28 ` Jes Sorensen
2016-02-29 21:34 ` Larry Finger
2016-03-03 21:54 ` Jes Sorensen
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=wrfjlh6tb9zt.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=natserver2@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.