Notices

Reviving this one year old issue. Got tearsync support working with Nokia 770 :-)


Working source patch http://fanoush.wz.cz/maemo/#tearsync.
Works for me but take is as experimental code. I have tested it with two (=all?) widely available 770 board revisions - 1602 and 1802.

For kernel image get one of SDHC ones http://fanoush.wz.cz/maemo/#sdhc it is now part of them. If you already flashed one of them before, please redownload and reflash, previous versions had the non-working tearsync version included by mistake. It was harmless unless you actually try it with mplayer and use options below.

All source patches and kernel configuration used for compiling the image is now inside .tar.gz file in 'source' directory.

After flashing zImage from the archive, you can test it with mplayer arguments '-vo nokia770:tearsync=1'. If it works, you can also set it as default by adding line to /home/user/.mplayer/config
Or to enable yuv420 mode too (gives slight speedup), you can add
So after approx. one year delay we finally have it working. What took so long? Basically it was just lack of information, magic words are "pin muxing, ball G20, register 4, value 6, offset 6". The original code posted year ago was OK, it was just a matter of enabling TE pin input on OMAP side. Sadly pin muxing is done in bootloader and 770 bootloader have this disabled. Also getting this information was a pain since TI pretends there is no such thing as SoSSI in OMAP1 chips, documentation for SoSSI was intentionally removed from current and some past revisions of OMAP5912 datasheets.

and of course it works. Beautifully. Many many thanks

thank you! works great!

Thanks, it works great.

A minor typo correction, you need to write 'vo=nokia770:tearsync=1:yuv420=1' in the configuration file to activate the use of both yuv420 mode and tearsync.

Anyway, I'll add automatic detection of kernel support for these features and mplayer will use them by default in the next build. So there would be no need tweaking configuration files (unless you would like to disable tearsync ) and just flashing an upgraded kernel would be enough for getting better video quality and performance.

Is it normal that mplayer (v. 1.0rc1-maemo.27 and 18) hangs on some divx movies when movie starts?

I got a similar question, for some mp4 file, the picture freezes while the sound plays smoothly, anyone got ideas?


BTW: I saw the new mplayer released, when will Maemo version update?


thanks guys,

Yes, it is too slow and has to skip frames. In your case it essentially skips almost all the frames.

Yes, it was released long ago. Moreover, a lot more features are available in SVN version of upstream mplayer which is unreleased yet. But I'm not working on this stuff at the moment, a new maintainer/packager joining garage mplayer project would help.

No, it's not normal.

Thanks, I did try with skipframe option under X-term and eventually I got a message that my n800 is too slow to play this movie. Sigh...


Do you mean 1.0rc2? I also saw updates for libdvdnav-4.1.3 and libdvdread-4.1.3.

Thanks anyway!

Is mplayer for maemo dead?