usbmon: drop bogus 0t from usbmon.txt

The example is incorrect: there is no 0t socket (the '1t' format has no
bus number in it). Also, correct the broken sentence for USB Tag.

Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

authored by

Pete Zaitcev and committed by
Greg Kroah-Hartman
aacf4a01 7c124149

+7 -5
+7 -5
Documentation/usb/usbmon.txt
··· 34 34 Verify that bus sockets are present. 35 35 36 36 # ls /sys/kernel/debug/usbmon 37 - 0s 0t 0u 1s 1t 1u 2s 2t 2u 3s 3t 3u 4s 4t 4u 37 + 0s 0u 1s 1t 1u 2s 2t 2u 3s 3t 3u 4s 4t 4u 38 38 # 39 39 40 - Now you can choose to either use the sockets numbered '0' (to capture packets on 41 - all buses), and skip to step #3, or find the bus used by your device with step #2. 40 + Now you can choose to either use the socket '0u' (to capture packets on all 41 + buses), and skip to step #3, or find the bus used by your device with step #2. 42 + This allows to filter away annoying devices that talk continuously. 42 43 43 44 2. Find which bus connects to the desired device 44 45 ··· 100 99 101 100 Here is the list of words, from left to right: 102 101 103 - - URB Tag. This is used to identify URBs is normally a kernel mode address 104 - of the URB structure in hexadecimal. 102 + - URB Tag. This is used to identify URBs, and is normally an in-kernel address 103 + of the URB structure in hexadecimal, but can be a sequence number or any 104 + other unique string, within reason. 105 105 106 106 - Timestamp in microseconds, a decimal number. The timestamp's resolution 107 107 depends on available clock, and so it can be much worse than a microsecond