Hi Ezequiel,<div><br></div><div>I'll double check if V4L2 is suitable for my needs or if some minor modifications would make it more appropriate.</div><div><br></div><div>Best Regards,</div><div>Fred.<br><br><div class="gmail_quote">
2012/10/11 Ezequiel Garcia <span dir="ltr"><<a href="mailto:elezegarcia@gmail.com" target="_blank">elezegarcia@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Fred,<br>
<div class="im"><br>
On Thu, Oct 11, 2012 at 10:08 AM, EVS Hardware Dpt<br>
<<a href="mailto:hardware.evs@gmail.com">hardware.evs@gmail.com</a>> wrote:<br>
> Hi Ezequiel,<br>
><br>
> It's our own HD Sdi board. As far as I understand, being professional<br>
> broadcast oriented, it doesn't fall into V4L usage.<br>
><br>
<br>
</div>Wow, you read my mind, I was going to suggest you to look into<br>
V4L2 framework :-)<br>
If you've already considered and discarded that path, then that's fine.<br>
<br>
Let me just say V4L2 has evolved a lot and it's nowadays quite mature.<br>
If you ever plan to try to mainline your driver<br>
(which has an endless amount of benefits) then you should start<br>
by RFCing something to the linux-media list.<br>
<br>
If you implement a whole bunch of APIs out of tree, you may end<br>
with some weird implementation, which may be impossible to mainline<br>
and improbable to get support from developers around here.<br>
<br>
Of course, this is not necessarily your case.<br>
<br>
Hope this helps and good luck!<br>
<span class="HOEnZb"><font color="#888888"><br>
Ezequiel<br>
</font></span></blockquote></div><br></div>