Ben Greear <greearb@xxxxxxxxxxxxxxx> writes: > On 09/14/2016 07:18 AM, Valo, Kalle wrote: >> greearb@xxxxxxxxxxxxxxx writes: >> >>> From: Ben Greear <greearb@xxxxxxxxxxxxxxx> >>> >>> This allows user-space tools to decode debug-log >>> messages by parsing dmesg or /var/log/messages. >>> >>> Signed-off-by: Ben Greear <greearb@xxxxxxxxxxxxxxx> >> >> Don't tracing points already provide the same information? > > Tracing tools are difficult to set up and may not be available on > random embedded devices. And if we are dealing with bug reports from > the field, most users will not be able to set it up regardless. > > There are similar ways to print out hex, but the logic below creates > specific and parseable logs in the 'dmesg' output and similar. > > I have written a tool that can decode these messages into useful human-readable > text so that I can debug firmware issues both locally and from field reports. > > Stock firmware generates similar logs and QCA could write their own decode logic > for their firmware versions. Reinventing the wheel by using printk as the delivery mechanism doesn't sound like a good idea. IIRC Emmanuel talked about some kind of firmware debugging framework, he might have some ideas. -- Kalle Valo
