Timo Juhani Lindfors schrieb: > Timo Juhani Lindfors <[email protected]> writes: >> This is a great improvement for GPS logging! Thank you very much. > > After a few more tests kernel printed > > [ 4782.350000] rxerr: port=1 ch=0x24, rxs=0x00000001 > [ 4966.170000] rxerr: port=1 ch=0x47, rxs=0x00000001 > > and gpsd printed > > gpsd: bad checksum in NMEA packet. > > Is the kernel too slow to read data from the serial port and some FIFO > gets too full?
Is this "sporadic", i.e. does this error occur sometimes and after the error it works again? It could also be that if there is traffic on the serial line in the very same moment when the frequency change occurs the UART looses its clock during the character reception. After the successful clock transition it could be OK again and until the next clock change occurs while receiving data. But I am guessing here... my reasoning behind it is that in SOC like the S3C many clocks are derived from the core clock so if the core clock changes that have to adjust as well. And if you do that while a clock is used as a timing source to sample bits from the serial port it can lead to data corruption (or loss of data). Just a halfway educated guess... > best regards, > Timo Lindfors Cheers nils faerber -- kernel concepts GbR Tel: +49-271-771091-12 Sieghuetter Hauptweg 48 Fax: +49-271-771091-19 D-57072 Siegen Mob: +49-176-21024535 http://www.kernelconcepts.de
