From: Patrick McHardy <kaber@trash.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>,
Dan Williams <dcbw@redhat.com>, Roy Marples <uberlord@gentoo.org>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: prism54 regression in current -git
Date: Tue, 06 May 2008 12:37:37 +0200 [thread overview]
Message-ID: <482034F1.6080400@trash.net> (raw)
In-Reply-To: <480F05B2.9080409@trash.net>
Patrick McHardy wrote:
> Patrick McHardy wrote:
>> Luis R. Rodriguez wrote:
>>>> Good catch. The carrier is set upon a firmware trigger so it is
>>>> possible that when in AP mode we don't hit the trigger in firmware. I
>>>> left open the possibility for this happening and go figure it happens.
>>>> Even if we had docs this probably wouldn't be documented :) I'll try
>>>> to cook up an exception patch now.
>>>
>>> Let me know if this fixes it.
>>> [...]
>>
>> This will probably fix the error I'm seeing, but if I'm not
>> mistaken the mode can be changed while the device is UP and
>> this case is not handled by your patch.
>
> I've verified that is fixes the bug if the device is already
> configured for AP mode when set UP.
>
> It appears to also be working correctly when configuring
> the device for master mode after bringing it up, but I
> don't understand why.
Just to make sure this doesn't get lost, this fix hasn't made it to
Linus' tree yet and appears to be still needed.
prev parent reply other threads:[~2008-05-06 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 4:42 prism54 regression in current -git Patrick McHardy
2008-04-22 14:36 ` Dan Williams
2008-04-22 14:56 ` Patrick McHardy
2008-04-22 17:50 ` Luis R. Rodriguez
2008-04-22 18:03 ` Luis R. Rodriguez
2008-04-22 20:51 ` Patrick McHardy
2008-04-23 9:47 ` Patrick McHardy
2008-05-06 10:37 ` Patrick McHardy [this message]
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=482034F1.6080400@trash.net \
--to=kaber@trash.net \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@winlab.rutgers.edu \
--cc=uberlord@gentoo.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).