All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Walter Van Eetvelt <walter@van.eetvelt.be>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media <linux-media@vger.kernel.org>,
	workshop-2011@linuxtv.org
Subject: Re: RFC: V4L2 API ambiguities
Date: Mon, 13 Aug 2012 18:55:04 -0300	[thread overview]
Message-ID: <502977B8.8030201@redhat.com> (raw)
In-Reply-To: <CAGoCfiyi9SRfz=wE18O6mO4z2G0=UVJgfrkx2O+tZ4nwBiARAA@mail.gmail.com>

Em 13-08-2012 18:42, Devin Heitmueller escreveu:
> On Mon, Aug 13, 2012 at 5:39 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> No, it is not out of scope. The thing is that none of the developers
>> that are going to be there proposed a DVB-specific themes, unfortunately.
>>
>> Yet, there are two themes there that are not V4L only: the userspace
>> discussions and the SoC discussions. I expect that it will focus at
>> the media API's as a hole, and not just V4L API.
> 
> I'm talking specifically about a discussion of "V4L2 API Ambiguities",
> which is the topic of this thread and the meeting in question.

OK. With that regards, you're right.

> I
> realize other parts of the conference include DVB.  If you want me to
> start piling onto this thread will all the problems/deficiencies
> related to our DVB API, we can certainly do that.  However, none of
> the people on this thread will have any real insight into them given
> those individuals focus entirely on V4L2.

Yeah, but anyway we can try to cover the points that Walter
made during the DVB topics.

I suspect, however, that we need an RFC with a proposal for CI
decoupled from the demux, in order to be able to discuss it.

Regards,
Mauro

  reply	other threads:[~2012-08-13 21:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 12:27 RFC: V4L2 API ambiguities Hans Verkuil
2012-08-13 13:13 ` [Workshop-2011] " Hans de Goede
2012-08-13 14:52   ` Hans Verkuil
2012-08-13 14:58     ` Hans de Goede
2012-08-13 15:09   ` Ilyes Gouta
2012-08-13 19:15   ` Sylwester Nawrocki
2012-08-14  8:13     ` Hans de Goede
2012-08-14  0:00   ` Laurent Pinchart
2012-08-14  8:15     ` Hans de Goede
2012-08-13 16:09 ` Rémi Denis-Courmont
2012-08-13 20:27 ` Walter Van Eetvelt
2012-08-13 21:31   ` Devin Heitmueller
2012-08-13 21:39     ` Mauro Carvalho Chehab
2012-08-13 21:42       ` Devin Heitmueller
2012-08-13 21:55         ` Mauro Carvalho Chehab [this message]
2012-08-13 23:54 ` [Workshop-2011] " Laurent Pinchart
2012-08-14 10:54   ` Hans Verkuil
2012-08-14 11:06     ` Laurent Pinchart
2012-08-14 11:11       ` Hans Verkuil
2012-08-14 11:15         ` Laurent Pinchart
2012-08-14 11:32           ` Hans Verkuil
2012-08-14 11:42             ` Laurent Pinchart
2012-08-14 21:14               ` Guennadi Liakhovetski
2012-08-14 22:10                 ` Laurent Pinchart
2012-08-14 12:43     ` Hans de Goede
2012-08-14 12:44       ` Chinmay V S
  -- strict thread matches above, loose matches on Subject: below --
2012-10-15 11:35 Hans Verkuil
2012-10-17  6:38 ` 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=502977B8.8030201@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=walter@van.eetvelt.be \
    --cc=workshop-2011@linuxtv.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 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.