• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 243 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.

Linux version selection questions

EugeneS
Prodigy 150 points
Other Parts Discussed in Thread: DM3730, SYSBIOS

Our board which uses DM3730 has LS-Research wireless module(Ti-Wifi 1271) and vendor we are working with says

that in order to operate this module in the AP mode we probably better start using Linux kernel 3.x.

On the hand we depend on TI DVSDK's codecs server package for (video encode/decode) and dsplink Linux kernel driver which we think

right now works on the Linux kernel 2.6.37.

 

Here is our questions:

 

1. Is it true that LS-Research wireless module(Ti-Wifi 1271) can be used in the AP mode only with kernels 3.x?

If yes, then what extra functionality is missing in the the 2.6.37 Linux kernel?

2. Does TI plan to support codecs server package and dsplink driver on Linux kernel versions 3.x?

If yes then when?

 

3. We know that there is the SysLink product which in some way is the successor of the DspLink.

Does SysLink package support DM3730?

Does TI plan to release DVSDK and codecs server package for the SysLink or we better stick

with the latest TI DVSDK which currently uses DspLink given the fact that we want to release

our product in a year from the spring of 2012?

 

4. Are we doing the right thing while trying to use 2.6.37 kernel version instead of 3.x? (May be TI's drivers for all the peripherals

of the DM3730 are already included into the Linux kernel 3.x source tree?)

Are there any benefits when using Linux kernel 2.6.37 (OMAPPSP_04.02.00.07) from TI for the DM3730?

Thank you

  • 0
    Expert 1600 points

     

    EugeneS said:

    1. Is it true that LS-Research wireless module(Ti-Wifi 1271) can be used in the AP mode only with kernels 3.x?

    If yes, then what extra functionality is missing in the the 2.6.37 Linux kernel?

    [ORB] -- Let me get back to you on this.. I don't believe there is AP support. Can you ping LS-Research on the need for 3.x kernel support? Worst case you could try to back port some features from 3.x to 2.6.37. This depends on what is needed on 3.x for AP support.

     

    EugeneS said:

    2. Does TI plan to support codecs server package and dsplink driver on Linux kernel versions 3.x?

    If yes then when?

     

    [ORB] -- At this time we are only supporting 2.6.37 kernel based from our SDK offering. There is no plans to move to 3.x in the near future. I'll update this post if this changes.

    EugeneS said:

    3. We know that there is the SysLink product which in some way is the successor of the DspLink.

    Does SysLink package support DM3730? Does TI plan to release DVSDK and codecs server package for the SysLink or we better stick

    with the latest TI DVSDK which currently uses DspLink given the fact that we want to release

    our product in a year from the spring of 2012?

    [ORB] -- SYSBIOS is available for DM37x. Please see: http://www.ti.com/product/dm3730#softTool and http://www.ti.com/tool/sysbios for more information. However if you wish to avoid complications I would stick to our SDK offering. The SDK has everything you need for development. It's been tested and validated on 2.6.37. It will also provides you with proper documentation for designing your applications. Do you have any reason for targeting SYSlink vs DSPlink?

    EugeneS said:

    4. Are we doing the right thing while trying to use 2.6.37 kernel version instead of 3.x? (May be TI's drivers for all the peripherals

    of the DM3730 are already included into the Linux kernel 3.x source tree?)

    Are there any benefits when using Linux kernel 2.6.37 (OMAPPSP_04.02.00.07) from TI for the DM3730?

    [ORB] -- Again, I suggest sticking with our latest SDK offering. If you choose to move to a newer kernel please plan on porting efforts as well as test and validation.

    Thank you