From mboxrd@z Thu Jan 1 00:00:00 1970 From: vladimir_zapolskiy@mentor.com (Vladimir Zapolskiy) Date: Sun, 19 Mar 2017 17:00:08 +0200 Subject: [PATCH v5 00/39] i.MX Media Driver In-Reply-To: <20170319142240.GA23922@n2100.armlinux.org.uk> References: <1489121599-23206-1-git-send-email-steve_longerbeam@mentor.com> <20170318192258.GL21222@n2100.armlinux.org.uk> <20170318204324.GM21222@n2100.armlinux.org.uk> <4e7f91fa-e1c4-1cbc-2542-2aaf19a35329@mentor.com> <20170319142110.GT21222@n2100.armlinux.org.uk> <20170319142240.GA23922@n2100.armlinux.org.uk> Message-ID: <51e2be34-6fa2-9d91-5111-adcd697b3e3f@mentor.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 03/19/2017 04:22 PM, Russell King - ARM Linux wrote: > On Sun, Mar 19, 2017 at 02:21:10PM +0000, Russell King - ARM Linux wrote: >> There's a good reason why I dumped a full debug log using GST_DEBUG=*:9, >> analysed it for the cause of the failure, and tried several different >> pipelines, including the standard bayer2rgb plugin. >> >> Please don't blame this on random stuff after analysis of the logs _and_ >> reading the appropriate plugin code has shown where the problem is. I >> know gstreamer can be very complex, but it's very possible to analyse >> the cause of problems and pin them down with detailed logs in conjunction >> with the source code. > > Oh, and the proof of correct analysis is that fixing the kernel capture > driver to enumerate the frame sizes and intervals fixes the issue, even > with bayer2rgbneon being used. > > Therefore, there is _no way_ what so ever that it could be caused by that > plugin. > Hey, no blaming of the unknown to me bayer2rgbneon element from my side, I've just asked an innocent question, thanks for reply. I failed to find the source code of the plugin, I was interested to compare its performance and features with mine in-house NEON powered RGGB/BGGR to RGB24 GStreamer conversion element, which is written years ago. My question was offtopic. -- With best wishes, Vladimir