On Sat July 21 2012 14:16:22 Sylwester Nawrocki wrote: > Hi Hans, > > On 07/17/2012 09:32 PM, Hans Verkuil wrote: > > On Tue July 17 2012 19:30:53 Mauro Carvalho Chehab wrote: > >> As we did in 2012, we're planning to do a media summit again at KS/2012. > >> > >> The KS/2012 will happen in San Diego, CA, US, between Aug 26-28, just > >> before the LinuxCon North America. > >> > >> In order to do it, I'd like to know who is interested on participate, > >> and to get proposals about what subjects will be discussed there, > >> in order to start planning the agenda. > > > > I'd like to have 30 minutes to discuss a few V4L2 API ambiguities or just > > plain weirdness, just like I did last year. I'll make an RFC issues to discuss > > beforehand. I might also have a short presentation/demo of v4l2-compliance, as > > I believe more people need to know about that utility. > > What do you think about adding new M2M capability flag for memory-to-memory > video devices ? I prepared an RFC patch for that already: > http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg48497.html > > I think that at least qualifies to your list of V4L2 API ambiguities, even > though we have device_caps now. Using ORed OUTPUT and CAPTURE flags implies > all existing applications must check now both flags when they're trying to > discover a video capture or video output device. I agree. I've added to my list (which is getting pretty long BTW, I will probably need more than 30 minutes). When adding support for M2M devices to v4l2-compliance I also noticed that using CAPTURE+OUTPUT is a rather awkward way to signal this capability, so I agree to adding a special cap bit for that. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
