Hi! >> I'm developing a test of device firmware loading (after 3.7 it can be >> loaded directly or as usual), but I'm not sure under which ltp directory >> it should be placed. Is it OK if I use two locations as described below? >> >> .../testcases/kernel/device-drivers/firmware/fw_load_kernel/fw_load.ko - >> kernel space part (calls request_firmware with specified parameters), and >> >> .../testcases/kernel/device-drivers/firmware/fw_load_user/fw_load - user >> space part (creates firmware files, replaces udev's firmware searched >> paths, loads the module, prints results...). > 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? > And there is another problem with building kernel modules, I think that > we don't have any configure checks to find out if kernel-devel is > installed (i.e. /lib/modules/$(version)/build/ exists) and which kernel > version to use, etc. But this part shouldn't be that hard. > OK, it can be fixed.
------------------------------------------------------------------------------ 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
