Hi Robert, On 8 June 2012 09:26, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx> wrote: > Hi Javier, > > On Fri, Jun 08, 2012 at 09:21:13AM +0200, javier Martin wrote: >> If you refer to driver in [1] I have some concerns: i.MX27 VPU should >> be implemented as a V4L2 mem2mem device since it gets raw pictures >> from memory and outputs encoded frames to memory (some discussion >> about the subject can be fond here [2]), as Exynos driver from Samsung >> does. However, this driver you've mentioned doesn't do that: it just >> creates several mapping regions so that the actual functionality is >> implemented in user space by a library provided by Freescale, which >> regarding i.MX27 it is also GPL. >> >> What we are trying to do is implementing all the functionality in >> kernel space using mem2mem V4L2 framework so that it can be accepted >> in mainline. > > We will work on the VPU driver and it's migration towards a proper > mem2mem device very soon, mainly on MX53, but of course MX27 should be > taken care of by the same driver. > > So I'd suggest that we coordinate that work somehow. Do you plan to provide both encoding and decoding support or just one of them? -- Javier Martin Vista Silicon S.L. CDTUC - FASE C - Oficina S-345 Avda de los Castros s/n 39005- Santander. Cantabria. Spain +34 942 25 32 60 www.vista-silicon.com -- 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
