From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Matthew Robbetts <wingfeathera@gmail.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Warnings/errors in use with a QCA989x card
Date: Tue, 9 Jun 2015 11:52:59 +0300 [thread overview]
Message-ID: <87616xgt5g.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <126CD870-B6DF-4885-97D2-C8F15F887C8B@gmail.com> (Matthew Robbetts's message of "Mon, 8 Jun 2015 09:59:56 -0700")
Matthew Robbetts <wingfeathera@gmail.com> writes:
>> On Jun 8, 2015, at 07:42, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>
>> Michal Kazior <michal.kazior@tieto.com> writes:
>>
>>> I think it'd make more sense to actually update the recommended
>>> firmware revision. Currently it's still the 10.1.467 in your git.
>>> It's pretty confusing if you ask me. There's a ton of untested
>>> 10.2.4 images. How does a user know which one to use?
>> Yeah, that's a mess and I should fix it. At the same time we should
>> reorganise the git repo entirely so that we can cleanly support
>> various hardware familes like qca6174. Any ideas how to do that?
>>
>> And my recommendation is to use the latest firmware version from
>> 10.2.4 branch which at this time is 10.2.4.70-2. I would be queries
>> to receive feedback how it works for people.
>
> I’d be happy to keep up with the latest firmware build in general if
> that’s your recommendation. Are there any release notes available?
Unfortunately the firmware team does not provide me release notes for
new firmware releases.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-06-09 8:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 1:52 Warnings/errors in use with a QCA989x card Matthew Robbetts
2015-06-05 5:17 ` Michal Kazior
2015-06-05 15:52 ` Ben Greear
2015-06-05 20:23 ` Matthew Robbetts
2015-06-05 20:39 ` Ben Greear
2015-06-08 7:18 ` Michal Kazior
2015-06-22 18:02 ` Matti Laakso
2015-06-22 22:40 ` Matthew Robbetts
2015-06-23 5:06 ` Michal Kazior
2015-06-23 16:48 ` Matthew Robbetts
2015-06-24 5:09 ` Michal Kazior
2015-06-05 20:16 ` Matthew Robbetts
2015-06-06 13:50 ` Kalle Valo
2015-06-07 20:44 ` Matthew Robbetts
2015-06-08 7:23 ` Michal Kazior
2015-06-08 14:42 ` Kalle Valo
2015-06-08 16:59 ` Matthew Robbetts
2015-06-09 8:52 ` Kalle Valo [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=87616xgt5g.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
--cc=wingfeathera@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