mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@skynet.be>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	video4linux-list@redhat.com,
	"v4l-dvb maintainer list" <v4l-dvb-maintainer@linuxtv.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	davinci-linux-open-source-bounces@linux.davincidsp.com
Subject: Re: [PULL] http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-ng
Date: Tue, 2 Dec 2008 17:58:35 +0100	[thread overview]
Message-ID: <200812021758.35503.laurent.pinchart@skynet.be> (raw)
In-Reply-To: <20081201130643.661f5743@pedra.chehab.org>

Hi Mauro,

On Monday 01 December 2008, Mauro Carvalho Chehab wrote:
> Hi Hans,
>
> On Mon, 1 Dec 2008 15:24:43 +0100
>
> Laurent Pinchart <laurent.pinchart@skynet.be> wrote:
[snip]

> > In a few months time (probably even earlier) the v4l2_device structure
> > will be reworked (and possible renamed).
>
> Hmm... why? it would be better to try to have the KABI changes for it at
> the same kernel release if possible.

Because Hans is working on more changes.

> > I'm fine with it going to linux-next now if
> > we agree on the following.
> >
> > - We should only advocate v4l2_device usage for subdevices-aware video
> > devices. Porting all drivers to v4l2_device is currently pointless and
> > will only make future transitions more difficult.
>
> This makes sense to me.
>
> > - v4l2_device should be marked as experimental. I don't want to hear any
> > API/ABI breakage argument in a few months time when the framework will
> > evolve.
>
> Are you meaning marking this as experimental at Kconfig? This seems too
> complex, since we'll need to test for some var on every driver that were
> converted, providing two KABI options for each converted driver (the legacy
> and the v4l2_device way). This doesn't seem to be a good idea, since will
> add a lot of extra complexity to debug bugs.

Not at the Kconfig level, just in the documentation (and possible headers).

This is a work in progress. Hans wants the changes to go mainline to get 
broader testing, which is a valid reason, but I'd like to make sure people 
understand that more changes are coming.

Best regards,

Laurent Pinchart

  parent reply	other threads:[~2008-12-02 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 11:46 Hans Verkuil
2008-12-01 12:27 ` Mauro Carvalho Chehab
2008-12-01 12:31   ` Hans Verkuil
2008-12-01 12:31 ` Laurent Pinchart
2008-12-01 12:51   ` Hans Verkuil
2008-12-01 13:29     ` Laurent Pinchart
2008-12-01 13:45       ` Hans Verkuil
2008-12-01 14:24         ` Laurent Pinchart
2008-12-01 14:47           ` Hans Verkuil
2008-12-02 17:01             ` Laurent Pinchart
2008-12-01 15:06           ` Mauro Carvalho Chehab
2008-12-01 18:07             ` Hans Verkuil
2008-12-02 16:58             ` Laurent Pinchart [this message]
2008-12-02 17:21               ` Mauro Carvalho Chehab
2008-12-02 17:26                 ` Hans Verkuil
2008-12-02  0:02         ` Andy Walls

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=200812021758.35503.laurent.pinchart@skynet.be \
    --to=laurent.pinchart@skynet.be \
    --cc=davinci-linux-open-source-bounces@linux.davincidsp.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®