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.

DVSDK and kernel versions

Other Parts Discussed in Thread: OMAP3530

Good afternoon,

I'm not sure if it has been discussed on this list or elsewhere, but I'm having an issue where my board support vendors are transitioning to the 2.6.28 kernel with no plans to backport drivers, etc.

Will DVSDK be tied forever to 2.6.22?  My application will only be using a subset of DVSDK stuff (I think just dsplink and local power manager).  Is it safe to use any of this with later kernels?

Curious what other people are experiencing ...

  • Oops, forgot to mention, I'm running on OMAP3530.

  • I am not aware of any immediate plans to transition OMAP35x DVSDK to newer kernels, though I am pretty sure this will happen eventually.

    FYI, have you heard of our beagle board (http://beagleboard.org/), which is also based on OMAP35x family; I believe the beagle board open source community is using kernel 2.6.28 at the moment.

  • Hi,

    Well, I would say if you have board support vendors they should probably care for supporting the software tools if they are moving to a newer kernel :S

    I understand that there are official plans in the future for OMAP SDKs to support git kernels (and therefore the DVSDK), but don't hold your breath for it. That said, it doesn't seems that hard to support what you are looking for, dsplink and lpm currently run well on 2.6.28 with OE patches for beagle (we have been in a marathon this week with guys from OE, TI and RidgeRun adding support for the DVSDK infrastructure to beagle on 2.6.28 kernel).

    So, your vendor or yourself should be able to add support for what you need in 2.6.28 kernel. If you need some help, we can provide custom engineering services for it ;)

    Regards,

    Diego Dompe

    RidgeRun Engineering