Hmm should this really be sizeof()? Not next_idx (which effectively
defines number of bytes of the dbglog)?
I haven't tried decoding this yet, but we may need to know the next_idx
to decode this properly.
So basically a (length, payload) encoding would be necessary here
instead of a single stream, right?
As long as you know the starting point for a message, you can decode the
rest of the message(s) as a stream of 32 bit ints. The current code that
I wrote is a circular buffer, so after first wrap, we lose an idea of where
to start reading.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
