From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Tobias Predel <tobias.predel@gmail.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Recent driver changes destabilized QCA9377 connection quality
Date: Thu, 2 Feb 2017 07:48:49 +0000 [thread overview]
Message-ID: <8737fxowx5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170129104829.GA3440@lichtkranz.fritz.box> (Tobias Predel's message of "Sun, 29 Jan 2017 11:48:30 +0100")
Tobias Predel <tobias.predel@gmail.com> writes:
> I just want to report a negative development I have been experiencing
> for a week now.
>
> Recent changes in ath10k driver code seem to destabilize QCA9377
> connection quality in 802.11b/g networks, as hardware and software
> configuration (wpa_supplicant) hasn't changed. Before, I have managed
> to have a fair connection quality for around three months. At the
> moment I encounter multiple connection losses.
>
> dmesg reports usual losses and timeouts on both linux-lts 4.4.44 and
> linux 4.8.13 (Arch Linux).
>
> Please restore former functionality.
You mention recent changes, so what kernel exact version works without
problems? Has the firmware version remained the same all the time?
If it's a regression in kernel, can you bisect to find the commit which
broke it? You would need to compile your own kernels to do that.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-02-02 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 10:48 Recent driver changes destabilized QCA9377 connection quality Tobias Predel
2017-01-29 20:37 ` Adrian Chadd
2017-01-29 21:18 ` Tobias Predel
2017-02-02 7:48 ` Valo, Kalle [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-26 15:40 Tobias Predel
2017-02-27 4:24 ` Mohammed Shafi Shajakhan
2017-02-27 10:59 ` Michal Kazior
2017-02-28 17:59 ` Tobias Predel
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=8737fxowx5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=tobias.predel@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