greearb@xxxxxxxxxxxxxxx writes: > From: Ben Greear <greearb@xxxxxxxxxxxxxxx> > > Should help debug firmware crashes, and give users a way > to provide some useful debug reports to firmware developers. > > Signed-off-by: Ben Greear <greearb@xxxxxxxxxxxxxxx> > Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> Like we talked on IRC, I think it's better to take a dump of the whole DRAM and find all the info during postprocessing in user space. I just consider it too much work to investigate firmware internals from ath10k as the internals can change between firmware versions. In user space that's a lot easier to manage. Of course downside is the increased memory usage, but if that becomes a problem there are ways to solve that. For example, adding a module parameter with bitmask for individually enabling enum ath10k_fw_crash_dump_type is first which comes to my mind. I have patches ready for the DRAM thing, but I have some issues which I found during testing. I'll post the patches soon as I have solved the issues, but don't know how long that will take. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
