All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chirag Shahani <chirag.shahani@gmail.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: firmware version 10.2.4.70.54 crash when running on centos-7.3(kernel version -> 3.10.0-514.el7.x86_64)
Date: Mon, 3 Apr 2017 08:39:43 -0700	[thread overview]
Message-ID: <CAEi_5N1iOVbBX8HVWVoaAMczcSSCHNSB6drm4L0EDWX8bVxY0Q@mail.gmail.com> (raw)
In-Reply-To: <87r31cpq6q.fsf@kamboji.qca.qualcomm.com>

Hello,

Thank you for all the info. I used the backport release
backports-4.2.6-1 signed with firmware 10.2.4-1.0 (as this has a
commit recently) and have not faced any crash until now.
--
Chirag

On Sat, Apr 1, 2017 at 12:01 AM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Chirag Shahani <chirag.shahani@gmail.com> writes:
>
>> My aim to use this kernel centos 7.1 kernel
>> 3.10.0-229.48.1.el7.x86_64. Could you please let me know which
>> backport relase I should try to have the latest firmware for centos
>> 7.1 kernel 3.10.0-229.48.1.el7.x86_64
>
> The problem with backports projects is that right now they are not
> making any official releases. But a release within the past year, or
> taking the latest from git, is what I would do. At least then you would
> not be using an ancient version of ath10k.
>
> There's some documentation here:
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2017-04-03 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 17:32 firmware version 10.2.4.70.54 crash when running on centos-7.3(kernel version -> 3.10.0-514.el7.x86_64) Chirag Shahani
2017-03-31 11:00 ` Kalle Valo
2017-03-31 19:40   ` Chirag Shahani
     [not found]   ` <CAEi_5N0291YRJzzguecbMSKGGCg6muEEudwhA1BJ33NKnvDPcQ@mail.gmail.com>
2017-04-01  7:01     ` Kalle Valo
2017-04-03 15:39       ` Chirag Shahani [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=CAEi_5N1iOVbBX8HVWVoaAMczcSSCHNSB6drm4L0EDWX8bVxY0Q@mail.gmail.com \
    --to=chirag.shahani@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=kvalo@qca.qualcomm.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.