parse_tcpdump_log.pl: Add an option to show that bulk/isoc xfers happened

This is not really a parser for bulk/isoc, but it helps to see where,
in the stream, the xfers started to occur.

Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

diff --git a/contrib/parse_tcpdump_log.pl b/contrib/parse_tcpdump_log.pl
index a29a4a4..e665e29 100755 (executable)
--- a/contrib/parse_tcpdump_log.pl
+++ b/contrib/parse_tcpdump_log.pl
@@ -38,11 +38,13 @@ my $debug = 0;
 my $man = 0;
 my $help = 0;
 my $pcap = 0;
+my $all = 0;
 my $device;
 
 GetOptions('debug=i' => \$debug,
           'help|?' => \$help,
           'pcap' => \$pcap,
+          'all' => \$all,
           'device=s' => \$device,
            man => \$man
          ) or pod2usage(2);
@@ -374,6 +376,13 @@ sub print_frame($$)
        return;
 }
 
+my %frametype = (
+       0 => "ISOC",
+       1 => "Interrupt",
+       2 => "Control",
+       3 => "Bulk",
+);
+
 sub process_frame($) {
        my %frame = %{ $_[0] };
 
@@ -385,7 +394,10 @@ sub process_frame($) {
        }
 
        # For now, we'll take a look only on control frames
-       return if ($frame{"TransferType"} ne "2");
+       if ($frame{"TransferType"} ne "2" && $all) {
+               printf "Transfer type: %s\n", $frametype{$frame{"TransferType"}};
+               return;
+       }
 
        if ($frame{"Status"} eq "-115") {
                push @pending, \%frame;