Hi Joao Paulo, > It is difficult to follow anything else happening when a SCO connection > is active, as the log gets floded with SCO packets. This adds an option > to disable dumping SCO packets. > --- > monitor/main.c | 9 +++++++-- > monitor/packet.c | 6 ++++-- > monitor/packet.h | 1 + > 3 files changed, 12 insertions(+), 4 deletions(-) > > diff --git a/monitor/main.c b/monitor/main.c > index 5fa87ea3f..6a8618c41 100644 > --- a/monitor/main.c > +++ b/monitor/main.c > @@ -70,7 +70,8 @@ static void usage(void) > "\t-V, --vendor <compid> Set default company identifier\n" > "\t-t, --time Show time instead of time offset\n" > "\t-T, --date Show time and date information\n" > - "\t-S, --sco Dump SCO traffic\n" > + "\t-N, --no-sco-packets Do not dump SCO packets\n" > + "\t-S, --sco Dump SCO traffic (without -N)\n” I am confused. I assumed I made SCO off by default. Anyhow, I don’t want to see tons of independent options. Since next thing is you tell me that AVDTP media channel is also something you want to filter out. So then we better find a generic way to apply filters and also notifications about “dropped x packets due to filter” kinda hints. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
