> Unfortunately it requires the same number of fixed and floating point ops to > convert this format to a proper YUV as RGB because its color wheel is rotated > and the UV information is packed in an unusual manner (I'm very thankful > somebody else managed to reverse engineer the colorspace encoding). Can you describe the format in more detail ? > > For the moment add a private ioctl, but this is also relevant to fixing the > > API > > Will do... but let me know where the new API work is being done so I can get > the camera supported on it and make sure that things like non-square pixels > and application-configurable shutter speeds are addressed as video > capabilities. I think everyone who matters reads this list ?