rdk 3.5 bug id detail description

SDOCM00096999 MSGQ free crashes when application uses signals

                               -- When application uses SIgnals it would cause syslink kernel modules like MessageQ to unblock and return error. This condition was not handled in RDK resulting in Message wrongly getting freed. This would result in MessageQ_put failing in applications that use signals.

                               -- Fix was in syslink to handle signals correctly and in RDK to handle error condition when a syslink API like MessageQ fails.

SDOCM00097028 Enabling DMA in SwMs causes A8 spurious irq when input is tiled

                            -- There was a bug in programming the EDMA xfer in SwMs link when input is tiled. This would cause a EDMA TCC error. The EDMA TCC Error would result in an interrupt on A8 and since there is no interrupt handler on A8 for EDMA TC error, it would result in a spurios irq warninf from kernel.

                           -- Fix was in SwMs link to handle tiled input correctly and not cause EDMA TC error

SDOCM00097029 MSGQ ListMP corruption

                           - When there is lot of MessageQ traffic with messages being sent simultaneously by multiple cores it would cause MessageQ and HeapMemMP data stuctures to get corrupted. You would see a syslink assert MSG on A8 or a M3/DSP exception.

                         -- Fix was in RDK to ensure Messages are freed in the same core they are alloced and changing the Mutli processor gate from GateHwSpinLock to GatePeterson for the HeapMemMP.

No it is not possible to create a patch for these issue on RDK 3.0 as changes are extensive and cannot be provided as patch.Only option is to migrate to RDK 3.5 release