From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Firmware crash when sending large numbers of forwarded packets
Date: Sat, 8 Mar 2014 18:57:04 +0200 [thread overview]
Message-ID: <87pplwmxwf.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAHqTa-1BjUQH_zQp=8NEHt7LQ1JQAG5ftzx+u4i4OqEqaG7teg@mail.gmail.com> (Avery Pennarun's message of "Sat, 8 Mar 2014 02:20:28 -0600")
Avery Pennarun <apenwarr@gmail.com> writes:
> On Sat, Mar 8, 2014 at 2:03 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>
>> What I recommend is to use the master branch of my ath.git tree. That's
>> fairly recent wireless-testing (max 2 weeks old) plus latest ath10k +
>> ath6kl patches I have (ie. merge of wireless-testing and my ath-next
>> branch).
>
> Ok, thanks. We're using a fairly old kernel on our device right now
> (3.2.26) so we're using the ath10k driver from linux-backports. This
> means it's a little tricky to pick an arbitrary version if it has
> diverged to far from linux/master or linux-next.
Yeah, you are not the only one using ath10k with linux-backports.
Ideally we should have our own "backports-ath10k" which contains latest
and greatest ath10k from my master tree. This would be really handy for
debugging problems and verifying bug fixes, but I don't see any way to
find time for that right now :/
> I did try a few different versions though and they did the same thing.
Yeah, I wasn't expecting master branch to contain any fixes to your
issues. This was more like a generic comment.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-03-08 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:38 Firmware crash when sending large numbers of forwarded packets Avery Pennarun
2014-03-07 11:15 ` Michal Kazior
2014-03-07 15:53 ` Ben Greear
2014-03-08 0:54 ` Avery Pennarun
2014-03-08 1:08 ` Ben Greear
2014-03-08 1:21 ` Avery Pennarun
2014-03-10 7:47 ` Michal Kazior
2014-03-08 8:03 ` Kalle Valo
2014-03-08 8:20 ` Avery Pennarun
2014-03-08 16:57 ` Kalle Valo [this message]
2014-03-10 19:26 ` Avery Pennarun
2014-03-11 7:31 ` Kalle Valo
2014-03-10 10:10 ` Michal Kazior
2014-03-10 10:16 ` Michal Kazior
2014-05-12 1:43 ` Avery Pennarun
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=87pplwmxwf.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.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 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.