linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@redhat.com>
To: ali@internetdog.org
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: r8712u issue
Date: Tue, 19 Jul 2011 19:38:55 +0200	[thread overview]
Message-ID: <4E25C12F.3080804@redhat.com> (raw)
In-Reply-To: <20110719173203.GA7406@internetdog.org>

On 19.07.2011 19:32, Ali Bahar wrote:
> On Tue, Jul 19, 2011 at 07:16:36PM +0200, Stefan Assmann wrote:
>> On 19.07.2011 18:16, Ali Bahar wrote:
>>> On Tue, Jul 19, 2011 at 11:06:55AM -0500, Larry Finger wrote:
>>>> On 07/19/2011 08:24 AM, Stefan Assmann wrote:
>>>>>
>>>>> So far I can say that with scan_ssid=1 after rebooting the AP the
>>>>> connection is properly re-established. Looks promising.
>>>>
>>>> Your results make sense. The driver is fairly passive in all this.
>>>> It gets TX requests from the MAC layer, and passes received data
>>>> back up to that layer. It seems likely that the MAC layer built into
>>>> r8712u is not keeping track of missing responses, or it is not
>>>> probing the AP. In either case, it would not be productive to devote
>>>> any effort to fixing that part when either using NetworkManager or
>>>> setting scan_ssid for wpa_supplicant establishes periodic scans.
>>>> When these fail to get response from the AP, the softmac code will
>>>> respond, as you see.
>>>>
>>>> The ultimate fix will be to convert to the driver to use mac80211,
>>>
>>> Just what I've been thinking lately. I didn't think it very worthwhile
>>> to invest too much into fixing the miscellany.
>>
>> Agreed! Maybe we could add a note to the documentation to make the
>> behaviour more obvious.
> 
> There's documentation?! ;-|
> 
> ... The following could be an option:
> http://linuxwireless.org/en/users/Drivers/rtl819x

Good idea!

> 
> Larry's the author, and so it's _his_ call. _I_ am just tackling
> whatever problems I run into; at the moment, that happens to be the
> r8712u driver.

Right, my statement wasn't directed strictly to you, I was just
thinking of how to improve the situation. :)

  Stefan

  reply	other threads:[~2011-07-19 17:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E2051F3.20103@redhat.com>
2011-07-15 15:15 ` r8712u issue Larry Finger
2011-07-16 15:15   ` Ali Bahar
2011-07-18  7:49   ` Stefan Assmann
2011-07-18  8:27     ` Ali Bahar
2011-07-18  8:46       ` Stefan Assmann
2011-07-18  9:01         ` Ali Bahar
2011-07-18 14:53         ` Larry Finger
2011-07-18 15:01           ` Stefan Assmann
2011-07-18 15:44             ` Larry Finger
2011-07-19 13:24               ` Stefan Assmann
2011-07-19 13:28                 ` Ali Bahar
2011-07-19 16:06                 ` Larry Finger
2011-07-19 16:16                   ` Ali Bahar
2011-07-19 17:16                     ` Stefan Assmann
2011-07-19 17:32                       ` Ali Bahar
2011-07-19 17:38                         ` Stefan Assmann [this message]
2011-07-19 17:45                           ` Larry Finger
2011-07-19 17:51                             ` Ali Bahar

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=4E25C12F.3080804@redhat.com \
    --to=sassmann@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=ali@internetdog.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).