DKMS version 0.36.05 is now availabel (tarball or RPM):

* In dkms.conf, when specifying the name of your module, you should no longer append the .o or .ko to the end. Instead, based on what kernel you are building a module for, DKMS will figure out the suffix (if <2.5 then .o, otherwise .ko) and will work appropriately. The example below shows this change from the old format to the new.

* Removed the DKMS directives LOCATION and MODULE_NAME. Replaced them with the arrays BUILT_MODULE_NAME[#], BUILT_MODULE_LOCATION[#], DEST_MODULE_NAME[#] and DEST_MODULE_LOCATION[#]. This allows much more flexibility in finding and renaming modules and placing them in various locations of your /lib/modules tree. Whereas, before you would specify something like:

MODULE_NAME="qla2200.o:qla2200_6x.o qla2300.o:qla2300_6x.o"
LOCATION="/kernel/drivers/addon/qla2200"

you would now specify it as:

BUILT_MODULE_NAME[0]="qla2200"
DEST_MODULE_NAME[0]="qla2200_6x"
DEST_MODULE_LOCATION[0]="/kernel/drivers/addon/qla2200"

BUILT_MODULE_NAME[1]="qla2300"
DEST_MODULE_NAME[1]="qla2300_6x"
DEST_MODULE_LOCATION[1]="/kernel/drivers/addon/qla2200"

This above example doesn't show usage of BUILT_MODULE_LOCATION which is optional. This is used if your built modules are spread out within your source tree, and you need dkms to find them. It should be given relative to the root directory of your module source (eg. relative to the directory which holds your dkms.conf file).

If you do not intend to rename the modules after they have been built, then DEST_MODULE_NAME is optional. As stated above, with DEST_MODULE_LOCATION, you can now install each module to different locations in your /lib/modules tree.

By Gary at 02:24 PM in Linux | Comments (0)