RE: DM6446:how to integrate the DSPLINK to GIT kernel

Hi, I done it for the OMAPL137 with the 2.6.32 kernel. You should apply the patch for the the dsplink and use the kbuild method (see the davinci wiki).You need to copy some include files for the montavista distribution in your current kernel. Arnaud Message: 2 Date: Wed, 10 Feb 2010 23:14:14

MPEG4-streaming

Hello I am preparing my enginner diploma. I look for a help to go deeper in the implementation of a IP video door phone. In fact, i am asking about how to implement streaming of MPEG4 using gstreamer and from a camera source on A DaVinci Texas Instruments DM355 Evaluation Module. Thanks I.G

[no subject]

Hello everyone i am using ELDK cross compiler CC enviroment is arm-linux-gnueabi-g++ as shown in the example but the problem is that i am unable to do make it sucessfully. here is the error what i get

HELP:COMPILATION

Hello everyone i am using ELDK cross compiler CC enviroment is arm-linux-gnueabi-g++ as shown in the example but the problem is that i am unable to do make it sucessfully. here is the error what i get

Re: MPEG4-streaming

Idriss Ghodhbane wrote: Hello I am preparing my enginner diploma. I look for a help to go deeper in the implementation of a IP video door phone. In fact, i am asking about how to implement streaming of MPEG4 using gstreamer and from a camera source on A DaVinci Texas Instruments DM355

CMEM Memory Map

Hi, I am using /dev/cmem module to allocate memory for the dsp algorithms. My current cmem map looks like this # insert cmemk, tell it to occupy physical 118MB-128MB (10M). insmod cmemk.ko phys_start=0x8760 phys_end=0x8800 pools=1x360,5x829440,2x1244160,1x40960,2x8192 Yes, this is

RE: MPEG4-streaming

Hi, We have used live555 to stream the MPEG4. Regards, Suresh .S -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com]on Behalf Of Vladimir Pantelic Sent: Monday, February 15, 2010 4:51 PM To:

Re: CMEM Memory Map

Sameer Naik wrote: One way to achieve this is my simply increasing the cmem memory, so that the module load line, for example, would look like this: 1. # insert cmemk, tell it to occupy physical 109MB-128MB (19M). insmod cmemk.ko phys_start=0x86D0 phys_end=0x8800

Re: CMEM Memory Map

Sameer Naik spiffera, alle Monday 15 February 2010 circa: At least currently i am not allocating buffers other than of size 829440, using CMEM, but at the same time i am not sure whether any of the dsp algorithms allocated memory using CMEM (by guess would be no). I would want this to be

Admin attention: Duplicate emails.

Hi, For the past few weeks I'm getting copies of every email from the community. I'm not sure how to fix this duplication. I went through the subscription page and could not think of any reason. Can someone please suggest me, how to fix this? Kindly bear with such emails - however I cant

Re: HELP:COMPILATION

Hi Rohan, On 15 February 2010 12:18, rohan tabish rohan_ja...@yahoo.co.uk wrote: [snip] /root/ELDK/usr/bin/../lib/gcc/arm-linux-gnueabi/4.2.2/../../../../arm-linux-gnueabi/bin/ld: macaw.o: Relocations in generic ELF (EM: 3) macaw.o: could not read symbols: File in wrong format collect2: ld

issue davincifb_set_attr_blend call in davincifb.c

Hi, I have found that while setting the transparency attributes on OSD1 window the following is done: /* since bits_per_pixel = 4, this will truncate the width if it is * not even. Similarly r-dx will be rounded down to an even pixel. * ... Do we want to return an error

Re: CMEM Memory Map

thats right! On Mon, Feb 15, 2010 at 6:09 PM, Andrea Gasparini gaspar...@imavis.com wrote: Sameer Naik spiffera, alle Monday 15 February 2010 circa: At least currently i am not allocating buffers other than of size 829440, using CMEM, but at the same time i am not sure whether any of the dsp

Re: DM3xx: UART transmit delays

On 11/02/10 09:58, Brian Murphy wrote: Hi Folks, We have been working with L137 and there is an issue where the serial driver handles the UART in a very bad way. This may be the same issue as described in the other two mails on this thread. The issue is that the serial driver 8250.c

RE: CMEM Memory Map

Greetings, As far as I knew, any XDAIS or XDM spec'd algorithms cannot allocate their own CMEM buffers. CMEM allocations are always under application control and thus you can dictate where the shared memory is allocated. In fact, you could not use CMEM at all and just have a section of memory

RE: CMEM Memory Map

Just a quick [hopefully not confusing] clarifying point... All this discussion is correct assuming all the codecs are 'remote'; that is, all codecs execute on the DSP. If any codecs are ARM-based (e.g. all the DM355/365 codecs) and managed by Codec Engine, their XDAIS-requested memory will

RE: CMEM Memory Map

-Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com ] On Behalf Of Vladimir Pantelic Sent: Monday, February 15, 2010 4:27 AM To: davinci-linux-open-source@linux.davincidsp.com Cc:

RE: DM3xx: UART transmit delays

Hi Brian, Thanks for sharing the patch. We tested this on 2.6.32 kernel on DM355 device and it worked fine however we are yet to get this working with 2.6.30 kernel. One of the things that we are trying to investigate is why the transmit FIFO empty interrupts are not generated. If you have

Re: any idea on /dev/fb/0-3 drivers

On Mon, Feb 15, 2010 at 10:48 PM, Naresh Kansara nkans...@irvine-sensors.com wrote: Hi Viral, Thank you for your help. I do see an entry in /proc/devices file as 29 fb Also my kernel .config file has following lines #Graphinc support CONFIG_FB=y CONFIG_FB_DAVINCI=y But when I try to

Re: CMEM Memory Map

thanks a lot you guys. your comments are really helpful. Regards ~Sameer On Mon, Feb 15, 2010 at 11:32 PM, Tivy, Robert rt...@ti.com wrote: -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com ]