Hi, On 21 August 2013 14:29, Laurent Pinchart wrote: > On Wednesday 21 August 2013 16:17:37 Sakari Ailus wrote: >> On Wed, Aug 07, 2013 at 05:43:56PM +0000, Thomas Vajzovic wrote: >>> It defines the exact size of the physical frame. The JPEG data is >>> padded to this size. The size of the JPEG before it was padded is >>> also written into the last word of the physical frame. That would require either using a custom pixel format and have userspace reading the size from the buffer, or mapping the buffer in kernel space and reading the size there. The latter is easier for userspace, but might it hinder performances ? I think it ought to be a custom format and handled in userspace, otherwise the bridge driver would have to call a subdev function each frame to get it to fix-up the used size each time, which is quite ugly. Regards, Tom -- Mr T. Vajzovic Software Engineer Infrared Integrated Systems Ltd Visit us at www.irisys.co.uk Disclaimer: This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the original message and the sent message from your computer. Infrared Integrated Systems Limited Park Circle Tithe Barn Way Swan Valley Northampton NN4 9BG Registration Number: 3186364. -- 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
