Re: mt9v034 driver

Re: mt9v034 driver

[Guennadi Liakhovetski]

Hi Igor

(forwarding to the real media Mailing List)

On Wed, 17 Apr 2013, Igor Kugasyan wrote:

> Dear Mr. Guennadi,
> 
> Please tell me can I use the soc_camera_ (soc_camera.h, soc_camera.c) 
> interface for a mt9v034 driver as a mt9v022 driver or not?

I don't know anything about mt9v034. It might or might not be compatible 
with one of supported cameras. If it isn't, a new driver has to be 
developed.

> I've read your Video4Linux soc-camera subsystem document and not found a mt9v034 among client drivers.
> I have the Leopard Board 368 (LI-TB02) with the WVGA camera

No, you cannot use soc-camera with Leopard Board. Its camera interface 
might be supported by some other driver, but I'm not sure about that.

>           LI-VM34LP but I haven't a mt9v034 driver for my camera
> for the linux-2.6.32 kernel with RidgeRun

Don't think there's anything that can be done with any kernel apart from 
the current -next, i.e. the forthcoming 3.10.

>           2011Q2 SDK for LeopardBoardDM365 and 
> dvsdk_dm365-evm_4_02_00_06. I haven't sufficient experience for 
> comprehension but I learn...

The only possibility I see is to use a current kernel, adapt an existing 
or write a new camera sensor driver for mt9v034 and use it with the 
appropriate SoC camera interface driver.

Thanks
Guennadi

> Please,
>           please, help me to solve this problem.
> 
>         Thanks
>           in advance.
> 
>         
> 
>         Best regards,
> 
>           
> 
>           Sincerely
>               yours
> 
>             Igor Kugasyan
> 
>             CONECS SSRE
> 
>             Lviv 79060
> 
>             Naukova 7
> 
>             Ukraine
> 
>           
> 
>         T +38 032 2952597
> 
>         F +38 032 2954879
> 
>         E dndp@conecs.lviv.ua 		 	   		  

---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

Re: mt9v034 driver

[Laurent Pinchart]

Hi Igor,

On Wednesday 17 April 2013 16:15:59 Guennadi Liakhovetski wrote:
> On Wed, 17 Apr 2013, Igor Kugasyan wrote:
> > Dear Mr. Guennadi,
> > 
> > Please tell me can I use the soc_camera_ (soc_camera.h, soc_camera.c)
> > interface for a mt9v034 driver as a mt9v022 driver or not?
> 
> I don't know anything about mt9v034. It might or might not be compatible
> with one of supported cameras. If it isn't, a new driver has to be
> developed.

I've put someone on that, so we should get mt9v034 support in mainline in the 
not too distant future.

> > I've read your Video4Linux soc-camera subsystem document and not found a
> > mt9v034 among client drivers. I have the Leopard Board 368 (LI-TB02) with
> > the WVGA camera
> 
> No, you cannot use soc-camera with Leopard Board. Its camera interface
> might be supported by some other driver, but I'm not sure about that.
> 
> >           LI-VM34LP but I haven't a mt9v034 driver for my camera
> > 
> > for the linux-2.6.32 kernel with RidgeRun
> 
> Don't think there's anything that can be done with any kernel apart from
> the current -next, i.e. the forthcoming 3.10.
> 
> >           2011Q2 SDK for LeopardBoardDM365 and
> > 
> > dvsdk_dm365-evm_4_02_00_06. I haven't sufficient experience for
> > comprehension but I learn...
> 
> The only possibility I see is to use a current kernel, adapt an existing
> or write a new camera sensor driver for mt9v034 and use it with the
> appropriate SoC camera interface driver.

-- 
Regards,

Laurent Pinchart

Re: mt9v034 driver

[Laurent Pinchart]

Hi Igor,

On Friday 26 April 2013 16:30:49 Igor Kugasyan wrote:
> Dear Sirs,
> 
> I wrote a driver for the mt9v034 as Todd recommended (on basis of working
> mt9p031 and mt9v022), built kernel with this driver,

Note that a driver for the same sensor has already been posted, see 
https://patchwork.linuxtv.org/patch/14907/.

> but faced with the
> problem:
 
> /dev # cat video0
> cat: can't open 'video0': No such device
> 
> ----------------------------------------------------------------------------
> NAND
> Starting NAND Copy...
> Valid magicnum, 0xA1ACED66, found in block 0x00000019.
> 
> 
> U-Boot 2010.12-rc2 (Feb 07 2013 - 18:15:34)
> 
> Cores: ARM 297 MHz
> DDR:   243 MHz
> I2C:   ready
> DRAM:  128 MiB
> NAND:  256 MiB
> MMC:   davinci: 0, davinci: 1
> Net:   Ethernet PHY: GENERIC @ 0x00
> DaVinci-EMAC
> Hit any key to stop autoboot:  0 
> 
> Loading from nand0, offset 0x400000
>    Image Name:   "RR Linux Kernel"
>    Created:      2013-04-26  11:03:27 UTC
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4247104 Bytes = 4.1 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
> Automatic boot of image at addr 0x82000000 ...
> ## Booting kernel from Legacy Image at 82000000 ...
>    Image Name:   "RR Linux Kernel"
>    Created:      2013-04-26  11:03:27 UTC
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    4247104 Bytes = 4.1 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> Linux version 2.6.32.17-davinci1 (root@ubuntu) (gcc version 4.3.3 (Sourcery
> G++ Lite 2009q1-203) ) #129 PREEMPT Fri Apr 26 14:02:08 EEST 2013

Not only is 2.6.32 from ancient times, I suppose it's the kernel provided with 
the TI BSP. I don't think you will get any support for that here, you should 
contact your TI support channel. We can only provide support for the mainline 
kernel.

-- 
Regards,

Laurent Pinchart