From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
Yijun_Shen@dell.com, Perry_Yuan@dell.com,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k fail to load firmware
Date: Tue, 19 Jul 2016 11:27:27 +0200 [thread overview]
Message-ID: <20160719092727.GD2751@redhat.com> (raw)
In-Reply-To: <CA+BoTQk7QKaO2yxMq5JEhrBhn4WtpmWTcOxfiXcvYxrFvaxdgw@mail.gmail.com>
On Tue, Jul 19, 2016 at 11:17:03AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 11:02, <Perry_Yuan@dell.com> wrote:
> > Dell - Internal Use - Confidential
> >
> > I rename the bin file . and capture new full logs from booting to firmware error .
> > The error still happened. Please help to check it .
> > I want to know whether the new firmware bin are updated the right one in this git ?
> > If the firmware is good , the errors should be gone .
Please use reply-to-all, so I could see messages. You can drop ML
eventually if you thing your data is confidential.
> Thanks for checking!
>
> Apparently the available board-2.bin doesn't contain any subsystem
> vendor=1028 board data (just checked).
>
> Also, you guys (i.e. Perry & Stanislaw) seem to be using 2 slightly
> different devices. One reports its subsystem ids as 1028:0310 (in the
> original log Stanislaw provided) and 1028:0410 (found in logs attached
> by Perry).
I provided dmesg, which I get from Perry, hence seems that Perry tests
on 2 different devices :-)
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-07-19 9:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 7:09 ath10k fail to load firmware Stanislaw Gruszka
2016-07-19 7:18 ` Michal Kazior
2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
2016-07-19 8:24 ` Perry_Yuan
2016-07-19 8:32 ` Michal Kazior
2016-07-19 9:02 ` Perry_Yuan
2016-07-19 9:17 ` Michal Kazior
2016-07-19 9:27 ` Stanislaw Gruszka [this message]
2016-07-19 9:41 ` Perry_Yuan
2016-07-20 3:14 ` Perry_Yuan
2016-07-20 6:58 ` Michal Kazior
2016-07-20 7:23 ` Perry_Yuan
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
2016-07-25 10:25 ` Michal Kazior
2016-08-02 12:19 ` Valo, Kalle
2016-07-29 7:45 ` Perry_Yuan
2016-07-29 9:07 ` Perry_Yuan
2016-08-02 12:10 ` Valo, Kalle
2016-08-03 7:00 ` Michal Kazior
2016-08-22 8:40 ` Stanislaw Gruszka
2016-08-22 10:29 ` Valo, Kalle
2016-08-22 11:02 ` Stanislaw Gruszka
2016-08-22 14:05 ` Valo, Kalle
2016-08-23 18:55 ` Valo, Kalle
2016-08-24 6:33 ` Stanislaw Gruszka
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=20160719092727.GD2751@redhat.com \
--to=sgruszka@redhat.com \
--cc=Perry_Yuan@dell.com \
--cc=Yijun_Shen@dell.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--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 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.