<br><br><div class="gmail_quote">On Fri, May 3, 2013 at 2:53 PM, Oliver Schinagl <span dir="ltr"><<a href="mailto:oliver+list@schinagl.nl" target="_blank">oliver+list@schinagl.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03-05-13 03:33, Piyush Verma wrote:<br>
> Ok So at list 3 people interested in H264 Encoding I have the encoding<br>
> example code mention by Henrik and I will available today here.<br>
><br>
> Besides I have worked before with H264 Encode/Decode with S5PV210 there<br>
> all source I have from kernel to userspace.<br>
><br>
> There are not much step for encode and decode hardly 5 calles for whole<br>
> decode or encode process. I think it would be possible to easily reverse<br>
> Engineering.<br>
><br>
> Overall step in my mind is<br>
><br>
> 1 Get a NAL Unit.<br>
> 2. Write to Special decode memory or pass pointer.<br>
> 3 Call Hardware Decode Function.<br>
> 4 Check if all picture decode.<br>
> 5 Read Picture from output memory.<br>
><br>
> Same for encode.<br>
><br>
> Can't we log this 5 call in Kernel and understand then call and sequence<br>
> after running user space program ?<br>
><br>
> Give me some feedback if all ok why not we start for it.<br>
</div>Nobody has taken the time to start it.<br>
<br>
So far what we have for reverse engineerd cedar:<br>
<br>
Ianb's github that has some wrapper functions to help trace things<br>
Opensource kernel modules, adding extra info to extract stuff shouldn't<br>
be hard<br>
info on libcedar (or what was it called) that it looks like they took<br>
ffmpeg libraries and hacked in cedar support.<br></blockquote><div><br>I think that is longer path.<br>The whole cedar have lots of thing which is out of hardware decoding.<br><br>For whole video we just need to thing Hardware Decoding + Post Process to render on screen.<br>
<br>Post process is already open (All Code) at this time we just need to get only decode / encode process make working.<br><br>All other process we can achieve simple with FFMpeg.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">><br>
><br>
><br>
><br>
><br>
> On Fri, May 3, 2013 at 8:41 AM, Dmitriy B. <<a href="mailto:rzk333@gmail.com">rzk333@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:rzk333@gmail.com">rzk333@gmail.com</a>>> wrote:<br>
><br>
> I have seen encoding libs & examples in the SDK files, and know that<br>
> some people have attemted to use them with at least partial success.<br>
><br>
><br>
> But "SDK files" != "public cedarx-libs repo", and you cant share<br>
> these examples, right?<br>
> I am interested in encoding with CedarX too, but I dont have the<br>
> full SDK.<br>
><br>
> _______________________________________________<br>
> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
</div>> <mailto:<a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a>><br>
<div class="im">> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</div>> <mailto:<a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a>><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
><br>
><br>
> --<br>
> Thanks & Regards<br>
><br>
> Piyush Verma<br>
><br>
><br>
><br>
<br>
<br>
<br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Thanks & Regards<br><br>Piyush Verma<br><br>