Firmware debugging patches?

[Kalle Valo]

Ben Greear <greearb at candelatech.com> writes:

> I have a bunch of patches that can dump some firmware debug logs,
> stack, and exception stacks as ascii hex. Ath10k firmware-having folks
> can use private tools to extract and decode useful info from this.

You mean via printk? That sounds ugly.

There was talk on linux-wireless about how to handle firmware crash
dumps in a generic way. One proposal was to use ethtool and an event for
this. Before that I was thinking of using trace points. Maybe we should
support both?

We should come up with an extensible format how to provide the firmware
crash logs to user space, for example using some TLV based format, which
contain all the necessary information (hw details, firmware version,
memory dumps and whatnot). But ath10k should not have any parsing of the
dumps, that should happen in user space.

-- 
Kalle Valo