Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

There should be a dsplinkk.ko file in the /lib/modules/3.2.0/ directory in the reference filesystems. See http://support.criticallink.com/redmine/boards/10/topics/2068?r=2073#message-2073

There is a blurb about rebuilding the module for a modified kernel if you need that.

-Mike

Michael Williamson wrote:

There should be a dsplinkk.ko file in the /lib/modules/3.2.0/ directory in the reference filesystems. See http://support.criticallink.com/redmine/boards/10/topics/2068?r=2073#message-2073

There is a blurb about rebuilding the module for a modified kernel if you need that.

-Mike

Hello All,
I successfully rebuilt the kernel to the version 3.2.0, then I tried to install the kernel object dsplinkk.ko .
I used the one given with the MDK of August 2012, in the directory suggested by Mike /lib/modules/3.2.0/
after giving the command:
"insmod dsplinkk.ko"
Prints out an error as:
"
dsplinkk: disagrees about version of symbol set_user_nice
dsplinkk: Unknown symbol set_user_nice (err -22)
dsplinkk: disagrees about version of symbol wake_up_process
dsplinkk: Unknown symbol wake_up_process (err -22)
insmod: error inserting 'dsplinkk.ko': -1 Invalid parameters
"
What do I need to do?

Thank you very much!

Michele

If you added or removed features from the kernel, you may need to rebuild the dsplink drivers.

To do that:

1. source the toolchain setup script like you did to build the kernel.
2. cd to ${MDK}/sw/3rdparty/dsplink_linux_1_65_00_03/dsplink
3. edit the setenv-bash and change the ARM_BASE_BUILDOS to point to your kernel build tree
4. run the build_arm.bash script
   

   .../dsplink# . ./setenv-bash
   .../dsplink# . ./build_arm.bash
   

If it works, there should be a gpp/export/BIN/Linux/OMAPL138/dsplinkk.ko file (newly built, check the timestamps)

-Mike

I updated my instructions to clarify the commands on the last post...

-Mike