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.

Undocumented OMAP-L137 changes in PSP 1.20.00

Other Parts Discussed in Thread: OMAP-L137

I've been waiting for the new PSP to fix several bugs in the headers for the CSLr for OMAP-L137 (specifically for the EDMA CC and PSC).

After downloading the latest release (1.20.00) I read the release notes and found no mention of changes to the CSLr, so expected the bugs to remain.

However, just to check I diff'ed the headers and found that infact the changes had been made.

So, my question is this: Is it common practice for TI to make changes to software releases without the supporting release notes detailing what those changes are?

If so this makes me slightly nervous as I do not want to have to check every release myself for any undocumentation changes that may affect my software development.

Cheers!

  • Joseph,

    Let us focus on this specific case.  If in this case there has been a miss  then it is an exception which needs to be corrected.   There was a similar post earlier http://e2e.ti.com/forums/p/5531/20920.aspx#20920 

    where we discussed and saw that the bugs/changes are documented in the release notes

    regards

    sathya

  • Thank you for your reply.

    I understand that the release notes contain a list of bugs/changes in that release (similar to the post you referenced, though that post was more directed at allowing access to pending bugs reported by other developers without having to wait for a subsequent release in which they are fixed).

    What concerned me was after reading the release notes is that it appears only "large" changes and bugs directly related to source driver code seems to have warranted entries in the release notes.

    What I have raised here are two distinct changes to two different modules (PSC and EDMA) in the CSLr, both of which are not documented.

    If both are indeed an oversight then that is fine, but I was concerned that it was more of a trend (as what may seem "minor" changes to header files may be deemed not warrant documentation). And if this is the case I am concerned.