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.

yocto meta-ti status for L138 (syslink)



hi,

trying the last meta-ti (git://git.yoctoproject.org/meta-ti) but it fails to build (for OMAP L-138) due to some patch missing (eg: https://e2e.ti.com/support/embedded/tirtos/f/355/p/451117/1623748#1623748).

I wonder if it was tested for L138.

Once applied all the patch I can build and load the syslink module, but it fails to run the examples.

best regards

Max

  • Hi,
    Yes, we have not tested syslink examples with latest kernel version.
    We have tested for linux kernel 3.3.
    What is your syslink version ?
  • Titusrathinaraj Stalin said:

    What is your syslink version ?

    I use syslink 2.21.01.05

    Titusrathinaraj Stalin said:
    Hi,
    Yes, we have not tested syslink examples with latest kernel version.
    We have tested for linux kernel 3.3.

    Ok, so meta-ti is not tested with L138, because meta-ti builds mainline kernel 3.14.43, and it seems that some patch aren't applied to syslink (eg: http://processors.wiki.ti.com/index.php/MCSDK_OMAPL138_User_Guide_Chapter_Exploring#Build_Syslink

    Anyway it seems that there isn't much work to do to make syslink works with more recent kernels (also 4.2). At least it seems to me

    best regards

    Max

  • Hi mastupristi,

    Not sure about kernel 3.14.
    Only for Linux kernel 3.3, it is been tested. The recommended version is 3.3

    mastupristi said:
    Anyway it seems that there isn't much work to do to make syslink works with more recent kernels (also 4.2). At least it seems to me


    You can go-ahead and give it a try. It will be useful for community members too. we haven't tried yet.

    ----
  • I did some tests:

    hardware: hawkboard

    syslink 2.21.01.05 patched (eg: http://processors.wiki.ti.com/index.php/MCSDK_OMAPL138_User_Guide_Chapter_Exploring#Build_Syslink)

    Linux Version Patch to syslink Patch to kernel test
    3.4.108 OK
    3.10.87 export symbol final_putname in file fs/namei.c OK
    3.12.47 export symbol final_putname in file fs/namei.c OK
    3.13.11 ioremap_cached become ioremap_cache in file ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c export symbol final_putname in file fs/namei.c OK
    3.14.43 ioremap_cached become ioremap_cache in file ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c export symbol final_putname and getname in file fs/namei.c OK
    3.18.21

    ioremap_cached become ioremap_cache in file ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c
    system.h become system_info.h in file ti/syslink/utils/hlos/knl/osal/Linux/OsalIsr.c

    export symbol final_putname and getname in file fs/namei.c OK
    4.0.9

    ioremap_cached become ioremap_cache in file ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c
    system.h become system_info.h in file ti/syslink/utils/hlos/knl/osal/Linux/OsalIsr.c

    export symbol putname and getname in file fs/namei.c OK
    4.1-rc1

    ioremap_cached become ioremap_cache in file ti/syslink/utils/hlos/knl/osal/Linux/MemoryOS.c
    system.h become system_info.h in file ti/syslink/utils/hlos/knl/osal/Linux/OsalIsr.c

    export symbol putname and getname in file fs/namei.c FAIL

    I cannot go further to this investigation, but maybe these infos are useful for somebody else in this community.

    best regards

    Max

  • Hi Mastupristi,
    Thanks for sharing your workaround.
    Surely it would help other community members as well.