Ben Greear <greearb@xxxxxxxxxxxxxxx> writes: > This series has taken a long time already, so it would be fine with me > to deal with the dbglog cleanup in subsequent patches, and just assume > for now that the dbglog messages start at index 0 in the dbglog-entry-data. I also would like to get this support finally in. As the basic infrastructure seems to be mostly ok, I'm planning to split the patchset into two and the first containing just the basic infrastructure and register dump: ATH10K_FW_CRASH_DUMP_REGDUMP = 1, Which I'll actually rename to ATH10K_FW_CRASH_DUMP_REGISTERS. And I'll also fix the endian problem Michal pointed out. And then we can later add the rest, once they are properly tested and the endian issues are solved: ATH10K_FW_CRASH_DUMP_DBGLOG = 0, ATH10K_FW_CRASH_DUMP_STACK = 2, ATH10K_FW_CRASH_DUMP_EXC_STACK = 3, ATH10K_FW_CRASH_DUMP_RAM_BSS = 4, ATH10K_FW_CRASH_DUMP_ROM_BSS = 5, And as we use TLV format this split doesn't break anything in user space. How does that sound? -- 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
