Hi everybody, while trying to debug a serial port issue, I found out some code might seemed to miss write memory barriers. Does the volatile keyword guarantee that gcc will no reorder memory writes, or is the attached patched needed ?
Best regards, Laurent Pinchart -------------- next part -------------- A non-text attachment was scrubbed... Name: cpm_wmb.patch Type: text/x-diff Size: 578 bytes Desc: not available Url : http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060517/dbb2412a/attachment.patch