Hi! > > The problem with device-drivers directory is that the code there is > > broken (unmaintained since 2009 or so) and the make (from the top > > directory) doesn't go there. It should be cleaned/removed/fixed but > > nobody had time to look at the tests and decide what to do with them. > > > > Otherwise the destination fits well enough. > As I understand from README file in that directory, these tests should > not be run automatically. It explains why make doesn't go there. But the > firmware loading test can be (preferably should be) run automatically. > That way, may be change directory to .../testcases/kernel/firmware?
Hmm, so the test tests userspace API for firmware loading but needs helper kernel module, am I right?. In that case kernel/firmware/ should be ok as well. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
