From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Raffaele Recalcati <lamiaposta71@gmail.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: tvp5150 extension to tvp5151
Date: Mon, 22 Nov 2010 09:32:25 -0200 [thread overview]
Message-ID: <4CEA54C9.4030300@infradead.org> (raw)
In-Reply-To: <AANLkTinTwyioFt2mGmetK=rfj-q_7hLBQ_FR_aE20FXZ@mail.gmail.com>
Hi Raffaele,
Em 19-11-2010 16:26, Raffaele Recalcati escreveu:
> I need to support fully tvp5151.
> So I'm trying to understand your driver, that is ready for VBI and not
> for video acquisition.
> I also take sometimes a look at tvp514x.c, for instance trying to add
> VIDIOC_ENUM_FMT and other ioctls.
> I think we can move from tvp5150.c to tvp515x.c, maybe...
> I don't think is good to have tvp51xx.c because tvp514x.c family is
> more complex (more inputs...).
> By now I'm using tvp5150.c with some modifications and video acquisition works.
> I need to complete the support in order to have gstreamer fully running.
> I'm working on 2.6.32, but I have planned to port it to mainline.
Renaming it to tvp515x.c and adding support for tvp5051 seems a good way.
With tvp5150, video acquisition works fine with several devices with em28xx,
although we may need to add more video formats at the media bus, depending
on what you're doing. I didn't test VBI support on it, because the devices
I have are based on em28xx, and I didn't find any way to capture the VBI
decoded packages and sent to userspace with that design. So, the basic stuff
is there, but maybe some adjusts may be needed for VBI.
> Do you have any suggestion for my work?
The better is to submit the patches you have, for us to apply upstream.
Cheers,
Mauro
next prev parent reply other threads:[~2010-11-22 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 18:26 tvp5150 extension to tvp5151 Raffaele Recalcati
2010-11-22 11:32 ` Mauro Carvalho Chehab [this message]
2010-11-22 14:44 ` Raffaele Recalcati
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=4CEA54C9.4030300@infradead.org \
--to=mchehab@infradead.org \
--cc=lamiaposta71@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox