From: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
To: Sergey Stepanov <no.such.process@gmail.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: QCA9984 firmware crash
Date: Tue, 10 Jan 2017 21:27:16 +0530 [thread overview]
Message-ID: <20170110155716.GB7422@atheros-ThinkPad-T61> (raw)
In-Reply-To: <CABuVar+MFzBbGToWU0O5ooqmybRyaqGqpNAqXvgjKUzMzwR4jA@mail.gmail.com>
On Tue, Jan 10, 2017 at 08:54:34PM +0500, Sergey Stepanov wrote:
> Hello, all
>
> Thanks for helping, finally I got this thing working.
[shafi] It would be good if you let us know what did you fix to make this
working ? Is the one suggested by Adrian ?
>
> 2017-01-10 20:44 GMT+05:00 Adrian Chadd <adrian@freebsd.org>:
> > hiya,
> >
> > Have you pushed the channel list into the firmware? You (a) nede to
> > push a channel list early on, way before you create vdevs, and (b) it
> > needs to match the band (2g, 5g, 2g/5g) that the firmware expects.
> > pushing 2g channels to a 5g band causes the firmware to panic upon
> > vdev create/up.
> >
> >
> >
> > -adrian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-01-10 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 11:27 QCA9984 firmware crash Sergey Stepanov
2017-01-09 18:17 ` Adrian Chadd
2017-01-10 5:58 ` Sergey Stepanov
2017-01-10 10:25 ` Mohammed Shafi Shajakhan
2017-01-10 15:44 ` Adrian Chadd
2017-01-10 15:54 ` Sergey Stepanov
2017-01-10 15:57 ` Mohammed Shafi Shajakhan [this message]
2017-01-10 16:26 ` Adrian Chadd
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=20170110155716.GB7422@atheros-ThinkPad-T61 \
--to=mohammed@codeaurora.org \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=no.such.process@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