1*1da177e4SLinus Torvalds# 2*1da177e4SLinus Torvalds# USB Monitor configuration 3*1da177e4SLinus Torvalds# 4*1da177e4SLinus Torvalds 5*1da177e4SLinus Torvalds# In normal life, it makes little sense to have usbmon as a module, and in fact 6*1da177e4SLinus Torvalds# it is harmful, because there is no way to autoload the module. 7*1da177e4SLinus Torvalds# The 'm' option is allowed for hackers who debug the usbmon itself, 8*1da177e4SLinus Torvalds# and for those who have usbcore as a module. 9*1da177e4SLinus Torvaldsconfig USB_MON 10*1da177e4SLinus Torvalds tristate "USB Monitor" 11*1da177e4SLinus Torvalds depends on USB 12*1da177e4SLinus Torvalds default y 13*1da177e4SLinus Torvalds help 14*1da177e4SLinus Torvalds If you say Y here, a component which captures the USB traffic 15*1da177e4SLinus Torvalds between peripheral-specific drivers and HC drivers will be built. 16*1da177e4SLinus Torvalds The USB_MON is similar in spirit and may be compatible with Dave 17*1da177e4SLinus Torvalds Harding's USBMon. 18*1da177e4SLinus Torvalds 19*1da177e4SLinus Torvalds This is somewhat experimental at this time, but it should be safe, 20*1da177e4SLinus Torvalds as long as you aren't building this as a module and then removing it. 21*1da177e4SLinus Torvalds 22*1da177e4SLinus Torvalds If unsure, say Y. Do not say M. 23