Ben Greear wrote: > I was thinking about adding a method that grabbed as many registers > as I have info for and dumping them with printk when DMA errors > hit. This would make kernel splats more useful. > > And also have a debugfs file called 'registers' or similar that one > could cat out and get similar info. And this can let folks look > at steady-state or whatever. > > But, the logic to turn the register bit values into strings would > be in the driver (and thus add some code size bloat). > > My hope is that this would allow a better chance of understanding > the stop-DMA errors that some people get reliably (but which I can never reliably > reproduce). > > I'm not sure how that plays into your 'event log' idea, but maybe > one will help the other. I was thinking more on the lines of instrumentation, but what you are describing here looks like a VERBOSE_DEBUG option is needed. Sujith -- 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
