From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ob0-f174.google.com ([209.85.214.174]:37445 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753642Ab2D1NvJ convert rfc822-to-8bit (ORCPT ); Sat, 28 Apr 2012 09:51:09 -0400 Received: by obbta14 with SMTP id ta14so2238491obb.19 for ; Sat, 28 Apr 2012 06:51:08 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 28 Apr 2012 10:51:08 -0300 Message-ID: Subject: Re: video capture driver interlacing question (easycap) From: =?ISO-8859-1?Q?Ezequiel_Garc=EDa?= To: linux-media Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-media-owner@vger.kernel.org List-ID: On Thu, Apr 26, 2012 at 5:33 PM, Ezequiel García 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?