public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	media-workshop@linuxtv.org,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [media-workshop] Tentative Agenda for the November workshop
Date: Thu, 25 Oct 2012 00:42:14 +0200	[thread overview]
Message-ID: <1372729.rmYJ0LutvU@avalon> (raw)
In-Reply-To: <50868685.5040701@samsung.com>

Hi Sylwester,

On Tuesday 23 October 2012 13:59:01 Sylwester Nawrocki wrote:
> On 10/23/2012 12:22 PM, Laurent Pinchart wrote:
> > On Tuesday 23 October 2012 08:46:21 Hans Verkuil wrote:
> >> On Tue October 23 2012 03:03:35 Laurent Pinchart wrote:
> >>> On Monday 22 October 2012 14:06:06 Hans Verkuil wrote:
> >>>> On Mon October 22 2012 13:18:46 Laurent Pinchart wrote:
> >>>>> On Monday 22 October 2012 12:53:02 Sylwester Nawrocki wrote:
> >>>>>> On 10/22/2012 12:39 PM, Laurent Pinchart wrote:
> >>>>>>> On Monday 22 October 2012 10:35:56 Hans Verkuil wrote:
> >>>>>>>> Hi all,
> >>>>>>>> 
> >>>>>>>> This is the tentative agenda for the media workshop on November
> >>>>>>>> 8, 2012. If you have additional things that you want to discuss,
> >>>>>>>> or something is wrong or incomplete in this list, please let me
> >>>>>>>> know so I can update the list.
> >>>>>>> 
> >>>>>>> Thank you Hans for taking care of the agenda.
> >>>>>>> 
> >>>>>>>> - Explain current merging process (Mauro)
> >>>>>>>> - Open floor for discussions on how to improve it (Mauro)
> >>>>>>>> - Write down minimum requirements for new V4L2 (and DVB?)
> >>>>>>>> 
> >>>>>>>>   drivers, both for staging and mainline acceptance: which
> >>>>>>>>   frameworks to use, v4l2-compliance, etc. (Hans Verkuil)
> >>>>>>>> 
> >>>>>>>> - V4L2 ambiguities (Hans Verkuil)
> >>>>>>>> - TSMux device (a mux rather than a demux): Alain Volmat
> >>>>>>>> - dmabuf status, esp. with regards to being able to test
> >>>>>>>> 
> >>>>>>>>   (Mauro/Samsung)
> >>>>>>>> 
> >>>>>>>> - Device tree support (Guennadi, not known yet whether this topic
> >>>>>>>> 
> >>>>>>>>   is needed) - Creating/selecting contexts for hardware that
> >>>>>>>>   supports this (Samsung, only if time is available)
> >>>>>>> 
> >>>>>>> This last topic will likely require lots of brainstorming, and
> >>>>>>> thus time. If the schedule permits, would anyone be interested in
> >>>>>>> meeting earlier during the week already ?
> >>>>>> 
> >>>>>> My intention was to also possibly discuss it with others before the
> >>>>>> actual media workshop. Would be nice if we could have arranged such
> >>>>>> a meeting. I'm not sure about the room conditions though. It's
> >>>>>> probably not a big issue, unless there is really many people
> >>>>>> interested in that topic.
> >>>>> 
> >>>>> A small room with a projector would be nice if possible, although not
> >>>>> required. Who would be interested in attending a brainstorming session
> >>>>> on contexts ?
> >>>> 
> >>>> I would be, but the problem is that the conference is also interesting.
> >>> 
> >>> More interesting than a brainstorming session about hardware contexts ?
> >>> ;-) There's of course talks I want to attend, but I can probably skip
> >>> some of them.
> >>> 
> >>>> The only day I have really available is the Friday *after* the summit.
> >>> 
> >>> We'll probably need several brainstorming sessions anyway. I'd like to
> >>> organize one before the media summit though, as we'll have limited time
> >>> to discuss the topic during the summit, which doesn't suit brainstorming
> >>> sessions very well.
> >> 
> >> Sylwester, would Samsung be able to prepare for a brainstorming session
> >> on Monday or Tuesday? Both Laurent and myself have presentations on
> >> Wednesday, so that's not the best day for such a session.
> 
> Kamil has presentation on Tuesday so there would be only Monday left.
> 
> >> Do you think we should do a half-day or a full day session on this?
> > 
> > Half a day should be more than enough to start with. The topic is quite
> > complex, and we'll need to sleep over it, several times. A full day would
> > just result in brain overheat. I was thinking more in the line of
> > starting our thought process, so maybe twice an hour or two hours would
> > be good. That would allow us to attend the ELCE talks as well :-)
> > (there's definitely a couple of them that I would like to listen to).
> 
> I agree, I wouldn't like to loose whole day of the conference for that
> as well. One, two hours for the starters could be sufficient. So we can
> possibly agree on some initial idea and could get back to it later.
> I don't think I have already material for a full day session.

One hour, possibly twice, would have my preference. That shouldn't be too 
difficult to organize. When will you and Kamil arrive ?

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2012-10-24 22:41 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  8:35 Tentative Agenda for the November workshop Hans Verkuil
2012-10-22 10:39 ` [media-workshop] " Laurent Pinchart
2012-10-22 10:53   ` Sylwester Nawrocki
2012-10-22 10:57     ` Alain VOLMAT
2012-10-22 11:17       ` Sylwester Nawrocki
2012-10-22 11:18     ` Laurent Pinchart
2012-10-22 12:06       ` Hans Verkuil
2012-10-23  1:03         ` Laurent Pinchart
2012-10-23  6:46           ` Hans Verkuil
2012-10-23 10:22             ` Laurent Pinchart
2012-10-23 11:59               ` Sylwester Nawrocki
2012-10-24 22:42                 ` Laurent Pinchart [this message]
2012-10-25  8:43                   ` Sylwester Nawrocki
2012-10-25  8:52                     ` Hans Verkuil
2012-10-22 21:13       ` Guennadi Liakhovetski
2012-10-22 21:14 ` Guennadi Liakhovetski
2012-10-31 13:12   ` Guennadi Liakhovetski
2012-11-01 16:01     ` Hans Verkuil
2012-11-01 16:05       ` Laurent Pinchart
2012-11-01 19:01         ` Sylwester Nawrocki
2012-10-25 17:27 ` Mauro Carvalho Chehab
2012-11-01 15:44   ` Hans Verkuil
2012-11-01 16:12     ` Mauro Carvalho Chehab
2012-11-02 13:13       ` drivers without explicit MAINTAINERS entry - was: " Mauro Carvalho Chehab
2012-11-02 13:47         ` Hans Verkuil
2012-11-02 14:34           ` Mauro Carvalho Chehab
2012-11-02 15:05             ` [media-workshop] drivers without explicit MAINTAINERS entry - was: " Palash Bandyopadhyay
2012-11-12 18:41             ` drivers without explicit MAINTAINERS entry - was: Re: [media-workshop] " Alexey Klimov
2012-11-12 18:54               ` Mauro Carvalho Chehab
2012-11-23 10:31               ` Hans Verkuil
2012-11-25 23:18                 ` Alexey Klimov
2012-11-26 14:15                   ` Hans Verkuil
2012-11-26 14:21                     ` Alexey Klimov
2012-11-03  9:25         ` [PATCH] firedtv: add MAINTAINERS entry Stefan Richter
2012-11-08 14:18         ` drivers without explicit MAINTAINERS entry - was: Re: [media-workshop] Tentative Agenda for the November workshop Laurent Pinchart
2012-11-13  9:53           ` Laurent Pinchart
2012-12-10 22:01             ` martin
2012-12-11  0:11               ` Laurent Pinchart
2012-11-10 20:55         ` Sakari Ailus
2012-11-12 10:37           ` Mauro Carvalho Chehab
2012-11-12 22:14             ` [PATCH 1/1] MAINTAINERS: Update maintainer for smiapp and adp1653 drivers 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=1372729.rmYJ0LutvU@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=media-workshop@linuxtv.org \
    --cc=s.nawrocki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox