Firmware debugging patches?
kvalo at qca.qualcomm.com
Thu Jun 5 03:51:43 PDT 2014
sorry for jumping in late, I get too much email as usual :/
Ben Greear <greearb at candelatech.com> writes:
> [Good stuff snipped, adding linux-wireless as this is a more
> general issue if we are going to consider general framework]
> Maybe we should start with goals before getting to implementation
> details. Here's my wish list that is ath10k specific, but probably
> similar to other firmware users:
> 1) We need the firmware crash text currently printed to
> 2) It would be nice to get the firmware RAM and stack dumps at time of
> crash to debug more interesting crashes.
> 3) It would be nice to know about firmware debug messages for
> the period of time directly before the crash (maybe 2-5 minutes?)
> 4) It would be nice to have this interleaved with kernel, supplicant,
> and related logs.
I would add:
5) A generic user space interface so that the same user space tool can
store firmware crash dumps from all wireless drivers and no need to
reinvent the wheel.
> If we are storing crashes for something like ethtool to report, we need
> RAM and/or disk storage so the firmware RAM dumps and such can be stored until
> the user and/or automated tools ask for them. We need some way to automatically
> clean up old crashes so disk/ram is not overly utilized. For APs,
> they are low on both RAM and 'disk', so storing crash logs for any
> length of time may be problematic.
I think most, if not all, wireless drivers store the firmware binary in
RAM forever. I'm having hard time to believe that storing one instance
(the latest one) of firmware crash dump would make any difference.
That's why I'm not worried about RAM usage.
More information about the ath10k