From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Firmware debugging patches?
Date: Fri, 6 Jun 2014 12:43:13 +0300 [thread overview]
Message-ID: <87tx7yl6fh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <538CEAE0.6090304@candelatech.com> (Ben Greear's message of "Mon, 2 Jun 2014 14:21:36 -0700")
Ben Greear <greearb@candelatech.com> writes:
> I'm looking at how iwlwifi/mvm does this. I should be able to read the
> ath10k stack and exception stack on generic firmware, but to get the BSS region,
> I ended up adding some additional meta info to the firmware-2.bin image
> specifying the offsets when doing my CT firmware.
>
> You should not need to re-compile the firmware for this, but you would have
> to be able to run some xtensa tool commands to get this info and re-pack
> the firmware with additional meta-info (as far as I know).
>
> Any chance upstream firmware could support specifying the bss region
> offsets so that I can dump that into the debugfs dump file?
Sure, having the bss region in enum ath10k_fw_ie_type makes sense. And
if the value is missing from the image, we would have some sane default
in ath10k.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-06-06 9:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53891ACD.7070902@candelatech.com>
2014-06-02 16:21 ` Firmware debugging patches? Kalle Valo
2014-06-02 16:40 ` Ben Greear
2014-06-02 17:08 ` Kalle Valo
2014-06-02 17:42 ` 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
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
2014-06-02 21:21 ` Ben Greear
2014-06-06 9:43 ` Kalle Valo [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=87tx7yl6fh.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.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