On Friday 26 June 2009 16:43:52 Aguirre Rodriguez, Sergio Alberto wrote:
But in user space there is nothing changed having access to
device and control them.
As you know, subdev and int-device is all about how to bind
interface(or host?) and device and make them communicated each
On Friday 26 June 2009 07:27:15 Dongsoo, Nathaniel Kim wrote:
Hello,
On Fri, Jun 26, 2009 at 7:43 AM, Gary Thomasg...@mlbassoc.com wrote:
Still trying to wrap my head around the OMAP/34xx camera support.
I need to use the TVP5150 sensor/controller, but the existing
driver uses
But in user space there is nothing changed having access to
device and control them.
As you know, subdev and int-device is all about how to bind
interface(or host?) and device and make them communicated each other.
But using subdev device driver with int-device supporting interface
(or
Still trying to wrap my head around the OMAP/34xx camera support.
I need to use the TVP5150 sensor/controller, but the existing
driver uses v4l_subdev. The working examples I've found
(from Sergio's tree) use sensors like ov3640 with uses v4l2_int_device
Are these two totally separate beasts?
If
Hello,
On Fri, Jun 26, 2009 at 7:43 AM, Gary Thomasg...@mlbassoc.com wrote:
Still trying to wrap my head around the OMAP/34xx camera support.
I need to use the TVP5150 sensor/controller, but the existing
driver uses v4l_subdev. The working examples I've found
(from Sergio's tree) use sensors
