Getting larger resolution than 1080p

Hi I have made some new resolutions for MT9P031 sensor. One is almost full frame 2560x1920. But when I see the image are no relevant data in line after 1908. pixel. Some sort of noise is there. I have made changes in buffer length and all what I expected to change. Do some one have any

RE: Question Regarding DM365

Veeranna, Refer 1.sprufg9.pdf, 2.sprufg8.pdf, 3.sprugg8.pdf(Face Detection User guide, DM36x) 3.spraah0a.pdf 4.spraa96a.pdf Regards, Suresh S -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com

RE: Question Regarding DM365

HI Suresh, Thanks for ur reply, In the doc 'sprugg8.pdf' they are mentioning register level configuration to configure the face detection module, we want know is TI providing upper level APIs for the same(like for DMA, ACPY3 APIs). Thanks, veeru -Original Message- From: sureshs

CMEM and mmap'd buffers in 2.6.28rc6

Hey folks, We've run into a seemingly strange problem when trying to encode live video on our custom DM6446 hardware board using a 2.6.28-rc6-based kernel. We have applied all the patches we're aware of to get VPFE, CMEM, and DSPLink to compile correctly against this kernel. We have verified

Re: CMEM and mmap'd buffers in 2.6.28rc6

Ryan Talbot wrote: CMEM Error: getPhys: Failed to get physical address of 0x4015c000 CMEM Error: getPhys: Failed to get physical address of 0x40226fff Those addresses correspond to the virtual addresses of the first capture buffer, and the second capture buffer -1, respectively. Those were

RE: /dev/video3 - Cannot open- Invalid argument

Hi, I think the problem is no encoder is registered for this node. We have to register an encoder driver for the node, which we are going to use. If it is not available it returns error. Thanks, Brijesh Jadav From:

ARM application build issue

Hi, I get the following errors while building my ARM application Initially I used codec_engine_2_10_00_08 Later I changed to codec_engine_2_10_02. but still the problem persists. Any clues? -

RE: /dev/video3 - Cannot open- Invalid argument

Hi, Thanks. We have been able to register an encoder for /dev/video3. The sys/class/davinci-display/ch1/output/mode are written to and we can read from it. The device /dev/video3 also gets created. However, we are unable to proceed further as far as redirecting the captured video to the

builing CE with latest kernel

Hi, I tried compiling CE 2.23.01 using 2.6.30-rc7 but I failed. Did anyone of you succeded? -- Non c'è più forza nella normalità, c'è solo monotonia. ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com

DM365 EMAC boot mode

Hi All, I am trying to use DM365 EMAC boot mode to boot Linux without flash. From document, it says that DM365 chip supports it. But it is not clear with TI source code (ubl and u-boot) support EMAC boot. I have the ubl and uboot bin files for NAND boot mode on EVM board. Do I need to modify

RE: DM365 EMAC boot mode

Tao, The UBL you are referring to is meant only for the NAND boot mode. You will have to come up with your own application use EMAC boot mode Thanks, Sandeep -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com

RE: DM365 EMAC boot mode

Tao, Please see inline Sandeep -Original Message- From: Tao Wu [mailto:lanlan...@gmail.com] Sent: Tuesday, June 09, 2009 11:52 AM To: Paulraj, Sandeep; davinci-linux-open-source- boun...@linux.davincidsp.com Subject: Re: DM365 EMAC boot mode Thanks for your reply. Does TI

RE: ARM application build issue

You mention you're building an ARM application, but the build looks like it's building a DSP-side server. If you _are_ building an ARM app, it's wrong that the ti.sdo.ce.osal.bios package is coming into the picture at all. You might double check that your ARM-side app's config script is

Re: [PATCH v2 3/3] Adding DM365 entries to Makefile/Kconfig/defconfig

Paulraj, Sandeep s-paul...@ti.com writes: -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Friday, June 05, 2009 5:43 PM To: Paulraj, Sandeep Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: [PATCH v2 3/3] Adding DM365 entries to

[PATCH] MUSB: split out CPPI interrupt handler (take 2)

As DaVinci DM646x has a dedicated CPPI DMA interrupt, replace cppi_completion() (which has always been kind of layering violation) by a complete CPPI interrupt handler. Signed-off-by: Dmitry Krivoschekov dkrivosche...@ru.mvista.com Signed-off-by: Sergei Shtylyov sshtyl...@ru.mvista.com

Re: [PATCH v2 3/3] Adding DM365 entries to Makefile/Kconfig/defconfig

Kevin Hilman khil...@deeprootsystems.com writes: Paulraj, Sandeep s-paul...@ti.com writes: -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] diff --git a/arch/arm/mach-davinci/Kconfig b/arch/arm/mach- davinci/Kconfig index 7640867..90325c7 100644 ---

[PATCH 0/10 - v2] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446 This is the version v2 of the patch series. This is the reworked version of the driver based on comments received against the last version of the patch.

[PATCH 3/10 - v2] dm355 ccdc module for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com DM355 CCDC hw module Adds ccdc hw module for DM355 CCDC. This registers with the bridge driver a set of hw_ops for configuring the CCDC for a specific decoder device connected to vpfe. Following are some of the major comments

[PATCH 4/10 - v2] dm644x ccdc module for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com DM644x CCDC hw module This is the hw module for DM644x CCDC. This registers with the vpfe capture driver and provides a set of hw_ops to configure CCDC for a specific decoder device connected to the VPFE Following are some of the

[PATCH 5/10 - v2] ccdc types used across ccdc modules for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com common types used across CCDC modules No change from last version Reviewed By Hans Verkuil. Reviewed By Laurent Pinchart. Signed-off-by: Muralidharan Karicheri m-kariche...@ti.com --- Applies to v4l-dvb repository

[PATCH 5/10 - v2] ccdc hw device header file for vpfe capture

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com CCDC hw device header file Adds ccdc hw device header for vpfe capture driver Incorporated review comments against previous patch Reviewed By Hans Verkuil. Reviewed By Laurent Pinchart. Signed-off-by: Muralidharan Karicheri

[PATCH 10/10 - v2] common vpss module for video drivers

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com Reviewed By Hans Verkuil. Reviewed By Laurent Pinchart. This is a new module added for vpss library functions that are used configuring vpss system module. All video drivers will include vpss.h header and call functions defined in

[PATCH 6/10 - v2] Makefile and config files for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com Makefile and config files for the driver This adds Makefile and Kconfig changes to build vpfe capture driver. Added configuration variable for vpss driver based on last review Reviewed By Hans Verkuil. Reviewed By Laurent

[PATCH 7/10 - v2] DM355 platform changes for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com DM355 platform and board setup This has platform and board setup changes to support vpfe capture driver for DM355 EVMs. Added registration of vpss platform driver based on last review Reviewed By Hans Verkuil. Reviewed By Laurent

[PATCH 8/10 - v2] DM6446 platform changes for vpfe capture driver

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com DM644x platform and board setup This adds plarform and board setup changes required to support vpfe capture driver on DM644x Added registration of vpss platform driver based on last comment Reviewed By Hans Verkuil. Reviewed By

[PATCH 2/10 - v2] ccdc hw device header file for vpfe capture

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com CCDC hw device header file Adds ccdc hw device header for vpfe capture driver Incorporated review comments against previous patch Reviewed By Hans Verkuil. Reviewed By Laurent Pinchart. Signed-off-by: Muralidharan Karicheri

Re: device driver for 800x480 LCD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 elbert shiang wrote: Hi, Dear All: Hi, I want to make dm355 connect to the TFT-LCD which has RGB666 signal. I have no idea where to start to build the device driver from tool chain. Can anyone guide me which documentation I should

[PATCH v3 2/3] ARM DaVinci Adding DM365 EVM Support

The patch adds support for DM365 EVM Signed-off-by: Sandeep Paulraj s-paul...@ti.com --- arch/arm/mach-davinci/board-dm365-evm.c | 76 +++ 1 files changed, 76 insertions(+), 0 deletions(-) create mode 100644 arch/arm/mach-davinci/board-dm365-evm.c diff --git

[PATCH v3 3/3] Adding DM365 entries to Makefile/Kconfig/defconfig

This patch does the following 1) Adds entries to davinci_all_defconfig for DM365 2) Adds entries to the Makefile for DM365 3) Adds entries for DM365 in the Kconfig Signed-off-by: Sandeep Paulraj s-paul...@ti.com --- arch/arm/configs/davinci_all_defconfig |2 ++ arch/arm/mach-davinci/Kconfig

[PATCH RFC] adding support for setting bus parameters in sub device

From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com re-sending with RFC in the header This patch adds support for setting bus parameters such as bus type (BT.656, BT.1120 etc), width (example 10 bit raw image data bus) and polarities (vsync, hsync, field etc) in sub device. This

Re: [PATCH RFC] adding support for setting bus parameters in sub device

On Tuesday 09 June 2009 22:55:53 m-kariche...@ti.com wrote: From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com re-sending with RFC in the header This patch adds support for setting bus parameters such as bus type (BT.656, BT.1120 etc), width (example 10 bit raw image data bus)

Re: [PATCH RFC] adding support for setting bus parameters in sub device

On Tuesday 09 June 2009 23:03:01 Hans Verkuil wrote: On Tuesday 09 June 2009 22:55:53 m-kariche...@ti.com wrote: From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com re-sending with RFC in the header This patch adds support for setting bus parameters such as bus type

[PATCH v1] Adding DaVinci DM365 EDMA Support

The patch adds support for EDMA in DM365 The EDMA user guide for DM365 can be found at http://focus.ti.com/lit/ug/sprufi0/sprufi0.pdf Signed-off-by: Sandeep Paulraj s-paul...@ti.com --- arch/arm/mach-davinci/dm365.c | 91 + 1 files changed, 91

RE: [PATCH RFC] adding support for setting bus parameters in sub device

email: m-kariche...@ti.com -Original Message- From: Hans Verkuil [mailto:hverk...@xs4all.nl] Sent: Tuesday, June 09, 2009 5:03 PM To: Karicheri, Muralidharan Cc: linux-me...@vger.kernel.org; davinci-linux-open- sou...@linux.davincidsp.com; Muralidharan Karicheri Subject: Re: [PATCH RFC]

RE: CMEM and mmap'd buffers in 2.6.28rc6

-Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com ] On Behalf Of Ryan Talbot Sent: Tuesday, June 09, 2009 2:29 PM To: Vladimir Pantelic; davinci-linux-open-source@linux.davincidsp.com Cc:

[PATCH] Minor Update to Kconfig

Patch updates the Kconfig for the various DaVinci EVMs This is being done based on a comment received when DM365 patches were reviewed. Each EVM defaults to be enabled whenever the SOC is enabled Signed-off-by: Sandeep Paulraj s-paul...@ti.com --- arch/arm/mach-davinci/Kconfig | 10 +-

[PATCH v1] DM365 NAND Support

This patch adds NAND support for the DM365. The EMIF controller on the DM365 is the same as the DM355. Signed-off-by: Sandeep Paulraj s-paul...@ti.com --- arch/arm/mach-davinci/board-dm365-evm.c | 84 +++ 1 files changed, 84 insertions(+), 0 deletions(-) diff --git

Re: ARM application build issue

Hi Chris, Thank you for the suggestion. My application is ARM side only, but as you mentioned the app.cfg file was wrongly configured as osalGlobal.runtimeEnv = osalGlobal.DSPLINK_BIOS; So I changed it to osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX; But now the

RE: ARM application build issue

Can you check if XDCPLATFORM is rightly defined in your app's makefile? Regards, Prem Texas Instruments India -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Jaya krishnan Sent: