Hi Joe, > After digging a bit further I found that the problem isn't lost characters or character corruption at all... > > The UART is actually at 430KBaud (not 900KBaud as I mentioned earlier). How did you verify that register read? The data received is very bursty (i.e. sets of messages every second or so), containing a > sync sequence to indicate a start of packet. > > The received bytes should be: 0x01, 0x52, 0x41 ....rest of packet. > > This works 100% of the time on 3.2, but on 3.3 I sometimes (but not always) get: 0x01, 0x00, 0x52, 0x41. > > i.e. there is a NULL/0x00 inserted after the first character. > > All this is tested using a very simple userspace application thats reads data from ttyO1. > > Any ideas? Should I kick open a new thread as it's not really to do with suspend anymore? Is there any flow control you are using? > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
