Re: MMC driver

2006-10-18 Thread Lorenzo Lutti
Kevin Hilman ha scritto: I'm starting to believe that my EVM is damaged; there's no way for me to mount a MMC device. I've tried both positions for J5, but nothing happened; I've tried also with the "original" kernel/root fs installed on the EVM's hard disk, but it doesn't work either. Can someo

Re: Re: git kernel audio driver kernel panic

2006-10-18 Thread ycchang . chang
hello, I've pulled the latest source tree today, and got new kernel panic messages as follows [EMAIL PROTECTED]:~# uname -aLinux 192.168.1.200 2.6.18-omap1-g82f5d268-dirty #7 Wed Oct 18 14:12:59 CST 2006 armv5tejl GNU/Linux [EMAIL PROTECTED]:/opt# ./mplayer /mnt/opt/dvevm/data/sounds/davincieffect.

Re: MMC driver

2006-10-18 Thread Kevin Hilman
Lorenzo Lutti wrote: > Lorenzo Lutti ha scritto: > >> I'm trying to make the MMC driver work. Now I can compile it, but when >> I try to load it, it doesn't work. After these successful commands: >> >> modprobe mmc-block >> modprobe davinci_mmc >> mknod /dev/mmc0 b 254 0 >> >> There's no way to ac

"VID0 Window is disabled due to silicon bug"

2006-10-18 Thread Paul Bartholomew
Hello - The "DaVinci_LSP_Release_Notes.pdf" document that came with the DVEVM (1.10) says (on page 12 of 16): "VID0 Window is disabled due to silicon bug". What exactly does this mean? >From what I can tell, the driver code in "davincifb.c" *does* enable "VID0". As a matter of fact, it looks li

Re: MMC driver

2006-10-18 Thread Lorenzo Lutti
Lorenzo Lutti ha scritto: I'm trying to make the MMC driver work. Now I can compile it, but when I try to load it, it doesn't work. After these successful commands: modprobe mmc-block modprobe davinci_mmc mknod /dev/mmc0 b 254 0 There's no way to access or mount /dev/mmc0. Probably I'm missin

RE: DSP Stack Memory Map

2006-10-18 Thread Jerry Johns
Title: RE: DSP Stack Memory Map So, in a nutshell, there is no way I can do what I’m intending to do (shrink memory map to <=128M) without buying the DVSDK? Is there a way around this? I don’t need to peer into the source code – I just want to change the allocated memory, and I don’t thin

RE: DSP Stack Memory Map

2006-10-18 Thread Ring, Chris
Title: RE: DSP Stack Memory Map The copy codec packages (e.g. codecs.videnc_copy) include libraries - and even sources(!), and are there as examples for the Codec Engine product.  Provided you have all the DSP-side requirements (provided with the DVSDK) like DSP-side compilers, DSP/BIOS, Fram

RE: DSP Stack Memory Map

2006-10-18 Thread Jerry Johns
Title: RE: DSP Stack Memory Map But then how do they expect us to compile the video_copy server, and the associated codecs (videnc_copy, viddec_copy) with it? How are these different from the encode,decode demos H264 codecs in terms of compilability? -Original Message- From: DDV [mai

DSP Stack Memory Map

2006-10-18 Thread DDV
Hello, >The encode server is just made of the two h264 codecs that are already given >to us as packages in the codecs directory - so I was thinking I can change >the cfg files in the video_copy to make this possible You can't do it with DVEVM only. DVEVM packages have not any codecs. It have pack

DSP Stack Memory Map

2006-10-18 Thread Jerry Johns
Hello, I’ve just recently ramped up to 1.10 DVEVM, and am getting started working on some H264 stuff – at the moment, I’m using the encode demo files as my base of operation (allows for H264 encoding on dsp side, and spits out data to arm shared buffers); however, I want to change

Re: git kernel audio driver kernel panic

2006-10-18 Thread Kevin Hilman
[EMAIL PROTECTED] wrote: > > I've tried to use the OSS driver in 2.4.18-git. After I open mplayer > with aac sound and I got the > following kernel panic messages Please try with latest git tree (as of yesterday.) I recently updated fixed some issues in the i2c driver which were causing this pan

Problem writing to SPI registers

2006-10-18 Thread Carlos Ojea
I am seeing a weird behaviour when I write to SPI registers. They seem to hold their value only for a short period of time, and then they go to 0x00. With this code: #define SPIGCR0 0x01C66800 *(int *__iomem) IO_ADDRESS(SPIGCR0) |= 0x0001; printk ("SPIGCR0 %X\n", *(int *__

RE: How to access DVEVM mini-pci

2006-10-18 Thread Griffis, Brad
Short Answer: No, the mini PCI isn't functional. More Complete Answer: Note that the DM6446 does not have a PCI peripheral. The mini PCI slot on the DVEVM board is only mini PCI *form factor*. Some of the VLYNQ pins are actually pinned out here. If I recall correctly they are pinned out to what

Re[3]: Kernel from a latest git sources is not started

2006-10-18 Thread DDV
Hello, ycchang. You wrote Wednesday, October 18, 2006, 01:17:49: > After I upgrade the uboot from 1.1.3 to 1.1.3_0.5.4 the kernel > from git boots fine now I have do it too. Now a git kernel boot but it can't start Davinci USB as module. When i try to build-in Davinci USB driver into kernel the