Re: [PATCH V2] RFC: ARM: DaVinci: ASoc use iram to buffer sound

Troy Kisky wrote: Yusuf Caglar AKYUZ wrote: Troy Kisky wrote: Use the sram(iram) to avoid underrun on audio. I will clean this up after someone says it works for them. Hi, First of all, thanks for looking into this. This patch makes audio usable again for me on 2.6.30 kernel

Re: [PATCH V2] RFC: ARM: DaVinci: ASoc use iram to buffer sound

Steve Chen wrote: On Tue, 2009-06-30 at 18:03 +0300, Yusuf Caglar AKYUZ wrote: Aaah! There were some problem with my player, today I tested with aplay and everything is fine. It would be nice to have this patch included in mainline. Can you provide some details on which player

Re: overrun occuring in arecord for 2.6.30

Mani, Arun wrote: Hi Caglar, Have you tried a loopback of aplay and arecord with this fix? I am still getting overruns with this fix. I tried both following: $arecord -f cd | aplay -f cd $arecord | aplay I receive only one *underrun*, at the time of beginning and then no more. Am I

Re: overrun occuring in arecord for 2.6.30

/msg12570.html Thanks, Arun -Original Message- From: Yusuf Caglar AKYUZ [mailto:caglarak...@gmail.com] Sent: Tuesday, June 30, 2009 1:03 PM To: Mani, Arun Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: overrun occuring in arecord for 2.6.30 Mani, Arun wrote: Hi

Re: [PATCH V2] RFC: ARM: DaVinci: ASoc use iram to buffer sound

Steve Chen wrote: I believe GStreamer uses the OSS emulation layer. It appears that the problem is at sample rate of 44.1k. I disabled CONFIG_SND_SUPPORT_OLD_API and tried with that. Results are the same. Is there a way to disable OSS emulation layer, or should I check gstreamer handling

Re: [PATCH V2] RFC: ARM: DaVinci: ASoc use iram to buffer sound

David Brownell wrote: On Tuesday 30 June 2009, Steve Chen wrote: Can you try aplay -D hw:0,1 r441_c2.wav If you see something like Warning: rate is not accurate (requested = 44100Hz, got = 48000Hz) please, try the plug plugin That means McBSP/AIC33 are not setup to handle

Re: dvsdk 2.0 fails to build.

Andrea Gasparini wrote: Hi, I'm trying to build DVSK 2_00_00_22, and I'm failing in it. More precisely, it's dmai make that blame with the following line: /mnt/lavoro/gigavision/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/../lib/gcc/armv5tl-

Re: dvsdk 2.0 fails to build.

Andrea Gasparini wrote: Andrea Gasparini spiffera, alle Monday 29 June 2009 circa: Anyway, the question remains valid, DO I REALLY NEED to modify almost ten config.bld to have the right path, or is there another, simpler way? ok, I was too hurried in saying so. It seems it's enough to

Re: overrun occuring in arecord for 2.6.30

Mani, Arun wrote: Hi All, Anyone tried arecord in 2.6.30. I am constantly getting a overrun error which is blocking the capture. Thanks, Arun I tried it, and it is not working for me. I see constant overruns as well. This code was working quite well on 2.6.28, I have no idea what

Re: overrun occuring in arecord for 2.6.30

Mani, Arun wrote: Caglar, Thanks very much. Can I get the patch against Arago tree too. That will be of great help. Thanks, Arun. Patch is attached inline. It is against Arago next branch. Regards, Caglar

Re: [PATCH V2] RFC: ARM: DaVinci: ASoc use iram to buffer sound

Troy Kisky wrote: Use the sram(iram) to avoid underrun on audio. I will clean this up after someone says it works for them. Hi, First of all, thanks for looking into this. This patch makes audio usable again for me on 2.6.30 kernel and overruns are gone. What I want to ask is, there is

Re: [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver

Denys Dmytriyenko wrote: On Fri, Jun 26, 2009 at 12:46:31AM +0300, Yusuf Caglar AKYUZ wrote: Karicheri, Muralidharan wrote: We have been using the arago git tree and I don't see any of the issues that you are seeing. Could you use arago tree and Let me know if you see the same issue

Re: [PATCH 0/5] davinci: This patch series ports PWM driver from 2.6.10 tree.

Koen Kooi wrote: On 25-06-09 00:12, caglarak...@gmail.com wrote: From: Yusuf Caglar Akyuzcag...@bilkon-kontrol.com.tr This patch series imports 2.6.10 PWM driver into recent kernel. No functional changes have been made to the driver itself. However, I added a simple sysfs interface for

Re: [PATCH 0/5] davinci: This patch series ports PWM driver from 2.6.10 tree.

David Brownell wrote: On Thursday 25 June 2009, Yusuf Caglar AKYUZ wrote: BTW, I'm not aware of any PWM kernel infrastructure. While porting this driver I looked into to kernel tree but I couldn't find anything related to. linux/pwm.h ... pretty minimal, and ISTR PXA-centric, but it can

Re: [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver

Kevin Hilman wrote: m-kariche...@ti.com writes: From: Muralidharan Karicheri a0868...@gt516km11.gt.design.ti.com Big Thanks to all reviewers who have contributed to this driver by reviewing and offering valuable comments. VPFE Capture driver for DaVinci Media SOCs :- DM355 and DM6446

Re: [PATCH 0/11 - v3] ARM: DaVinci: Video: DM355/DM6446 VPFE Capture driver

Karicheri, Muralidharan wrote: Yusuf, I am not sure what is the state of vpfe branch maintained by Kevin. We have been using the arago git tree and I don't see any of the issues that you are seeing. Could you use arago tree and Let me know if you see the same issue? This tree is being

Re: [PATCH 0/9] This patch series ports VPBE drivers from 2.6.10 tree.

Karicheri, Muralidharan wrote: Caglar, Is this based on LSP 1.20/1.30? Yes. Thanks, Caglar ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com

Re: Status of PWM, Resizer and VPBE Drivers

Karicheri, Muralidharan wrote: Yusuf, When you do you plan to send a patch to this list for review ? I cleaned my patches. I was waiting for latest patches on the list to be applies since some of my patches touches mach-davinci/* as well. I'm going to post in a few minutes. Thanks, Caglar

Re: about cmem module for kernel 2.6.30!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff wrote: All, I am using the newest kernel (2.6.30) on DM355. I need to use cmem module from LSP 1.20 package. When I recompiled cmem module using kernel 2.6.30, It seemed it can not get work. (kernel was dead). I don't why it is. How to

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

Re: vpfe capture driver plans

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karicheri, Muralidharan wrote: Hi All, As you all know that I had submitted initial version of the vpfe capture driver to V4l2 mailing list and got comments against the same. I am currently doing rework of the driver based on the comments.

Re: dvsdk 2.0 oabi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Markus Rechberger wrote: Hi, Hi, I was trying to compile the dvsdk 1.3 and dvsdk 2.0 for eabi 0 but since there are a few binary libraries included it does not work out. Is there any way to get EABI 0 versions of those precompiled dvsdk

Re: dvsdk 2.0 oabi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Markus Rechberger wrote: [...] I got the dvsdk already work with a newer compiler although, my problem is that the target system uses the Ingenient Codecs and was built with OABI/EABI 0 and Linux 2.6.18. In order to be able to use the DVSDK and

Re: dvsdk 2.0 oabi

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Markus Rechberger wrote: [...] I know it's not possible.. that's why I'd need DVSDK OABI binaries .. is there any way to get those? As for the kernel modules I saw the uClib objects for DVSDK 1.3 are in the OABI format, but the other libraries

Re: SRAM allocator(s!)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vladimir Pantelic wrote: David Brownell wrote: If, on a DM355, the ASoC driver can't get SRAM, there's no point in continuing, since the dropout problems basically make audio unusable without it. Even on otherwise idle systems. (The same may

Re: Booting dm355 from SD Card

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Brownell wrote: On Sunday 17 May 2009, Yusuf Caglar AKYUZ wrote: Because I couldn't find any UBL implementation which reads u-boot from SD Card, or at least mentioning of it. I was pretty sure that everything was ok, but I should re-check

Re: Booting dm355 from SD Card

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Venkatachala Upadhya wrote: Hello, Hi, See the below post, in the mailing list. If that helps! http://linux.omap.com/pipermail/davinci-linux-open-source/2009-March/011957.html That was my starting point, but no success here yet. Thanks

Booting dm355 from SD Card

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, I'm trying to boot dm355 from an SD card. Only resource I have found is [1]. Tools mentioned at [1] seems to format and program the SD card correctly and evm is at least not toggling GIO61 but I see nothing on serial console and board

Re: Booting dm355 from SD Card

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Brownell wrote: On Sunday 17 May 2009, Yusuf Caglar AKYUZ wrote: does anyone have pointers to boot dm355 from an SD card without any nand involvement? http://wiki.davincidsp.com/index.php?title=DM355_SD_card_boot_and_flash_utility I

Re: DM355 - No vpss register write happens in the latest kernel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karicheri, Muralidharan wrote: Kevin, I have ported the video driver to the latest davinci git kernel and I have built a single uImage for DM355 and DM6446. The driver works fine on DM6446, but doesn't work on DM355. When I dumped the

Re: Kernel hangs while booting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Muneendra wrote: Hi, No, Kernel itself is not comming up.. It is just uncompressing the kernel and trying to boot as shown below Starting kernel ... Uncompressing

Re: Freeing init memory hang

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Young, Joseph wrote: Hello, Hello, So I am attempting to boot the current Davinci Linux kernel for the Davinci DM644x EVM board, and am running into some problems. I have compiled the uImage, and am using the ramdisk.gz provided by TI, but

Re: U-Boot fw_setenv problem.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 srikanth bomma wrote: Hello all, Hi, [...] CRC write error on /dev/mtd1: Invalid argument Error: can't write fw_env to flash There is a bug in older u-boot fw_env.c file. I changed tools/env/fw_env.c from latest u-boot tree and it worked.

Re: divinci linux 2.6.28+ with DVSDK 1.30

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ondrej Pindroch wrote: Hi Will dvsdk 1.30 work with davinci linux 2.6.28+ instead of MVL 2.6.10 delivered with dvsdk? Or there are some changes needed? Yes, but not out of the box. You need to compile dsplink and cmem for your kernel. Then

Re: GUI development for OMAP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mahalakshmi Gonuguntala wrote: Hi, I have downloaded QT/embedded qt-embedded-linux-eval-src-4.5.0.tar.gz and cross compiled the qt for my arm toolchain.(./configure -embedded arm , make , make install ) and qt installation is sucessful.

Re: moved on to a kernel cmem problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mat Laibowitz wrote: I have been over the memory map a dozen times. I have set my mem parameter in the bootargs to as much as 10 megs lower than the start of my cmem region. I have given DSPLINK more than enough space in the codec servers memory

Re: moved on to a kernel cmem problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mat Laibowitz wrote: In order to debug my mpeg4dec app side program I was looking dmai to see how it accessed the viddec2 ce interface. Along the way I decided to try and compile it and also to try and upgrade some components. I modified the

Re: GUI development for OMAP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mahalakshmi Gonuguntala wrote: Hi All, Hi, We would like to develop a GUI for MISTRAL board (OMAP3530) . The GUI has to have a player kind of look. It should list all the files in the file system and we should be able to select a file from

Re: DSPLINK 1.60 Oops'es on 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Das, Samir wrote: Caglar, Are you seeing this OOPs when you do Ctrl-C? Since you say that mutex is deleted, which means that some thread has done the cleanup (Mutex got deleted). I was trying to come-up with more info on this but I had no

Re: Montavista Linux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcelo Guedes Silva wrote: I´m still with this problem. I follow three documents step-by-step, all of them said similar things, but the final uImage file has some problem. One of this document is the quickstart in:

Re: Davinci, MUSB, DVEVM - driver but no device?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lars Doelle wrote: Unfortunately, the 'alike' board differs here, in that it does not have a GPIO, which might explain the different behavior of the system. On the board at hand, the USB power is hard-wired. I couldn't find David Brownell's

Re: [PATCH 6/7] platform-related-updates for vpfe capture driver on DM6446

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 m-kariche...@ti.com wrote: Add platform related changes for vpfe capture driver on DM6446 [...] + /* * MSP430 supports RTC, card detection, input from IR remote, and * a bit more. It triggers interrupts on GPIO(7) from pressing @@

Re: [DaVinci OpenSource CCB] Re: [PATCH 6/7] platform-related-updates for vpfe capture driver on DM6446

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karicheri, Muralidharan wrote: Caglar, tvp514x is a generic name. I think in the board setup file, we need to use specific chip name that is used in the board which is TVP5146. Remember that tvp514x driver supports 4 types of chips and I think

Re: Question about compiled kernel image

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Whetstone wrote: Hi, Hi, I've compiled the linux kernel from the git repository source with the CodeSourcery toolchain and the result is that there are 2 binary files in the /arch/arm/boot directory (I think that's the correct directory

Re: Davinci, MUSB, DVEVM - driver but no device?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lars Doelle wrote: Hi All, i'm trying to get an USB-stick running on a DVEVM-alike hardware on a recent kernel, but the USB host appears to be plain dead. I've digged a little into the kernel and my result is, that 'platform_driver_probe' in

Re: Montavista Linux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marcelo Guedes Silva wrote: Hi everybody. I created a Montavista Linux Kernel Image. When I tried to run the kernel I received it (in the picture: diamond characters). Could someone explain what is happening? I have no idea and I didn´t receive

Re: Need help to play MONO file(.raw) using AIC34 audio codec

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Chen wrote: On Thu, 2009-03-12 at 18:55 +0530, DHAVAL LAKKAD wrote: Hi, Thank you very much for your reply. I would like to inform you that I am using OSS instead of ALSA. And in OSS, I have found this issue. I'm not familiar with the

Re: Davinci, MUSB, DVEVM - driver but no device?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergei Shtylyov wrote: Hello. Yusuf Caglar AKYUZ wrote: i'm trying to get an USB-stick running on a DVEVM-alike hardware on a recent kernel, but the USB host appears to be plain dead. I've digged a little into the kernel and my result

Re: DSPLINK 1.60 Oops'es on 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yusuf Caglar AKYUZ wrote: Hi, I'm using dsplink 1.60 along with CE 2.21 and sometimes I face kernel oops messages. [1] Then the issuing process locks-up. The error always(up to now) shows-up while process is finishing. I debugged this issue

Re: CE ( or DSPLINK? ) Remote Node Creation Error 0x80008018

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please ignore this message if you haven't already :) I found I had screwed-up ce libraries as you noted while fighting with a dsplink issue. Thanks, Caglar Yusuf Caglar AKYUZ wrote: Ring, Chris wrote: 0x80008018 is RMS_EINVPROT (EINVPROT == Error

DSPLINK 1.60 Oops'es on 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm using dsplink 1.60 along with CE 2.21 and sometimes I face kernel oops messages. [1] Then the issuing process locks-up. The error always(up to now) shows-up while process is finishing. I debugged this issue a little deeper further down and I

CE ( or DSPLINK? ) Remote Node Creation Error 0x80008018

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying DVSDK 2.0 combos with dm6446 but I'm getting error message: ...Engine_createNode Remote node creation FAILED (0x80008018). When I try CE_DEBUG=2, I do not see any other error/warning messages before this line. Both my (own)servers

Re: CE ( or DSPLINK? ) Remote Node Creation Error 0x80008018

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ring, Chris wrote: 0x80008018 is RMS_EINVPROT (EINVPROT == Error, invalid protocol), found in ti/sdo/ce/rms.h. This error occurs if the stubs (ARM-side) and skeletons (DSP-side) don't speak the same protocol. That is, the marshalling protocol

Re: How to stop the u-boot autoboot?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lori Gao wrote: Dear All: When i set the bootdelay parameter to zero, the u-boot will boot OS without delay. But in this situation, i can't stop the u-boot into the command model even pressing ctrl+c. How can i keep no delay to boot OS and

Re: Kernel and FS download through USB to EVM/custom board's NOR flash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Joshi wrote: Hi Swami, Thanks for the quick response. The serial download which I am doing it now for kernel and Ramdisk is taking around 20 min. Method I am following is loadb(via Kermit) followed by cp.b to NOR via HyperTerminal.

Re: Kernel and FS download through USB to EVM/custom board's NOR flash

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Joshi wrote: Hi Caglar, Thanks for the information But in our custom board we have the USB port configured for device mode only with miniAB connector mounted. So I cannot configure as HOST I guessed this. One more limitation is I

Re: Reg: Cross compiled ffplay on dvevm dm6446, problems..crashes..?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ragas sag wrote: Hi All, Hi, For the following messages' [...] Well finally( I hope ) i have some more question. When i ran ./ffplay sample.flv on the board, the video starts playing and after some time get the following kernal dumps,

Re: dm6467 nand filesystem question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 gather bzbz wrote: Hey, all Hi, I am trying to boot kernel and filesystem from the NAND on the 6467 EVM. Please help! 1. The nand partition is 0x-0x0008 : bootloader 0x0008-0x000a : params 0x000a-0x004a :

Re: Reg: Cross compiled ffplay on dvevm dm6446, problems..crashes..?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ragas sag wrote: Hi, Looks like it not a problem with ffmpeg, as these are the message's that i am getting when we play an flv file using ffplay binary on DM6336. Following are the error messages that i am getting. Looks like its got something

Re: Reg: Cross compiled ffplay on dvevm dm6446, problems..crashes..?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ragas sag wrote: On 2/13/09, Yusuf Caglar AKYUZ caglarak...@gmail.com wrote: [...] 1) Do i need to change setting in SDL library w.r.t to fb device? 2) If anybody has faced similar problem, kindly guide us in solving the problem. I guess

Re: Reg: Cross compiled ffplay on dvevm dm6446, problems..crashes..?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ragas sag wrote: On 2/13/09, Yusuf Caglar AKYUZ caglarak...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ragas sag wrote: On 2/13/09, Yusuf Caglar AKYUZ caglarak...@gmail.com wrote: [...] 1) Do i need to change setting

Re: i need your help for VPFE driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm adding mailing list to CC so people can correct me if I'm wrong. huan...@temobi.com wrote: I want to make tvp5146 capture interface work in 2.6.28-rc6 download from montavista git . There were some build errors related it 1. tvp5146 driver

Re: u boot and framebuffer interface

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Deepak Mundra wrote: On Wed, Feb 4, 2009 at 11:01 AM, Nitin Mahajan nitin...@yahoo.com wrote: HI! ___ From: Deepak Mundra deepa...@allaboutif.com To: davinci-linux-open-source@linux.davincidsp.com

Re: dm6446evm NAND Support Broken In 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Brownell wrote: On Monday 02 February 2009, Yusuf Caglar AKYUZ wrote: Is it possible to use CF? I haven't seen any references to it. I'm desperately searching for info on using CF. Let me ask while I found the specialist. I was told

dm6446evm NAND Support Broken In 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I was able to use NAND flash of dm6446 evm with 2.6.27, but I can't use it in 2.6.28 anymore. Checking davinci_probe in davinci_nand.c reveals that driver is looking for two nand resources whereas evm has only one. I guess this change was

Re: dm6446evm NAND Support Broken In 2.6.28

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Brownell wrote: On Monday 02 February 2009, Yusuf Caglar AKYUZ wrote: I was able to use NAND flash of dm6446 evm with 2.6.27, but I can't use it in 2.6.28 anymore. Checking davinci_probe in davinci_nand.c reveals that driver is looking

Re: 2.6.28 and VPFE Drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karicheri, Muralidharan wrote: Caglar, I am a bit confused here. I guess I already send you a patch(and Kevin also) to make it working with 2.6.28! I'm using your capture drivers at the moment with my 2.6.28 tree. I had a version sent to

Re: DM6446 MUSB

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subbrathnam, Swaminathan wrote: Brian, Could you provide more details to the failure ? There are sometimes reset errors with the PIO mode also. Caglar Regards swami -Original Message- From:

Re: CMEM/DSPLink and 2.6.28 kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ryan Talbot wrote: I searched the list, but couldn't find any evidence of patches to get CMEM or DSPLink working with davinci-git kernels 2.6.26. We're currently using 2.6.28-rc6-davinci1, CMEM from TI's LinuxUtils 2.21 package, and DSPLink 1.60.

Re: 2.6.28 and VPFE Drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Poulsen wrote: Caglar, The state of those two files is such that they are not ready to be used. V4L2 has changed enough that you will need to dig in and understand the drivers enough to make the changes. For example, the videobuf code

Re: 2.6.28 and VPFE Drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karicheri, Muralidharan wrote: Steve Caglar, We are already working to port the latest video drivers (capture first and then display) on DM6446 to open source kernel. I had a version of capture driver that is working with 2.6.26 kernel and I

Re: DM355.....

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arvind wrote: Hi, I am using DM355 board I want to use DM355 serial port0 serial port1. How can i use this.. my Code: #include fcntl.h #include stdio.h #include stdlib.h #include sys/types.h #include unistd.h int main(void){

Re: [PATCH 1/5] add vpfe capture driver support

Kevin Hilman wrote: m-kariche...@ti.com writes: This patch adds vpfe capture driver support. This is a new driver based on v4l2-int-device.h interface for attaching slave decoder device to v4l2 master device. This replaces the old davinci_vpfe.c and davinci_vpfe.h. Files have been renamed

Re: emdebian and Ubuntu?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrea Gasparini wrote: Ben West spiffera, alle Wednesday 21 January 2009 circa: However, the decision by Ubuntu maintainers above now means I must set up parallel Debian system. Has anyone else encountered this problem with Ubuntu and emdebian?

2.6.28 and VPFE Drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to make tvp5146 capture interface work in 2.6.28 with DVEVM. There were some build errors related with davinci_vpfe.c, I fixed them. Current situation is that a simple application can open video device, query capabilities and perform

Re: Resizer Initialization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Ressler wrote: Hello, I'd like to use the resizer in my application and quick boot time is also very important to me. In order to reduce boot time, I am bypassing the init scripts with init=/bin/bash in the bootargs. When I bypass

Re: Resizer Initialization

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Ressler wrote: Hi, Are you sure that resizer takes major number 254? I guess it uses dynamic number allocation. I believe you are correct, it uses dynamic number allocation. 254 was the number I saw it using when the device file was

Re: omap-L1xxx

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sergei Shtylyov wrote: Hello. Hello, Besides, how are you using DaVinci? Asking because OMAP-L1xx/ and DA8xx both seem to be targeted to the different market niches than DaVinci -- at least the former completely lack the video support that

Re: emdebian and Ubuntu?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Balister wrote: Yusuf Caglar AKYUZ wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Recently openembedded folks published an online image builder at [1] for various targets including davinci-dvevm. In case you're interested

Re: omap-L1xxx

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kevin Hilman wrote: Sergei Shtylyov sshtyl...@ru.mvista.com writes: Absolutely. Here's an example of enforcing your private opinion... Yes, this is my private opinion, but I am not enforcing anything. I am attempting to share the

Testing TI Production Codecs(MPEG4 Decoder) for dm6446

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying TI productions codecs for dm6446. The codec in question is mpeg4 sp decoder.(document no spruea3a.pdf) I'm able to decode video source some time i.e. ~1 min. But then VIDDEC_process fails with error code 0x408 or 0x401. If I continue

Re: GStreamer, fbvidesink and GIT Kernel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Venkatachala Upadhya wrote: HI, This should be /dev/fb/3 for fbvieo sink instead of /dev/fb0 fbvideosink device=/dev/fb0 Do you mean fbvideosink doesn't work with fb0? Because I tried fb3 also. The example was to demonstrate that fbdevsink

GStreamer, fbvidesink and GIT Kernel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, My problem is very specific to gstreamer ti plugins' code. I hope someone is still maintaining those codes and following this list. I'm trying to get started with gstreamer on git kernel 2.6.27-rc6. I'm trying to get ti-plugins working with

Re: GStreamer, fbvidesink and GIT Kernel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yusuf Caglar AKYUZ wrote: Hi all, My problem is very specific to gstreamer ti plugins' code. I hope someone is still maintaining those codes and following this list. I'm trying to get started with gstreamer on git kernel 2.6.27-rc6. I'm

Re: starting DSP server './decodeCombo.x64P' FAILED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Mahajan wrote: HI! I have some queries related to the DSP server, when it is present in NAND flash file system YAFFS2. Hi, What is the source of YAFFS2 image and which kernel version are you using? Caglar -BEGIN PGP SIGNATURE-

Re: starting DSP server './decodeCombo.x64P' FAILED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Mahajan wrote: HI! - Original Message From: Yusuf Caglar AKYUZ caglarak...@gmail.com To: Nitin Mahajan nitin...@yahoo.com Cc: davinci-linux-open-source@linux.davincidsp.com Sent: Tuesday, January 6, 2009 18:49:26 Subject

Re: starting DSP server './decodeCombo.x64P' FAILED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Mahajan wrote: I am using the dsplink version 1.50, I created the basic rootfs from ramdisk image and copied the DSP related binaries to this rootfs. Everyting works fine untill I am on NFS or ext2. Once the same rootfs is brought to

Re: starting DSP server './decodeCombo.x64P' FAILED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jérôme HUET wrote: Hello, I have the same problem when I want to use dsplink 1.40 with the latest kernel from the git repository. How did you manage to avoid this error? Did you follow the remarks at post [1] and related mails? Other than

Re: starting DSP server './decodeCombo.x64P' FAILED

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nitin Mahajan wrote: Thanks, I googled out this post in the mean time and went thru it. I have one question in general, whether all your DSP related software works well with the recent git kernel maintained by Montavista? I tested dsplink,

Re: Strange problem with Linux git version. lcd crashes ttyS0 console!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 BlackSword wrote: Hi all, I need you help! I meet such a problem. My system works perfect with original LSP1_20 for lcd. And with the git version it works perfect for component signal. But when i tried bootargs video=davincifb:output=lcd. problem

Re: Filesystem for NOR on 6446

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 jp wrote: Hi, Hi, I guess you're starting a new thread by replying to another thread. If this is the case, please do not because threads are mixing-up this way. I still have some problems to create a filesystem to put it on the NOR (16MBytes).

i2c devices present in i2c_board_info are not probed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm trying to use isl-1208 i2c rtc driver present in git kernel. However, I noticed that kernel never probes this driver. I modified my board setup code to include a rtc device dv-evm board setup code like: static struct i2c_board_info

Re: open suse 11.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vijay Soni wrote: On Suse 11.0 linux host platform, when I do /usr/sbin/exportfs -av command, it says file not found. I am in bash shell. Then I tried man exportfs, and it says that command not found. What is wrong? You should run it as root.