From: Ratmansky, Richard []

Hi Patrick (et al),


Yes I am having trouble sending.  Booting up with an older build, I can send using a program I wrote to another device with no issues.  The exact same program on the newer build will receive just fine, but will only send if I start a separate process that heavily utilizes the cpu (very repeatable) to capture imagery from a usb camera and compress it to jpeg.  I don’t need that second process running with the earlier build. 


What is the name of the OMAP-specific module?  Is it a module loaded via udev or some other startup script?  

We used compiled-in support for the omap specific hardware.  The module name is "omap-serial" (if not compiled into kernel), but I think you may have a different problem.  My problem was caused by the CPU clock slowing down, then taking too long to step up again before getting an Rx overflow.  The only Tx issue we had was the automatic generation of XON/XOFF bytes.  These bytes were sent when the Rx buffer was nearly full, but did not impact our application since most of the communication was (effectively) half duplex and the other device just ignored the XON/XOFF bytes.

Thanks again,