From: "B R Manjula" <brm@cdot.in>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k drivers on t1024 freescale board
Date: Tue, 12 Jan 2016 22:26:37 +0530 [thread overview]
Message-ID: <20160112165623.M2349@cdot.in> (raw)
In-Reply-To: <CA+BoTQnp1jQ5e4A5EuMxcn0YMzD5b3J-cjo_NwtL3_oN4=8-dA@mail.gmail.com>
thanks for input...
On Tue, 12 Jan 2016 13:02:29 +0100, Michal Kazior wrote
> On 12 January 2016 at 09:17, B R Manjula <brm@cdot.in> wrote:
> > Thanks for your input which version of the backport to be taken for kernel 3.12
> >
> > backports-4.2.6-1 signed
> > backports-4.1.1-1 signed
> > backports-4.0.1-1 signed
> > backports-3.19-rc1-1 signed
> > backports-3.18.1-1 signed
> > backports-3.17.1-1 signed
> > backports-3.16.2-1 signed
> > backports-3.15.9-1 signed
> > backports-3.14-1 signed
> > backports-3.12.8-1 signed
> > backports-3.10.19-1 signed
>
> All of them should work. That's how backports work:
>
> https://backports.wiki.kernel.org/index.php/Documentation
>
> > where do we get otp.bin file
>
> You don't. It's embedded in FW API2 firmware blobs. FW API1 is very
> old and I would discourage using a driver which requires it. FYI You
> can still get it either by extracting it or using older git checkout:
>
> https://github.com/kvalo/ath10k-
firmware/tree/9374d42c01bd84487855af9f9bffc622c50e7331/ath10k/QCA988X/hw2.0
>
> Michał
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Disclaimer:
----------
This email and any files transmitted with it are confidential and intended solely for
the use of the individual or entity to whom they are addressed. If you are not the
intended recipient you are notified that disclosing, copying, distributing or taking
any action in reliance on the contents of this information is strictly prohibited. The
sender does not accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail t
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-01-12 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 7:05 ath10k drivers on t1024 freescale board B R Manjula
2016-01-12 7:56 ` Fw: " B R Manjula
2016-01-12 8:04 ` Michal Kazior
2016-01-12 8:09 ` B R Manjula
2016-01-12 8:17 ` B R Manjula
2016-01-12 12:02 ` Michal Kazior
2016-01-12 16:56 ` B R Manjula [this message]
2016-01-12 11:29 ` B R Manjula
2016-01-12 12:06 ` Michal Kazior
2016-01-12 12:04 ` B R Manjula
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=20160112165623.M2349@cdot.in \
--to=brm@cdot.in \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.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