Hi Hans, On Wednesday 28 September 2011 10:01:03 Hans Verkuil wrote: > On Tuesday, September 27, 2011 18:46:10 Tomasz Stanislawski wrote: > > On 09/27/2011 04:10 PM, Mauro Carvalho Chehab wrote: > > > Em 27-09-2011 10:02, Tomasz Stanislawski escreveu: > > >> On 09/26/2011 02:10 PM, Mauro Carvalho Chehab wrote: > > >>> Em 26-09-2011 05:42, Tomasz Stanislawski escreveu: > > >>>> On 09/24/2011 05:58 AM, Mauro Carvalho Chehab wrote: > > >>>>> Em 22-09-2011 12:13, Marek Szyprowski escreveu: [snip] > > The legacy applications would be supported by simulation of old API > > using selection API. > > As I said before, G/S_CROP is perfectly valid and will not go away or be > deprecated. Just as S_CTRL is not replaced by S_EXT_CTRLS. There is no need > to force apps to move to the selection API. The selection API extends the > old crop API for good reasons, but for simple cropping S_CROP remains > perfectly fine. Now, of course. In a couple years time, the story will likely be different, and we might want to deprecate the G/S_CROP API. Shouldn't this message be conveyed to userspace developers ? I like the idea of asking them to favor the selection API over the crop API for new applications. > What would be nice is to deprecate the old crop ops for new drivers and > (ideally) convert existing drivers that use vidioc_g/s_crop to the new > vidioc_g/s_selection (with the final goal of removing vidioc_g/s_crop). > > And also note that cropcap is still needed to get the pixelaspect. -- Regards, Laurent Pinchart -- 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
