• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 287 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.

kernel and filesystem not compatible,

Andre16038
Expert 1915 points

I downloaded revision 37  source code for the DM365 and I downloaded revision 37 filesystem from arago.

the kernel image file goes under "2.6.32-rc2-davinci1"

I also I downloaded revision 38  source code for the DM365 and I downloaded revision 38 filesystem from arago.

the kernel image file goes under "2.6.32.17-davinci1"

if I use the the kernel from revision 38 with the filesystem from revision 37 it does not work it says module are not compatible,  even if I change on the kernel in the make file from 2.6.32.17-davinci1 to 2.6.32-rc2-davinci1, is they any other changes I have to make besides the make file or do know of any instructions of how to build the modules on the filesystem to be compatible with a different kernel version?

  • 0
    Guru 26430 points

    Except for the loadable modules, I usually find the kernel is more or less okay with any file system. I usually build the kernel first, then build the modules, eg.

    make modules ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

    Optionally you can install the modules on top of the existing FS (in /lib/modules) with

    make modules modules_install INSTALL_MOD_PATH=path_to_target_root ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

    I guess if you are loading modules automatically on boot, you need to install the modules. Otherwise, you should be able to just copy a specific .ko module out from the built kernel and load manually.

     

  • 0 in reply to Norman Wong
    Expert 1915 points

    Thank you, that answers me that question, do you have any idea about the the GStreamer modules to be compatible with the kernel and filesystem I'm running

    http://e2e.ti.com/support/embedded/f/354/t/110943.aspx

  • 0 in reply to Andre16038
    Guru 26430 points

    Usually you compile your external modules in context of the kernel build. In your external module directory, something like this:

    make -C path_to_your_kernel SUBDIRS=path_to_your_other_kernel_code modules

    GStreamer looks to be tied up with bitbake. I don't know anything about GStreamer or bitbake.