<div dir="ltr">On Tue, Jun 11, 2013 at 1:24 PM, Jeff Siddall <span dir="ltr"><<a href="mailto:news@siddall.name" target="_blank">news@siddall.name</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 06/09/2013 05:31 PM, Paul Kendall wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This device is actually very good.<br>
The API for h264/mpeg decode is the v4l2 API in linux. It looks like Samsung<br>
supplied patches and drove some of the changes for v4l2.<br>
Theres a git repo<br>
<a href="http://git.infradead.org/users/kmpark/public-apps/tree/HEAD:/v4l2-mfc-example" target="_blank">http://git.infradead.org/<u></u>users/kmpark/public-apps/tree/<u></u>HEAD:/v4l2-mfc-example</a><br>
that provides a sample program showing how to use the v4l2 api for decoding!<br>
<br>
If this was build in to MythTV then I think it would make a very nice<br>
frontend.<br>
Of course you'd have to consider the deinterlacing, but a quad core<br>
1.7GHz should be<br>
capable, right.<br>
</blockquote>
<br>
Quad core ARM? Umm... not likely. ARM != i7<br></blockquote><div><br></div><div style>For deinterlacing? the decode will be HW accelerated.</div></div></div></div>