<div>Hi All,</div><div><br></div><div>I've built the kernel (allwinner-v3.0-android-v2) and installed it using the instructions for building a debian root fs (<a href="http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/Building_Debian_From_Source_Code_for_Mele/">http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/Building_Debian_From_Source_Code_for_Mele/</a>). </div>
<div><br></div><div>I've then gone through and compiled the code from the allwinner-a10-video <a href="https://github.com/amery/allwinner-a10-video">https://github.com/amery/allwinner-a10-video</a> repository and converted a video to be in a pmp container for testing. While it does work to a certain extent, frames are decoded and displayed most of the time (though they're displayed too quickly). The library also prints a lot of debugging messages to the console. Running the 've' command multiple times will cause a kernel oops followed by other oopses and then eventually a panic.</div>
<div><br></div><div>Note: I'm using the a10_video_decode/libvecoredemo_linux_A10 & libvecoredemo_linux_A10_with_display sample code.</div><div><br></div><div>The kernel panics looks like memory corruption to me, I've been digging about trying to see what causes it, though not found anything yet. For reference, with the same media file (though not in pmp format) the "CedarXPlayerTest-1.4.1" binary from the ubuntu image does not cause a panic and will play nicely (no stuttering etc).</div>
<div><br></div><div>Based on this I think that </div><div><br></div><div>a) libvecore.a is probably not going to be useful in its current state (or at least in the state that is available publicly)</div><div><br></div><div>
b) there seems to be a problem with the cedar_dev device driver, in that it is possible to corrupt kernel memory and crash the system.</div><div><br></div><div>Here are some sample Oops messages, they're different each time.</div>
<div><br></div><div><a href="http://pastebin.com/CXazJtxQ">http://pastebin.com/CXazJtxQ</a></div><div><br></div><div><a href="http://pastebin.com/6ec5cymG">http://pastebin.com/6ec5cymG</a></div><div><br></div><div>This is more of an FYI and to see if anyone knows where to look next with regards to resolving the kernel oops/panic.</div>
<div><br></div><div>Iain.</div><div><br></div><div><br></div>