From: Ben Greear <greearb@candelatech.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Firmware debugging patches?
Date: Fri, 06 Jun 2014 09:02:40 -0700 [thread overview]
Message-ID: <5391E620.4090706@candelatech.com> (raw)
In-Reply-To: <87fvjimsxj.fsf@kamboji.qca.qualcomm.com>
On 06/05/2014 11:51 PM, Kalle Valo wrote:
> Ben Greear <greearb@candelatech.com> writes:
>
>>> Why do you want to put the crash dump in kernel log, can you describe
>>> your "use case" here? For me it would be enough to have a UUID for each
>>> crash dump and then have the driver print that to kernel log:
>>>
>>> ath10k: firmware crashed (uuid 1234567890-4321)
>>>
>>> And then you just need to find the correct dump from the file system and
>>> start debugging. Would that be enough for you?
>>
>> Not all systems will have fancy user-space able to deal with this.
>>
>> At the very least, please leave in the current firmware crash
>> dump text.
>
> I'm not removing anything. That was just an example how we can identify
> crashes.
Perhaps the time-stamp is good enough? I don't see a need for
a uuid, but perhaps I am missing something?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-06-06 16:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53891ACD.7070902@candelatech.com>
[not found] ` <87wqczz3h9.fsf@kamboji.qca.qualcomm.com>
[not found] ` <538CA904.4000508@candelatech.com>
[not found] ` <87ioojz1b1.fsf@kamboji.qca.qualcomm.com>
2014-06-02 17:42 ` Firmware debugging patches? Ben Greear
2014-06-02 18:46 ` Emmanuel Grumbach
2014-06-02 18:58 ` Ben Greear
2014-06-02 19:29 ` Emmanuel Grumbach
2014-06-02 19:48 ` Ben Greear
2014-06-04 19:23 ` Emmanuel Grumbach
2014-06-04 19:29 ` Ben Greear
2014-06-05 11:10 ` Kalle Valo
2014-06-05 15:51 ` Ben Greear
2014-06-05 11:06 ` Kalle Valo
2014-06-05 15:57 ` Ben Greear
2014-06-06 6:51 ` Kalle Valo
2014-06-06 16:02 ` Ben Greear [this message]
2014-06-07 13:03 ` Kalle Valo
2014-06-07 15:27 ` Ben Greear
2014-06-08 8:35 ` Kalle Valo
2014-06-08 9:13 ` Johannes Berg
2014-06-08 16:01 ` Emmanuel Grumbach
2014-06-08 15:39 ` Ben Greear
2014-06-09 8:17 ` Kalle Valo
2014-06-09 15:09 ` Ben Greear
2014-06-09 15:47 ` Ben Greear
2014-06-09 16:27 ` Ben Greear
2014-06-10 6:05 ` Kalle Valo
2014-06-10 15:06 ` Ben Greear
2014-06-26 15:26 ` Ben Greear
2014-06-26 16:01 ` Kalle Valo
2014-06-05 10:58 ` Kalle Valo
2014-06-05 15:59 ` Ben Greear
2014-06-05 10:51 ` Kalle Valo
2014-06-05 16:03 ` Ben Greear
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=5391E620.4090706@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=egrumbach@gmail.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).