On Fri, Aug 6, 2010 at 2:59 PM, Hakan Coskun <coskun@xxxxxxxxxxxxxxx> wrote: > thank you for your really quick reply. We are already using wireless-testing for our development. The ath9k extensions will be commited soon. At the moment, we are using the eclipse to index the code and walk through the files. This is working quite good. But how can we see during runtime, what is happening. Should we use something like kgdb to trace the operation or what is your approach you take for development. Can you give us any hints ? > IMHO the best way to do this is a combination of mac80211 tracepoints and ftrace, the function tracer, via trace-cmd. Something like: # trace-cmd record -p function -l ieee\* -e mac80211 sleep 300 ...should get you five minutes worth of useful traces. Of course command can be anything you like. -- Bob Copeland %% www.bobcopeland.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
