public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: tw686x driver
Date: Fri, 4 Mar 2016 12:11:51 +0100	[thread overview]
Message-ID: <56D96D77.4060707@xs4all.nl> (raw)
In-Reply-To: <m3d1raojqq.fsf@t19.piap.pl>

On 03/04/2016 07:11 AM, Krzysztof Hałasa wrote:
> Hans Verkuil <hverkuil@xs4all.nl> writes:
> 
>>> Staging is meant for completely different situation - for immature,
>>> incomplete code. It has nothing to do with the case.
>>
>> It can be for anything that prevents it from being mainlined. It was (still is?)
>> used for mature android drivers, for example.
> 
> What is preventing my driver from being mainlined?

I have two drivers with different feature sets. Only one can be active
at a time. I have to make a choice which one I'll take and Ezequiel's
version has functionality (audio, interlaced support) which matches best
with existing v4l applications and the typical use cases. I'm not going
to have two drivers for the same hw in the media subsystem since only
one can be active anyway. My decision, although Mauro can of course decide
otherwise.

I am OK with adding your driver to staging in the hope that someone will
merged the functionalities of the two to make a new and better driver.

Whether that means that Ezequiel's code is merged into yours or vice versa,
I really don't care.

My goal is to provide the end-user with the best experience, and this is
IMHO the best option given the hand I've been dealt.

I ordered a tw6869-based PCIe card so I can do testing myself once it has
arrived.

Regards,

	Hans

  reply	other threads:[~2016-03-04 11:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  8:32 tw686x driver Hans Verkuil
2016-03-03  6:51 ` Krzysztof Hałasa
2016-03-03  7:32   ` Hans Verkuil
2016-03-03 12:41     ` Krzysztof Hałasa
2016-03-03 13:37       ` Hans Verkuil
2016-03-03 14:22         ` Krzysztof Hałasa
2016-03-03 14:39           ` Hans Verkuil
2016-03-04  6:11             ` Krzysztof Hałasa
2016-03-04 11:11               ` Hans Verkuil [this message]
2016-03-04 12:37                 ` Krzysztof Hałasa
2016-03-04 13:40                   ` Hans Verkuil
2016-03-07  6:41                     ` Krzysztof Hałasa
2016-03-10  7:16                     ` Krzysztof Hałasa
2016-03-10  7:24                       ` Hans Verkuil

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=56D96D77.4060707@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=khalasa@piap.pl \
    --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