• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 508 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.

two different MSGQ_alloc() have two different parameter orders

bowerymarc
Expert 1935 points
Other Parts Discussed in Thread: OMAP-L138, SYSBIOS

just ran into this... TI?

compare this definition from dsplink's msgq.h:

EXPORT_API

DSP_STATUS

MSGQ_alloc (IN PoolId poolId, IN Uint16 size, OUT MSGQ_Msg * msg) ;

with this one from dspbios' msgq.h:

extern Int  MSGQ_alloc(Uint16 poolId, MSGQ_Msg *msg, Uint16 size);

Notice anything fishy?

(ran into this as I was moving code between gpp and dsp)


  • 0
    TI__Guru* 96960 points

    Unfortunately different groups were doing concurrent development within TI and some inconsistencies occurred. These inconsistencies were addressed in Syslink and SYS/BIOS.

    Todd

  • 0 in reply to ToddMullanix
    Expert 1935 points

    thanks for the forthright answer Todd.  

    as I look at the DVSDK 4.03 (OMAP-L138) it seems like the 4.02 I'm currently on, where DSPBIOS5 is the basis for all the other libraries and the examples (though I do see DSPBIOS6 in there, it doesn't seem to be the default... DSPBIOS6 is SYSBIOS?)   If this observation is correct, what's the roadmap for switching all that stuff over so the DVSDK uses syslink / sysbios as the default?

    thanks.

  • 0 in reply to bowerymarc
    TI__Guru* 96960 points

    You should post this on the linux forum (http://e2e.ti.com/support/embedded/linux/default.aspx). They know the DVSDK roadmap and component versions.

    Todd