Hiremath, Vaibhav wrote: >> -----Original Message----- >> From: Pawel Osciak [mailto:p.osciak@xxxxxxxxxxx] >> Sent: Monday, December 28, 2009 8:19 PM >> To: 'Hans Verkuil' >> Cc: linux-media@xxxxxxxxxxxxxxx; linux-samsung-soc@xxxxxxxxxxxxxxx; >> linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; Marek Szyprowski; >> kyungmin.park@xxxxxxxxxxx; Hiremath, Vaibhav; Karicheri, >> Muralidharan; 'Guru Raj'; 'Xiaolin Zhang'; 'Magnus Damm'; 'Sakari >> Ailus' >> Subject: RE: [PATCH/RFC v2.1 0/2] Mem-to-mem device framework >> >> Hello Hans, >> >> >> On Wednesday 23 December 2009 16:06:18 Hans Verkuil wrote: >>> Thank you for working on this! It's much appreciated. Now I've >> noticed that >>> patches regarding memory-to-memory and memory pool tend to get >> very few comments. >>> I suspect that the main reason is that these are SoC-specific >> features that do >>> not occur in consumer-type products. So most v4l developers do not >> have the >>> interest and motivation (and time!) to look into this. >> Thank you very much for your response. We were a bit surprised with >> the lack of >> responses as there seemed to be a good number of people interested >> in this area. >> >> I'm hoping that everybody interested would take a look at the test >> device posted >> along with the patches. It's virtual, no specific hardware required, >> but it >> demonstrates the concepts behind the framework, including >> transactions. >> > [Hiremath, Vaibhav] I was on vacation and resumed today itself, I will go through these patch series this weekend and will get back to you. > > I just had cursory look and I would say it should be really good starting point for us to support mem-to-mem devices.\ Hmm... it seems to me that those patches are still under discussion/analysis. I'll mark them as RFC at the Patchwork. Please let me know after you, SoC guys, go into a consensus about it. Then, please submit me the final version. Cheers, Mauro -- 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
