Firmware debugging patches?
greearb at candelatech.com
Wed Jun 4 12:29:05 PDT 2014
On 06/04/2014 12:23 PM, Emmanuel Grumbach wrote:
>> Do you have a link to your patch that defines the types you used?
> Take a look at 1bd3cbc1a0e9ed977a6bd470c5bc7bd36fd87e26.
> But I am adding more and more content to this file.
Yeah, after implementing it in ath10k it seems there would
be very little over-lap, so probably each driver should just
do their own.
We can keep the debugfs file names the same, and the udev
event types the same, which should help user-space a bit.
>> It does not resolve my interest in firmware logs interleaved with
>> kernel logs and possibly supplicant, however.
>> Looks like trace-cmds could do that, but it will not be
>> running for normal users when they experience crashes.
>> Any suggestions other than printk for this feature?
> I seems you found a way already :)
I can get firmware logs, but they are not interleaved.
Probably good enough for now..and we can always add
printk or similar in the future if we all decide it's
Being able to look at your iwlwifi work made my patches lot easier,
so thanks for taking the initiative!
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the ath10k