• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 517 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.

Loading Ducati in 3.4 kernel

Kavitha bk
Prodigy 160 points

HI

I want to load Ducati from the shell in 3.4 kernel .Please guide me ow to do so

i was using syslink in 2.6.35 kernel but now icant use as it is deprecated

Thanks

  • 0
    TI__Intellectual 1165 points

    Kavith,

    I would recommend to start from a TI distribution such as "OMAP Ubuntu Core" (http://omappedia.org/wiki/OMAP_Ubuntu_Core) or "Ubuntu 12.04 Precise Pangolin desktop" (http://omappedia.org/wiki/Prebuilt_ubuntu_binaries). These contain the right version of kernel, kernel modules, ducati firmware, startup scripts, etc. In such distributions, ducati firmware is automatically loaded at bootup and video works off the shelf.

    Regards,

    -- Olivier

  • 0
    TI__Mastermind 24525 points

    Please note that on 2.6.35 kernel used in Honeycomb and before, syslink daemon was a user space  process. In 3.0 onwards syslink driver has moved entirely to kernel. This fundamentally changes the way Ducati is loaded.

    Please make sure that kernel config has IPU driver enabled.

  • 0 in reply to Mayank Mangla
    Prodigy 160 points

    Thanks Mayank

    I know now it is a Kernel Module.

    I want to know Whether on dynamically loading the IPU driver as .ko .Does it reload the Ducati xem3 from firmware folder again

    I dont want to re-boot to change the ducati binary everytime 

    Thanks

    Kavitha

  • 0 in reply to Kavitha bk
    TI__Mastermind 24525 points

    syslink driver is built-in the kernel. You can not load/unload it at runtime. Therefore every time Ducati changes, the board needs to be rebooted.