public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	"media-workshop@linuxtv.org" <media-workshop@linuxtv.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Agenda for the Edinburgh mini-summit
Date: Fri, 30 Aug 2013 10:31:23 -0300	[thread overview]
Message-ID: <20130830103123.0bb6a256@samsung.com> (raw)
In-Reply-To: <52209C41.8040402@schinagl.nl>

Em Fri, 30 Aug 2013 15:21:05 +0200
Oliver Schinagl <oliver+list@schinagl.nl> escreveu:

> On 30-08-13 15:01, Hans Verkuil wrote:
> > OK, I know, we don't even know yet when the mini-summit will be held but I thought
> > I'd just start this thread to collect input for the agenda.
> >
> > I have these topics (and I *know* that I am forgetting a few):
> >
> > - Discuss ideas/use-cases for a property-based API. An initial discussion
> >    appeared in this thread:
> >
> >    http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/65195
> >
> > - What is needed to share i2c video transmitters between drm and v4l? Hopefully
> >    we will know more after the upcoming LPC.
> >
> > - Decide on how v4l2 support libraries should be organized. There is code for
> >    handling raw-to-sliced VBI decoding, ALSA looping, finding associated
> >    video/alsa nodes and for TV frequency tables. We should decide how that should
> >    be organized into libraries and how they should be documented. The first two
> >    aren't libraries at the moment, but I think they should be. The last two are
> >    libraries but they aren't installed. Some work is also being done on an improved
> >    version of the 'associating nodes' library that uses the MC if available.
> >
> > - Define the interaction between selection API, ENUM_FRAMESIZES and S_FMT. See
> >    this thread for all the nasty details:
> >
> >    http://www.spinics.net/lists/linux-media/msg65137.html
> >
> > Feel free to add suggestions to this list.

>From my side, I'd like to discuss about a better integration between DVB
and V4L2, including starting using the media controller API on DVB side
too. Btw, it would be great if we could get a status about the media
controller API usage on ALSA. I'm planning to work at such integration
soon. 

> What about a hardware accelerated decoding API/framework? Is there a 
> proper framework for this at all? I see the broadcom module is still in 
> staging and may never come out of it, but how are other video decoding 
> engines handled that don't have cameras or displays.
> 
> Reason for asking is that we from linux-sunxi have made some positive 
> progress in Reverse engineering the video decoder blob of the Allwinner 
> A10 and this knowledge will need a kernel side driver in some framework. 
> I looked at the exynos video decoders and googling for linux-media 
> hardware accelerated decoding doesn't yield much either.
> 
> Anyway, just a thought; if you think it's the wrong place for it to be 
> discussed, that's ok :)

Well, the mem2mem V4L2 devices should provide all that would be needed for
accelerated encoders/decoders. If not, then feel free to propose extensions
to fit your needs.

Regards,
Mauro

> 
> oliver
> >
> > Note: my email availability will be limited in the next three weeks, especially
> > next week, as I am travelling a lot.
> >
> > Regards,
> >
> > 	Hans
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-media" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 

Cheers,
Mauro

  reply	other threads:[~2013-08-30 13:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 13:01 Agenda for the Edinburgh mini-summit Hans Verkuil
2013-08-30 13:21 ` Oliver Schinagl
2013-08-30 13:31   ` Mauro Carvalho Chehab [this message]
2013-08-30 16:54     ` [media-workshop] " Laurent Pinchart
     [not found]       ` <CACHYQ-qyuP+MjWNc7bVHhUa0xxzQHEmb3JFe+9n6C0GzOnj54A@mail.gmail.com>
2013-08-31  0:03         ` Laurent Pinchart
     [not found]           ` <CACHYQ-qDD5S5FJvzT-oUBe+Y+S=CB_ZN+QNQPpu+BFE-ZPr45g@mail.gmail.com>
2013-08-31 20:19             ` Laurent Pinchart
     [not found]               ` <CA+M3ks7whrGtkboVcstoEQBRTkiLGF7Hf9nEsYEkyUD6=QPG9w@mail.gmail.com>
2013-09-04 10:48                 ` Mauro Carvalho Chehab
2013-09-05 11:37                   ` Hugues FRUCHET
2013-09-06 13:45                     ` Laurent Pinchart
2013-09-07  9:31                       ` Pawel Osciak
2013-09-10  9:44                         ` Laurent Pinchart
2013-09-09 10:32                     ` Hans Verkuil
2013-09-10  7:36                       ` Hugues FRUCHET
2013-09-10  7:54                         ` Hans Verkuil
2013-08-30 13:54   ` Hans Verkuil
2013-08-31  6:43 ` Hans Verkuil
2013-08-31 18:38   ` [media-workshop] " Guennadi Liakhovetski
2013-08-31 20:25     ` Laurent Pinchart
2013-08-31 20:36       ` Guennadi Liakhovetski
2013-09-01 11:13         ` Hans Verkuil
2013-08-31 14:40 ` Sakari Ailus

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=20130830103123.0bb6a256@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=media-workshop@linuxtv.org \
    --cc=oliver+list@schinagl.nl \
    /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