All of lore.kernel.org
 help / color / mirror / Atom feed
* video capture driver interlacing question (easycap)
@ 2012-04-26 20:33 Ezequiel García
  2012-04-28 13:51 ` Ezequiel García
  0 siblings, 1 reply; 4+ messages in thread
From: Ezequiel García @ 2012-04-26 20:33 UTC (permalink / raw)
  To: linux-media

Hi everyone,

As you may know I'm re-writing from scratch the staging/easycap driver.

Finally, after digging through the labyrinthic staging/easycap code,
I've reached a point where I'm able to understand isoc packets.
Despite not having any documentation (I asked several times) from chip vendor,
I can separate packets in odd and even.

So, instead of receiving frames the device is sending me fields, right?

My doubt now is this:
* Do I have to *merge* this pair of fields for each frame, or can I
give it to v4l?
If affirmative: how should I *merge* them?
* Is this related to multiplanar buffers (should I use vb2_plane_addr)?

Currently, staging/easycap does some strange and complex conversion,
from the pair of fields buffers, to get a "frame" buffer (!) but I'm
not sure if it's the correct way to do it?

I guess I can keep staring at em28xx (together with vivi/uvc/pwc) driver,
but if someone cares to give me a small hint or point me at a small portion
of code I'll be grateful.

Thanks,
Ezequiel.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-04-29 21:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-26 20:33 video capture driver interlacing question (easycap) Ezequiel García
2012-04-28 13:51 ` Ezequiel García
2012-04-28 21:37   ` Guennadi Liakhovetski
2012-04-29 21:04     ` Ezequiel García

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.