• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 429 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Rebuilding cmemk.ko dsplinkk.ko lpm_omap3530.ko

msj
Intellectual 830 points
Other Parts Discussed in Thread: OMAP3530

I rebuilt the linux kernel with OMAP35x-PSP-SDK-02.01.01.08, but now it appears I need to rebuild cmemk.ko, dsplinkk.ko and lpm_omap3530.ko libraries.

 

The instructions and Rules.mak refrence the MV tools not the code sourcery tools. 

Are there instructions for rebuild these libraries with the code sourcery tools?

 

Thanks for any help.

  • 0
    Prodigy 10 points

    I want to know too.

    I've updated the kernel to 2.6.29-rc3-omap1 with OMAP35x-PSP-SDK-02.01.03.11.

    But when I use insmod, met:

    cmemk: disagrees about version of symbol __class_create
    cmemk: Unknown symbol __class_create
    cmemk: disagrees about version of symbol class_destroy
    cmemk: Unknown symbol class_destroy
    cmemk: disagrees about version of symbol device_create
    cmemk: Unknown symbol device_create
    cmemk: disagrees about version of symbol device_destroy
    cmemk: Unknown symbol device_destroy
    insmod: cannot insert 'cmemk.ko': unknown symbol in module

    Need rebuilding these *.ko??

  • 0 in reply to chao c
    TI__Guru*** 125430 points

    Have you considered moving all the way to the current DVSDK 3.01?

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest/index_FDS.html

    There have been a lot of improvements in terms of the ease of use.  Specifically, the top level makefile is capable of building all of these components you are having trouble with.  This makes life MUCH easier.

    It's been a while since I've dug into those components due to the improvements I've cited, but as I recall those components contained their own makefile and Rules.make.  You need to edit the Rules.make similar to the top-level DVSDK (lots of copy/paste) and then you can build it.  Dsplink is a little tougher.  There is a perl configuration script you need to run first and there are several files that need to be edited.  These changes in the most recent DVSDK are particularly helpful in rebuilding dsplink.  I recommend making the move if possible.

    Brad