Re: Firmware debugging patches?

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