All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [REVIEW] au0828-video.c
Date: Fri, 12 Dec 2014 15:36:38 -0200	[thread overview]
Message-ID: <20141212153638.6ecb9664@recife.lan> (raw)
In-Reply-To: <CAGoCfiywSrq0f-L6a2LOS=ZS7xzfUJym46njesR8TkfoybQ5Pw@mail.gmail.com>

Em Fri, 12 Dec 2014 11:46:13 -0500
Devin Heitmueller <dheitmueller@kernellabs.com> escreveu:

> >> In short, that code cannot be removed.
> >
> > Sure it can. I just tried tvtime and you are right, it blocks the GUI.
> > But the fix is very easy as well. So now I've updated tvtime so that
> > it timeouts and gives the GUI time to update itself.
> 
> That's a nice change to tvtime and I'm sure it will make it more robust.
> 
> > No more need for such an ugly hack in au0828. The au0828 isn't the only
> > driver that can block, others do as well. Admittedly, they aren't very
> > common, but they do exist. So it is much better to fix the application
> > than adding application workarounds in the kernel.
> 
> You're breaking the ABI.  You're making a change to the kernel that
> causes existing applications to stop working.  Sure you can make the
> argument that applications probably never should have expected such
> behavior (even if it's relied on that behavior for 15+ years).  And
> sure, you can make a change to the application in some random git
> repository that avoids the issue, and that change might get sucked in
> to the major distributions over the next couple of years.  That
> doesn't change the fact that you're breaking the ABI and everybody who
> has the existing application that updates their kernel will stop
> working.
> 
> Please don't do this.

I agree. We should not break the ABI, except if we're 100% sure that
all apps that rely on the old behavior got fixed at the distros.

That means that we'll need to keep holding such timeout code for
years, until all distros update to a new tvtime, of course assuming
that this is the only one application with such issue.

With regards to tvtime, I think we need to bump version there and
update it at the distros.

I added myself a few patches today, in order to fix it to work with
vivid driver on webcam mode.

My proposal is to wait for one extra week for people to review it.

As we've discussed on IRC channel, it would be good to add support
for format enumeration on it, but the changes don't seem to be
trivial. I'm not willing to do it, due to my lack of time, but,
if someone steps up for doing that, then we can wait for those
patches before bumping the version.

In anycase, if everything is ok after ~1 week of waiting for
tests, we can bump to version 1.0.5 and I can port the latest
version to Fedora. I dunno who maintains it on other distros.

Regards,
Mauro

  reply	other threads:[~2014-12-12 17:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 10:16 [REVIEW] au0828-video.c Hans Verkuil
2014-12-12 12:49 ` Mauro Carvalho Chehab
2014-12-12 12:55   ` Hans Verkuil
2014-12-12 13:14     ` Mauro Carvalho Chehab
2014-12-12 15:26       ` Shuah Khan
2014-12-12 15:28         ` Hans Verkuil
2014-12-12 15:30           ` Shuah Khan
2014-12-12 15:52           ` Devin Heitmueller
2014-12-12 16:32             ` Hans Verkuil
2014-12-12 16:46               ` Devin Heitmueller
2014-12-12 17:36                 ` Mauro Carvalho Chehab [this message]
2014-12-12 17:46                   ` Devin Heitmueller
2014-12-12 15:23 ` Shuah Khan

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=20141212153638.6ecb9664@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=shuahkh@osg.samsung.com \
    /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.