So, let's continue discussion in the mailing list. On Thu, 2014-11-13 at 14:54 +0530, Ulka Vaze wrote: > Hi , > I am currently testing Crystal Beach Dma on one of our systems. > We have kernel 2.6.32.431 here. On this when I modprobe dmatest then > in /sys/module/parameters/ file run is missing. > I tried to use it through debugfs but no entry appeared for > dmatest /sys/kernel/debug > The module was patched a lot during 3.8 — 3.12. > > However on latest 3.17 kernel it works. > Is there any way to test on 2.6.32 kernel . > Is some patch is required. > Yes, you may try to back port that. However, I would suggest you to look into the code of the module and supply parameters you need. Old version if I remember correctly immediately run test when you load the module (or when it is initialized if compiled-in). So, something like % modprobe dmatest iterations=1 % modprobe -r dmatest > Can you help? -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
