Hi Guennadi

Thanks for reply.

> AFAICS, all these platforms only use 8 bits, so, none of them is broken. 
> OTOH, I'm not sure any more, what was the motivation behind that removal. 
> Maybe exactly because we didn't have any platforms with 16-bit camera 
> connections and maybe I saw a problem with it, so, I decided to remove 
> them until we get a chance to properly implement and test 16-bits? Do you 
> have such a board?

about 16bit camera, one guy has it, but he is using v3.0 kernel,
so, it is not in trouble at this point.
(it is working)

The motivation was just "misunderstand-able", not super important at this point.
So please keep considering about it.

> > 2) ff51345832628eb641805a01213aeae0bb4a23c1
> > ([media] V4L: mt9t112: remove superfluous soc-camera client operations)
> > 
> >     this patch remoded MT9T112_FLAG_DATAWIDTH_xx flags from mt9t112 driver,
> >     but Ecovec platform still has it.
> > 
> >     arch/sh/boards/mach-ecovec24/
> 
> Perhaps, the reason was more or less the same - no users, untested code.

About this, now, I'm trying to use this camera on new board (but 8bit),
and the platform code was copied from ecovec.
But the camera image was not correct.

So, I checked the platform/ceu/mt9t112, 
and noticed that the driver is using new mbus style,
but platform is still using old style.
And I got confusion.

Now, this code is no users, untested.
So, the reason why image was broken is 50% new board specific issue,
but 50% original code issue.

Best regards
---
Kuninori Morimoto
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to