Re: isif - debugging on dm365

I was adding isif_cfg.y_c_swap variable, but it need a modification inside arch/arm/mach-davinci/dm365.c that I think is not the right direction. I mean, the isif platform data is not board related, but it is cpu related. I'd like to use isif_set_hw_if_params, but I'm not sure that it is really

Onward into 2010. Best wishes from ChinaPCBOne

I'm going to deviate from my typical marketing tip style and speak candidly. It's possible this email won't necessarily apply to you, but still hope you can take a few minutes to understand about our products and services, maybe able to help your business. My company is a professional PCB

can LSP - 02.10.00.14 be use for DM6467

hi guys,   i'm working on DM6467, using mvtools 5.0 and dvsdk 2.00.00.02.   there is some issue for the kernel, from ti website ,the kernel should be lsp-02.00.00.140.  but this verson kernel seems that there is some issue on network communication. so i tried LSP-02.10.00.14, it works on Dm6467,

Re: can LSP - 02.10.00.14 be use for DM6467

On Wed, Apr 7, 2010 at 9:16 AM, zhijin wang shuishou...@yahoo.com.cnwrote: hi guys, i'm working on DM6467, using mvtools 5.0 and dvsdk 2.00.00.02. there is some issue for the kernel, from ti website ,the kernel should be lsp-02.00.00.140. but this verson kernel seems that there is some

[PATCH] Davinci: generalized debug macros

This patch adopts a debug uart selection similar to the OMAP model. During the boot process, the uncompress code determines the physical and virtual base addresses of the board-specific debug uart. These addresses are then passed on to the in-kernel debug macros through a small chunk of memory

Re: isif - debugging on dm365

Raffaele Recalcati a écrit : I was adding isif_cfg.y_c_swap variable, but it need a modification inside arch/arm/mach-davinci/dm365.c that I think is not the right direction. I mean, the isif platform data is not board related, but it is cpu related. sensor or decoder connection to the isif

Re: [PATCH 0/2]-V2 Add touch screen input driver for TPS6507x family of multi-function chips.

Samuel Ortiz sa...@linux.intel.com writes: Hi Todd, hi Kevin, On Mon, Apr 05, 2010 at 05:53:11PM -0600, Todd Fischer wrote: This is the second posting of the TPS6507x touch screen driver. I have incorporated Kevin Hilman's request to split the board specific changes into a separate patch.

Re: [PATCH 0/2]-V2 Add touch screen input driver for TPS6507x family of multi-function chips.

Kevin Hilman khil...@deeprootsystems.com writes: Samuel Ortiz sa...@linux.intel.com writes: Hi Todd, hi Kevin, On Mon, Apr 05, 2010 at 05:53:11PM -0600, Todd Fischer wrote: This is the second posting of the TPS6507x touch screen driver. I have incorporated Kevin Hilman's request to split

DM365 H.264 Encoder size change problem

I am having a problem anytime I change the height and width setting of the H.264 encoder on the DM365. I have tried sending XDM_RESET control message to the encoder to try and reset it before I change to the new size. I have even deleted and recreated the encoder with VIDENC1_delete and

Re: [PATCH v2 09/16] Davinci: tnetv107x SOC specific header

Chemparathy, Cyril cy...@ti.com writes: Hi, Added on-chip peripheral base addresses so tnetv107x SOC header. There should be no need to define the full list of base addresses in one place because the are typically needed only at only one place (near the resource definition).

RE: how Codec_engine call the dsplink

From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of liuyue18301 Sent: Tuesday, April 06, 2010 6:56 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: how

RE: how Codec_engine call the dsplink

Rob's right, the Link details are intentionally hidden under Codec Engine. But it's often useful to know what's going on underneath. There are more details about CE and DSP Link interaction during DSP start/stop in section 2's Opening an Engine and Closing an Engine here:

RE: [PATCH v3 1/1] DA8XX/OMAP-L1XX: FB: Implement double buffering

On Mon, Apr 05, 2010 at 17:35:38, Kevin Hilman wrote: Ambrose, Martin mar...@ti.com writes: This work includes the following: . Implement handler for FBIO_WAITFORVSYNC ioctl. . Allocate the data and palette buffers separately. A consequence of this is that the palette and data

Re: [PATCH v3 1/1] DA8XX/OMAP-L1XX: FB: Implement double buffering

Ambrose, Martin mar...@ti.com writes: On Mon, Apr 05, 2010 at 17:35:38, Kevin Hilman wrote: Ambrose, Martin mar...@ti.com writes: This work includes the following: . Implement handler for FBIO_WAITFORVSYNC ioctl. . Allocate the data and palette buffers separately. A

Re: ARM CCNT Register : Cycle Count Register

Kieran Bingham kieranbing...@gmail.com writes: Is it possible to read / access the cycle count register in userspace? The counters are accessible to userspace only if enabled in the kernel. Here's a patch to do that: http://git.mansr.com/?p=linux-omap;a=commitdiff;h=5170038 -- Måns Rullgård