From: Kalle Valo <kvalo@codeaurora.org>
To: Contrib Open Source <contrib.open.source@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: SparkLan WPEQ-261ACN (QCA6174) : packets loss ?
Date: Thu, 11 Jan 2018 18:21:10 +0200 [thread overview]
Message-ID: <87inc8tlhl.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAEV+hqzaqrabZ2uYHHHSNxcmddyFU5Q8odyPqrPZSt-DTJye7A@mail.gmail.com> (Contrib Open Source's message of "Thu, 11 Jan 2018 16:00:35 +0100")
Contrib Open Source <contrib.open.source@gmail.com> writes:
> So my questions are :
> Q1) is it correct to "downgrade" firmware API in this case (symbolic
> link firmware-5.bin) ?
It's not safe, you have to really know what you are doing and understand
the ath10k internals. We do these FW API increases (5 -> 6) for a
reason, usually because the new firmware won't work with older version
of ath10k.
But if you want to run latest ath10k on older kernels I recommend to
look at backports project:
https://backports.wiki.kernel.org/index.php/Main_Page
> Q2) is it possible to use recent board files with an "older" firmware
> file ?
To my knowledge board files are not dependent on the firmware versions.
So yes, you should be able to use newer board-2.bin with older firmware
release.
> Q3) how to know which firmware files to use for my specific device ?
The firmware releases are not "device" specific (but of course it
depends on what you mean with device in this context). But my
recommendation is to always use the latest firmware which works with
your kernel (WITHOUT any symlink hacks etc).
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-01-11 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 15:00 SparkLan WPEQ-261ACN (QCA6174) : packets loss ? Contrib Open Source
2018-01-11 16:21 ` Kalle Valo [this message]
2018-01-11 18:36 ` Contrib Open Source
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=87inc8tlhl.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=contrib.open.source@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 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.