Building a New Linux Kernel

hi all I following the TMS320DM6446 DVEVM v1.30 Getting Started Guide (sprue66d.pdf) to Building a New Linux Kernel. But I have two path can to build: 1. /opt/mv_pro_4.0.1/montavista/pro/devkit/lsp/ti-davinci 2. /opt/mv_pro_4.0.1/montavista/pro/devkit/lsp/ti-davinci_evm-arm_v5t_le/linux-2.6.10_mv

Re: Problem with i2c driver in DM6446

Thanks Andrea. It's my fault to describe the problem. I am using LSP1.0 from TI. The address (0x65) is the RTC slave address which i sent and the problem is why the waveform add a 0xf6 data which i haven't sent? According to user guide of TMS320DM644x DMSoC Inter-Integrated Circuit (I2C) Perip

RE: OSD support in DM6467

Hi, It does not have any OSD and attribute window. It has only two Video windows. I don't know which demo you are talking about. Applications like DirectFB only runs on the the FBDEV so they will not run on dm6467. For these kind of applications, you need to write a V4L2 layer, same as the FBDE

Re: How to know if a udev rule be executed?

I'm trying to figure out exactly which version of udev I have with my montavista distro. I try to run 'udevd --version' / 'udev --version' but they just return me to the command prompt with no info at all. I made sure to check that udev was indeed running with 'ps aux | grep udev' and it's ce

Re: EVM 6467 board doesnot bootup

HI Phil, Thanks, I have followed and got it works. Thanks again. Ramesh On Mon, Sep 29, 2008 at 6:07 PM, Phil Quiney <[EMAIL PROTECTED] > wrote: > Hi, > > Normally you want the board to boot up so would do a 'saveenv' after > setting the bootcmd so it is there on next reboot. > > The user is a

CE 2.10.01 - disables DSP interrupts?

Greetings, I'm trying to track down an issue where I'm missing DSP side interrupts for about 112 micro-seconds whenever I invoke a process function on a codec. This may seem small, but it translates into about 56000 cpu cycles, which is enough to miss 5 interrupts at 22 micro-second intervals. I

RE: FYI - TI patch plan

Hi James, >> Hopefully, we can also get a single download, rather than using Git-Tree >> updates. There are a lot of great benefits to using the GIT tree. When you clone a GIT tree you get a complete replica of the tree (as cloning implies). This means you can view the history of updates/patche

RE: OSD support in DM6467

Hi, Thank you. So what can be done for displays, Like we had in DM6446, video window, OSD window and Attribute window. What should be done to run the demo available with EVM kit? Regards, Naveena From: Jadav, Brijesh R [mailto:[EMAIL PROTECTED] Sent: M

RE: OSD support in DM6467

Hi, As far as i know, dm6467 does not support FBDEV driver. It has only video pipelines so it supports only V4L2 drivers. You will find /dev/video0 to /dev/video3 for the V4L2 devices. Thanks, Brijesh Jadav From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of

Re: about LCD?

cat kit wrote: > Hi Caglar, is me again. > Hi, I'm adding mailing list to cc in case somebody else have faced this before. > Can I know how do you assign your cmem memory pool? because I got the > > "CMEMK Error: Failed to find a pool which fits 829440" > "CMEM Error: getPool: Failed to get

about dm355 CDMA

how should i do if i what to transfer encoded videos (dm355 evm captured) in CDMA net and receive the encoded video in pc ? thanks ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/ma

Re : Re: I2C NAK condition prevents device to be registered

GabrieleF, If you are sure about address( suggestion from me :you don't provide the right shifted address, provide 0x42 for write). Then may be it is due to Davinci I2c adapter driver which is not reentrant (if your soc as more than one I2C-CONTROLLER), then make sure that you are writing to

R: I2C NAK condition prevents device to be registered

Brad, the device's I2C addresses are: 0x42 for write access 0x43 for read access The DaVinci driver wants the I2C address 1 bit shifted to the right, so it should be 0x21 for both reads and writes I'm sure the address is quite correct. I need to know how to have I2C_M_IGNORE_NAK flag set d

RE: EVM 6467 board doesnot bootup

Hi, Normally you want the board to boot up so would do a 'saveenv' after setting the bootcmd so it is there on next reboot. The user is allowed to press a key to interrupt the boot - the timeout is 3 seconds by default (bootdelay variable). For your DHCP requests - if you have an NFS root f

RE: I2C NAK condition prevents device to be registered

Your NACK could be due to having the wrong slave address. The 7-bit slave address is shown many different ways. Sometimes it's shown left-aligned so that you can OR the R/W bit into the address. Other times it's right aligned. Also, the driver itself sometimes expects it one way or another!

Re: EVM 6467 board doesnot bootup

Hi Phil, Thanks, Yes, after 'nboot 8070 0 a ; bootm' its getting boot up. Still there is an problem 'Sending DHCP requests .., But I willl solve it. btw, am i need to enter DaVinci EVM # setenv nfshost 10 setenv bootcmd 'nboot 8070 0 a;bootm' to bootup. is there anyoth

RE: EVM 6467 board doesnot bootup

Hi, You did not tell the kernel to boot. All your boot command is doing is copying the kernel from NAND FLASH to RAM. It should be 'nboot 8070 0 a;bootm' Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0

Re: EVM 6467 board doesnot bootup

Hi Viral sachde, Phil. Thanks for your reply. 1) The printenv , was the cut and paste error. Now I tried again, this time, the badmagic error is not, but stull its not getting bootup DM6467 EVM # printenv bootdelay=3 baudrate=115200 ipaddr=192.168.1.201 setenv=bootcmd nboot 8070 0 a serv

RE: OSD support in DM6467

Hi, Can you check the output of /proc/devices, there should be a 'fb' character device (major 29). This corresponds to the /dev/fb/0 device (maj 29, minor 0) on my system (a DM355). This indicates that the kernel has the framebuffer driver built in. If this does not appear then, it has either

RE: EVM 6467 board doesnot bootup

Hi, Actually, on giivng it a second thought, I think the lines setenv nfshost 10.65.103.160 setenv rootpath /home/Ramesh/workdir6467/filesys setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath), nolock mem=120M ..w

RE: OSD support in DM6467

Hi, There is no device like /dev/fb/0 or /dev/fb/0. We tested the demos available with the DM6446 kit, it was working. It was also dealing with frame buffers. Is it sure that there is frame buffer support in DM6467? Has anybody worked with it? We are trying to do OSD on it. Re

RE: OSD support in DM6467

Hi, The davinci boards should have /dev/fb/0 rather than /dev/fb0 - this is true for DM355 & DM6446. I do not have a DM6467 to check against but I would guess it is the same. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambr

RE: EVM 6467 board doesnot bootup

Hi, Your u-boot parameters are truly broken. You have a 'setenv=bootcmd nboot 8070 0 a' which is nonsense. I think that should have been bootcmd=nboot 8070 0 a The reason it does not boot is because you have set 'bootcmd=bootm' As there is nothing in memory you get the bad m

I2C NAK condition prevents device to be registered

Hi, I've written a loadable module to drive a CCDC device (ov7670) on the I2C bus. But when I "insmod" it: [EMAIL PROTECTED]:~# insmod /lib/modules/2.6.25-rc1-davinci1/kernel/drivers/i2c/chips/ov7670.ko <7>i2c-core: driver [ov7670] registered <7>i2c-adapter i2c-1: found normal entry for adapter