• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 681 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.

DM365 LSP Linux version update plan

Woo-Seung Yeo35126
Intellectual 1890 points

Dear Champs,

 

My customer is using DM365 for IP camera design and wants to port WiFi driver to DVSDK.

The WiFi driver is created for up-to-date Linux kernel version 2.6.32 but DVSDK is based on Linux kernel version 2.6.18.

This version difference makes my customer hard in the driver porting.

Do we have Linux kernel version upgrade plan with DM365 DVSDK?

Please feel free to share your idea about how to make the porting easier.

 

Best Regards,

WS Yeo

  • 0
    TI__Mastermind 18320 points

    The DVSDK 3.10 product release will allow DM365 customers to port forward to the 2.6.32, as it is based on the Linux kernel from the DaVinci Git tree rather than the one from the MontaVista distro.  This product is still under development, but a beta release of DVSDK 3.10 will be made available later this month.

  • 0 in reply to David Friedland
    TI__Mastermind 25966 points

    Can anyone confirm that DVSDK_3_10_00_12 will allow the below customer to build libjpeg.a, libpng.a and libfreetype.a WITHOUT Montavista on DM365?

    >>Those libraries are included in the Montavista toolset but they are not compatible with the CodeSourcery linker.

    I guess this makes sense, but I don't understand why he thinks:

    >>The DVSDK_3_10_00_12 has source code examples that use the same calls I use in  my code. I have not rebuilt anything in the 3_10 dvsdk because I don't >>think that is the solution to this dilemma.

    Shouldn't building libjpeg.a, libpng.a and libfreetype.a in DVSDK_3_10_00_12 CodeSourcery solve his problem or are we missing something?
    Full e-mail below:
    Joe,
     
     I'm in the process of porting my project from DevRocket  to CodeSourcery. I have recreated the entire project but I'm running into trouble with some of my requirements. Specifically I am getting "unresolved externals" errors during the link process.
     
     We need to be able to decode JPEG and PNG files using the Arm because we may be playing out an MPEG file at the same time , so I can't use the coprocessor. I had all of this working in DevRocket, the problem is that support for this has been dropped in CodeSourcery or maybe I can't find what I need.
     
     In the past I used the libjpeg.a, libpng.a and libfreetype.a (I use this one to render fonts). Those libraries are included in the Montavista toolset but they are not compatible with the CodeSourcery linker.
    I also tried using the -Llibjpeg.so in the IDE but I still get unresolved externals for any reference to any JPEG method.
     
    The DVSDK_3_10_00_12 has source code examples that use the same calls I use in  my code. I have not rebuilt anything in the 3_10 dvsdk because I don't think that is the solution to this dilemma.
     
     If you can provide any insight or help into this matter it would be greatly appreciated.
     
    Thanks
     
    Manny
     
    PS: I'm under the gun , my DevRocket license expires this Friday
  • 0 in reply to Joe G.
    TI__Mastermind 25966 points

      I guess another way to ask is, do we have libjpeg.a, libpng.a and libfreetype.a binaries for DVSDK_3_10_00_12 that will link with CodeSourcery?

  • 0 in reply to Joe G.
    TI__Mastermind 25966 points

    Customer e-mailed that he solved.  Trying to get more detail.

  • 0 in reply to Joe G.
    TI__Mastermind 25966 points

    >>How did you solve the problem?  Were you able to link  with the MV libraries or did you find sources in in DVSDK_3_10?

     Linked to MV

  • 0 in reply to Joe G.
    TI__Prodigy 355 points

    All the libraries in question are part of the Arago filesystem and should be available from DVSDK 3.10

    By default, only shared libraries are installed on the filesystem (libjpeg.so, libpng.so, libfreetype.so), but their static versions (libjpeg.a, libpng.a, libfreetype.a) are also available in the form of IPK packages (with -static suffix) and can be installed with "opkg" tool.

    In order to link against those libraries, one needs to add "-ljpeg -lpng -lfreetype" to their gcc command line or Makefile.