All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ezequiel García" <elezegarcia@gmail.com>
To: linux-media <linux-media@vger.kernel.org>
Subject: Re: video capture driver interlacing question (easycap)
Date: Sat, 28 Apr 2012 10:51:08 -0300	[thread overview]
Message-ID: <CALF0-+Xz8RkGkjSg8n45POLQKWpFUhsNQCPpth4NK9Svhc+4SA@mail.gmail.com> (raw)
In-Reply-To: <CALF0-+WaMObsjmpqF8akQwaizETsS2zg05yT5fcOTA5CT=wLJA@mail.gmail.com>

On Thu, Apr 26, 2012 at 5:33 PM, Ezequiel García <elezegarcia@gmail.com> wrote:
> 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.

Anyone?

  reply	other threads:[~2012-04-28 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 20:33 video capture driver interlacing question (easycap) Ezequiel García
2012-04-28 13:51 ` Ezequiel García [this message]
2012-04-28 21:37   ` Guennadi Liakhovetski
2012-04-29 21:04     ` Ezequiel García

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALF0-+Xz8RkGkjSg8n45POLQKWpFUhsNQCPpth4NK9Svhc+4SA@mail.gmail.com \
    --to=elezegarcia@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.