On Wed, 2012-10-31 at 17:00 +0200, Vladimir Kondratiev wrote: > you just proved reason to be CC'ed: you give valuable feedback :-) :) > Oh, no! Usually, you start digging into ISR registers when something stalled > when it should not. At this point, you want to discover that, for example, > some interrupt bit not came up. Then, you may try to manually set it writing > into register. If you trace, it will flood dmesg, impacting performance, in > normal situation; and will not let you analyze and recover from abnormal one. Well I wasn't thinking printk, but rather trace events, so you can record it to the buffer and not have the big overhead etc. > I need "manual control" here. Fair enough. johannes -- 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
