From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Brent Taylor <motobud@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>,
Krishna Chaitanya <chaitanya.mgit@gmail.com>,
<ath6kl@lists.infradead.org>
Subject: Re: Laptop disassociating by local choice (reason=17)
Date: Wed, 3 Dec 2014 07:37:58 +0200 [thread overview]
Message-ID: <878uipl2dl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAP+RiCCE1Z96z6+YX=Cfnb0O3vGdnZeivJH5T3XQ5DWbCbbH_w@mail.gmail.com> (Brent Taylor's message of "Tue, 2 Dec 2014 23:31:13 -0600")
Brent Taylor <motobud@gmail.com> writes:
> On Dec 2, 2014 11:24 PM, "Kalle Valo" <kvalo@qca.qualcomm.com> wrote:
>>
>> Brent Taylor <motobud@gmail.com> writes:
>>
>> > I actually ran the wpa_supplicant with -ddddt as the parameter not
>> > knowing how many 'd's I could put there before I hit the limit of the
>> > debugging. The wpa_supplicant on the ubuntu laptop is v0.7.3. I'll
>> > change the -ddddt to just -dddt and re-run the test again.
>>
>> IMHO 0.7.3 is ancient. Please use something more recent.
>
> Ancient it may be, but why would it work with the ath9k chip and not
> the ath6kl chip?
Because of a bug we are not aware of? ath6kl and ath9k are very
different drivers and 0.7.3 might have some problem which only comes
with ath6kl. Up to you, but I would not waste time testing on that old
wpasupplicant.
--
Kalle Valo
next prev parent reply other threads:[~2014-12-03 5:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 18:12 Laptop disassociating by local choice (reason=17) Brent Taylor
2014-12-01 18:49 ` Brent Taylor
2014-12-01 19:00 ` Krishna Chaitanya
2014-12-02 19:18 ` Brent Taylor
2014-12-02 19:39 ` Krishna Chaitanya
2014-12-02 22:35 ` Brent Taylor
2014-12-02 23:32 ` Dan Williams
2014-12-02 23:43 ` Brent Taylor
2014-12-03 5:24 ` Kalle Valo
[not found] ` <CAP+RiCCE1Z96z6+YX=Cfnb0O3vGdnZeivJH5T3XQ5DWbCbbH_w@mail.gmail.com>
2014-12-03 5:37 ` Kalle Valo [this message]
2014-12-03 14:05 ` Brent Taylor
2014-12-03 16:58 ` Brent Taylor
2014-12-03 17:26 ` Brent Taylor
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=878uipl2dl.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=motobud@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 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).