RE: How to know if a udev rule be executed?
Hi, For udev ( anything else on the NFS root filesystem), you can use rpm to tell you the package version. It is a 2 step process, first find a binary or other file you want to find the version of. Then query the rpm database to find which package it belongs to. So for your example of udevd the process is [EMAIL PROTECTED]:~# which udevd /sbin/udevd [EMAIL PROTECTED]:~# rpm -qf /sbin/udevd # You can alternatively use rpm -qf `!!` if you like shortcuts udev-0.056-3.0.1.0600975 ..and as Geoff said, it is version 056. Additionally, once you know the package name, you can get information about the package (rpm -qi udev), list all files in the package (rpm -ql udev) and verify the package integrity (rpm -V udev). The above works on any RPM based linux distribution and can be a useful way of finding your way around. Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bj Sent: 29 September 2008 22:59 To: Amey, Geoff Cc: davinci-linux-open-source@linux.davincidsp.com Subject: 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 certainly there. [EMAIL PROTECTED]:~# udev --version [EMAIL PROTECTED]:~# udevd --version [EMAIL PROTECTED]:~# ps aux | grep udev root 822 0.0 0.4 1416 388 ?Ss 00:00 0:00 udevd root 1085 3.0 0.5 1572 456 ?S+ 00:02 0:00 grep udev How did you figure out your version, and then also how did you update it after realizing that your version wasn't up to snuff? The goal I'm trying to reach here is to create a udev rule to mount usb flash drives upon insertion. I saw the previous chatter about this topic and people claim that this issue has been gone over and solved but I'm still having problems with it so please don't direct me to 'just search the list'. Thanks for any tips. BJ Amey, Geoff wrote: Try looking into udevtest, I don't remember the exact sytax, but it applies all of your udev rules to a particular /sys/ entry and prints the result to the console. Another thing to be aware of with udev is the version. The one that came on my DM355 board was version 056, which doesn't support the RUN keyword. I had to upgrade to 057 to use the RUN keyword. (udev is currently somewhere around version 120). After downloading and cross compiling 057 (udev, udevd, udevinfo, udevtest, etc...) I was able to get my RUN rules to work. Hope this helps - Geoff -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Wu Sent: Tuesday, June 03, 2008 12:16 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to know if a udev rule be executed? I write a custom udev rule to auto mount the SD card, but it do not mount the card when I plug in. I want to know if the rule be executed? My rule content is: RUN+=mount /dev/mmcblk0p1 /mnt I write a simplest rule with no condition the rule is named /etc/udev/rules.d/60-local.rules ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
EVMDM6446 and dvsdk_1_30_00_40
Hello Everybody, I am following the sprue66d.pdf for using the DVEVM with DVSDK_1_30_00_40 But it fails saying *** Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Capturing 720x480 video (cropped to 720x480) Total I-frames: 0, P-frames: 0, B-frames: 0, IDR-frames: 0 rejected: 0 *** on further investigation we found that kernel itself was having some issues opening the video port. following is the part of dmesg; *** Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 2500KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 1020KB watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Linux video capture interface: v1.00 Registering platform device 'vpfe.1'. Parent at platform DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded Registering platform device 'DavinciDisplay.1'. Parent at platform Trying to register davinci display video device. layer=c73dfc00,layer-video_dev=c73dfd64 Trying to register davinci display video device. layer=c73dfa00,layer-video_dev=c73dfb64 davinci_init:DaVinci V4L2 Display Driver V1.0 loaded Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 *** following is my bootarg Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=142.102.22.174:/home/ketan/workdir/filesys,nolock mem=116M ip=142.102.22.85:142.102.22.174:142.102.22.39:255.255.254.0:dm6446evm::off dm9000eth=mac:00.0e.99.02.5b.71 video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc Has anybody else observed the same issue? Any idea how to resolve that? regards, -Ketan Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: EVMDM6446 and dvsdk_1_30_00_40
Hi, The problem is the buffer sizes - you are setting the mode to NTSC but are using PAL size buffers. If you change the sizes to 720x480 in the bootargs it should work. With the older kernel this did not cause a problem, however with the 'unified' kernel it matters. At least that is what we have found ;-) Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.com http://www.trinityconvergence.com/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ketan deshpande Sent: 30 September 2008 10:27 To: Linux DaVinci Subject: EVMDM6446 and dvsdk_1_30_00_40 Hello Everybody, I am following the sprue66d.pdf for using the DVEVM with DVSDK_1_30_00_40 But it fails saying *** Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Capturing 720x480 video (cropped to 720x480) Total I-frames: 0, P-frames: 0, B-frames: 0, IDR-frames: 0 rejected: 0 *** on further investigation we found that kernel itself was having some issues opening the video port. following is the part of dmesg; *** Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 2500KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 1020KB watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Linux video capture interface: v1.00 Registering platform device 'vpfe.1'. Parent at platform DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded Registering platform device 'DavinciDisplay.1'. Parent at platform Trying to register davinci display video device. layer=c73dfc00,layer-video_dev=c73dfd64 Trying to register davinci display video device. layer=c73dfa00,layer-video_dev=c73dfb64 davinci_init:DaVinci V4L2 Display Driver V1.0 loaded Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 *** following is my bootarg Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=142.102.22.174:/home/ketan/workdir/filesys,nolock mem=116M ip=142.102.22.85:142.102.22.174:142.102.22.39:255.255.254.0:dm6446evm::off dm9000eth=mac:00.0e.99.02.5b.71 video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc Has anybody else observed the same issue? Any idea how to resolve that? regards, -Ketan Be the first one to try the new Messenger 9 Beta! Click here. http://in.rd.yahoo.com/tagline_messenger_7/*http://in.messenger.yahoo.com/win/ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
What is the easiest way to change the brightness on the TVP5146. Through an ioctl?
What is the easiest way to change the brightness on the TVP5146. Through an ioctl?? Thanks Panchy Rivas ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Problem with u-boot and flash MT29F16G08DAA
Hi all, The default flash that came with the evmdm355 has been discontinued and the replacement from Micron is MT29F16G08DAA. The flash is very similar, I perform all tests and passes and in fact with CCS I can load UBL and u-boot perfectly. But in u-boot if I try to perform saveenv it cannot write to flash and I get the following errors: this is MT29F16G08QAA device UBL: Failed to read app descriptor UBL: NANDBoot() failed It seems like when u-boot is trying to save its enviroment variables it is writing to a bad location, and erases the location of the u-boot magic number and UBL cannot load u-boot again. Does anyone has this problem before? Thanks in advance, A.Silva ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: Problem with u-boot and flash MT29F16G08DAA
The answer is in the e-mail itself. Have a look at the part numbers. MT29F16G08DAA is what it is supposed to be and MT29F16G08QAA is what is getting detected. Thanks, Sandeep From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of António Silva Sent: Tuesday, September 30, 2008 10:23 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: Problem with u-boot and flash MT29F16G08DAA Hi all, The default flash that came with the evmdm355 has been discontinued and the replacement from Micron is MT29F16G08DAA. The flash is very similar, I perform all tests and passes and in fact with CCS I can load UBL and u-boot perfectly. But in u-boot if I try to perform saveenv it cannot write to flash and I get the following errors: this is MT29F16G08QAA device UBL: Failed to read app descriptor UBL: NANDBoot() failed It seems like when u-boot is trying to save its enviroment variables it is writing to a bad location, and erases the location of the u-boot magic number and UBL cannot load u-boot again. Does anyone has this problem before? Thanks in advance, A.Silva ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: FYI - TI patch plan
Yes, that is the ultimate goal for DaVinci patches as well. Sneha -Original Message- From: Philip Balister [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 10:50 AM To: Narnakaje, Snehaprabha Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: FYI - TI patch plan Narnakaje, Snehaprabha wrote: Hi, Texas Instruments plans to improve and/or add support for TI's family of DaVinci SoCs. This work is being done by a number of us here and I am coordinating the efforts. Beginning this month, TI will contribute patches to the DaVinci GIT tree, with the goal to update DM644x and add DM355 and DM6467 support. Another goal is to get all driver features and bug fixes up-ported from earlier TI/MontaVista LSP releases for these devices. We plan to follow the approximate roadmap below: September/October 2008: Patches for DM6467/DM355 baseport, DM9000 Ethernet (DM355), I2C (DM6467/DM355), GPIO (DM6467/DM355), EDMA (DM6467/DM355) and Video Capture (Using OMAP like I2C interface for the TVP decoders, contiguous buffer management) for DM644x. Next: Patches for NAND (DM6467, DM355 and DM644x), NOR on DM644x, Audio Driver support on DM6467 and DM355, SPI on DM6467 and DM355, Video capture on DM355, Support for Micron Sensors in the Video capture for DM644x and DM355, Video display framework using Encoder/Display manager and encoder modules for DM644x, fbdev display driver updates to use new Video display framework, fbdev display support for DM355 and V4L2 display driver for DM355 and DM644x. Later: Patches for IPIPE on DM355, Previewer/Resizer on DM644x, H3A on DM644x and DM355, Video display/capture and VDCE driver support on DM6467, MMC/SD driver support on DM355 and USB support on DM6467 and DM355. We want to benefit from the review and feedback from the DaVinci Linux community as we supply these patches, so the timeline for completing this process will depend on how extensive the community comments turn out to be. I will share updates and status of this plan to the list on a monthly basis. Is the ultimate goal to get these patches into the mainline kernel? That would be really good. The linux-omap guys are making an effort to get all the omap patches upstream. Philip Thanks and regards Sneha Narnakaje ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Re: FYI - TI patch plan
Narnakaje, Snehaprabha wrote: Hi, Texas Instruments plans to improve and/or add support for TI's family of DaVinci SoCs. This work is being done by a number of us here and I am coordinating the efforts. Beginning this month, TI will contribute patches to the DaVinci GIT tree, with the goal to update DM644x and add DM355 and DM6467 support. Another goal is to get all driver features and bug fixes up-ported from earlier TI/MontaVista LSP releases for these devices. We plan to follow the approximate roadmap below: September/October 2008: Patches for DM6467/DM355 baseport, DM9000 Ethernet (DM355), I2C (DM6467/DM355), GPIO (DM6467/DM355), EDMA (DM6467/DM355) and Video Capture (Using OMAP like I2C interface for the TVP decoders, contiguous buffer management) for DM644x. Next: Patches for NAND (DM6467, DM355 and DM644x), NOR on DM644x, Audio Driver support on DM6467 and DM355, SPI on DM6467 and DM355, Video capture on DM355, Support for Micron Sensors in the Video capture for DM644x and DM355, Video display framework using Encoder/Display manager and encoder modules for DM644x, fbdev display driver updates to use new Video display framework, fbdev display support for DM355 and V4L2 display driver for DM355 and DM644x. Later: Patches for IPIPE on DM355, Previewer/Resizer on DM644x, H3A on DM644x and DM355, Video display/capture and VDCE driver support on DM6467, MMC/SD driver support on DM355 and USB support on DM6467 and DM355. We want to benefit from the review and feedback from the DaVinci Linux community as we supply these patches, so the timeline for completing this process will depend on how extensive the community comments turn out to be. I will share updates and status of this plan to the list on a monthly basis. Is the ultimate goal to get these patches into the mainline kernel? That would be really good. The linux-omap guys are making an effort to get all the omap patches upstream. Philip Thanks and regards Sneha Narnakaje ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source smime.p7s Description: S/MIME Cryptographic Signature ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: What is the easiest way to change the brightness on the TVP5146.Through an ioctl?
How about writing directly to the file /sys/class/davinci_display/ch0/brightness. The SPRUEL6.pdf has similar examples but only for mode and output. I think this should be extendable to brightness too - though the LSP SPRUel6.pdf does not say anything about brightness. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panchy Rivas Sent: Tuesday, September 30, 2008 7:46 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: What is the easiest way to change the brightness on the TVP5146.Through an ioctl? What is the easiest way to change the brightness on the TVP5146. Through an ioctl?? Thanks Panchy Rivas DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: What is the easiest way to change the brightness on the TVP5146.Through an ioctl?
Hi, I use the following ioctl to set brightness: struct v4l2_control ctrl; ctrl.id = V4L2_CID_BRIGHTNESS; ctrl.value = i; ioctl(capture_fd, VIDIOC_S_CTRL, ctrl); cheers, Fredrik From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panchy Rivas Sent: den 30 september 2008 16:16 To: davinci-linux-open-source@linux.davincidsp.com Subject: What is the easiest way to change the brightness on the TVP5146.Through an ioctl? What is the easiest way to change the brightness on the TVP5146. Through an ioctl?? Thanks Panchy Rivas ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: What is the easiest way to change the brightness on the TVP5146. Through an ioctl?
Hello, You could use VIDIOC_QUERYCTRL, G_CTRL S_CTRL ioctls to change brightness and other control parameters in TVP5146 email: [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Panchy Rivas Sent: Tuesday, September 30, 2008 10:16 AM To: davinci-linux-open-source@linux.davincidsp.com Subject: What is the easiest way to change the brightness on the TVP5146. Through an ioctl? What is the easiest way to change the brightness on the TVP5146. Through an ioctl?? Thanks Panchy Rivas ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: EVMDM6446 and dvsdk_1_30_00_40
Hi, Your problem is nothing to do with following logs. It means you need to enable video port to use AEW/AF drivers. For capture this is not an issue. Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6 Look at the cause of following errors which shouldn't happen:- Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 I think for vid1 kernel args, you have a space before 2500K. video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K ^ Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 Phone : 301-515-3736 email: [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ketan deshpande Sent: Tuesday, September 30, 2008 5:27 AM To: Linux DaVinci Subject: EVMDM6446 and dvsdk_1_30_00_40 Hello Everybody, I am following the sprue66d.pdf for using the DVEVM with DVSDK_1_30_00_40 But it fails saying *** Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Capturing 720x480 video (cropped to 720x480) Total I-frames: 0, P-frames: 0, B-frames: 0, IDR-frames: 0 rejected: 0 *** on further investigation we found that kernel itself was having some issues opening the video port. following is the part of dmesg; *** Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 2500KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 1020KB watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Linux video capture interface: v1.00 Registering platform device 'vpfe.1'. Parent at platform DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded Registering platform device 'DavinciDisplay.1'. Parent at platform Trying to register davinci display video device. layer=c73dfc00,layer-video_dev=c73dfd64 Trying to register davinci display video device. layer=c73dfa00,layer-video_dev=c73dfb64 davinci_init:DaVinci V4L2 Display Driver V1.0 loaded Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 *** following is my bootarg Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=142.102.22.174:/home/ketan/workdir/filesys,nolock mem=116M ip=142.102.22.85:142.102.22.174:142.102.22.39:255.255.254.0:dm6446evm::off dm9000eth=mac:00.0e.99.02.5b.71 video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc Has anybody else observed the same issue? Any idea how to resolve that? regards, -Ketan Be the first one to try the new Messenger 9 Beta! Click here.http://in.rd.yahoo.com/tagline_messenger_7/*http:/in.messenger.yahoo.com/win/ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: EVMDM6446 and dvsdk_1_30_00_40
Phil, In the kernel bootargs, you always allocate maximum buffers and resolutions. But in FBIOPUT_VSCREENINFO, you can override with NTSC or any other resolution related parameters as long as we have enough buffers allocated for the resolution . The problem that Ketan has is because of incorrect bootargs. See my email for details. Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 Phone : 301-515-3736 email: [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Quiney Sent: Tuesday, September 30, 2008 5:40 AM To: ketan deshpande; Linux DaVinci Subject: RE: EVMDM6446 and dvsdk_1_30_00_40 Hi, The problem is the buffer sizes - you are setting the mode to NTSC but are using PAL size buffers. If you change the sizes to 720x480 in the bootargs it should work. With the older kernel this did not cause a problem, however with the 'unified' kernel it matters. At least that is what we have found ;-) Regards Phil Q Phil Quiney, Senior Software Engineer Trinity Convergence Cambridge Business Park Cowley Road Cambridge CB4 0WZ, UK T: +44(0)1223-435536 F: +44(0)1223-435560 www.trinityconvergence.comhttp://www.trinityconvergence.com/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ketan deshpande Sent: 30 September 2008 10:27 To: Linux DaVinci Subject: EVMDM6446 and dvsdk_1_30_00_40 Hello Everybody, I am following the sprue66d.pdf for using the DVEVM with DVSDK_1_30_00_40 But it fails saying *** Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Capturing 720x480 video (cropped to 720x480) Total I-frames: 0, P-frames: 0, B-frames: 0, IDR-frames: 0 rejected: 0 *** on further investigation we found that kernel itself was having some issues opening the video port. following is the part of dmesg; *** Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 2500KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 1020KB watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Linux video capture interface: v1.00 Registering platform device 'vpfe.1'. Parent at platform DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded Registering platform device 'DavinciDisplay.1'. Parent at platform Trying to register davinci display video device. layer=c73dfc00,layer-video_dev=c73dfd64 Trying to register davinci display video device. layer=c73dfa00,layer-video_dev=c73dfb64 davinci_init:DaVinci V4L2 Display Driver V1.0 loaded Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 *** following is my bootarg Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=142.102.22.174:/home/ketan/workdir/filesys,nolock mem=116M ip=142.102.22.85:142.102.22.174:142.102.22.39:255.255.254.0:dm6446evm::off dm9000eth=mac:00.0e.99.02.5b.71 video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc Has anybody else observed the same issue? Any idea how to resolve that? regards, -Ketan Be the first one to try the new Messenger 9 Beta! Click here.http://in.rd.yahoo.com/tagline_messenger_7/*http:/in.messenger.yahoo.com/win/ ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
PC/104 boards with DM355?
Hi. I am new to the TI DaVinci world and am glad to have found this group. I am on the business side of a project that plans to use the DM355. I have been searching in vain for a PC/104 board based on the DM355. Is anyone aware of this or any other single board computers already on the market? Thanks, John John Huang Oakwood Controls +1-717-318-4812 (cell) +1-717-326-1054 (fax) ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
RE: PC/104 boards with DM355?
Not the DM355 but we are using this one http://www.einfochips.com/services/DVPB.html that makes use of the DM6446 and is an all in one board and much smaller than the DVEVM. Josh From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Huang Sent: Tuesday, September 30, 2008 8:57 PM To: 'Linux DaVinci' Subject: PC/104 boards with DM355? Hi. I am new to the TI DaVinci world and am glad to have found this group. I am on the business side of a project that plans to use the DM355. I have been searching in vain for a PC/104 board based on the DM355. Is anyone aware of this or any other single board computers already on the market? Thanks, John John Huang Oakwood Controls +1-717-318-4812 (cell) +1-717-326-1054 (fax) ___ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
Password locked in dm355 board in NFS mount.
Hi, I tried to create ramdisk.gz for applications that I created in the nfs mounts. My host machine was rebooted a couple of times during this experiment. After then I tried to remount the NFS and now I cannot go beyond the login prompt. The system is locked at this stage - and I'm not able to decipher the error message 10.100.135.50 login: root /bin/login: error wh Could some one please tell me what is wrong and why this could happen. Cheers, Deepak DM355 EVM # DM355 EVM # DM355 EVM # DM355 EVM # DM355 EVM # DM355 EVM # DM355 EVM # DM355 EVM # printenv bootdelay=3 baudrate=115200 root=/dev/nfs gateway=10.100.135.1 bootfile=uImage filesize=a2772c fileaddr=8200 netmask=255.255.255.0 ipaddr=10.100.135.50 serverip=10.100.135.120 stdin=serial stdout=serial stderr=serial videostd=pal bootcmd=nboot 0x8070 0 0x40;bootm nfshost=10.100.135.120 rootpath=/home/dsv/workdir/filesys bootargs=console=ttyS0,115200n8 noinitrd rw ip=10.100.135.50:10.100.135.120:10.100.135.1:255.255.255.0:::off root=/dev/nfs nfsroot=10.100.135.120:/home/dsv/workdir/filesys,nolock mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576 x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal Environment size: 672/16380 bytes DM355 EVM # boot Loading from NAND 1GiB 3,3V 8-bit, offset 0x40 Image Name: Linux-2.6.10_mvl401 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1580692 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 ## Booting image at 8070 ... Image Name: Linux-2.6.10_mvl401 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1580692 Bytes = 1.5 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux... Linux version 2.6.10_mvl401 ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Jul 23 18:48:44 EDT 2008 CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ) CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets Machine: DaVinci DM355 EVM Memory policy: ECC disabled, Data cache writeback DM0350 Built 1 zonelists Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=10.100.135.50:10.100.135.120:10.100.135.1:255.255.255.0:::off root=/dev/nfs nfsroot=10.100.135.120:/home/dsv/workdir/filesys,nolock mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576 x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal PID hash table entries: 512 (order: 9, 8192 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 116MB = 116MB total Memory: 114176KB available (2749K code, 570K data, 180K init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok spawn_desched_task() desched cpu_callback 3/ ksoftirqd started up. desched cpu_callback 2/ desched thread 0 started up. NET: Registered protocol family 16 DaVinci: 104 gpio irqs Registering platform device 'serial8250.0'. Parent at platform Registering platform device 'musb_hdrc'. Parent at platform Registering platform device 'nand_davinci.0'. Parent at platform Registering platform device 'dm9000.0'. Parent at platform Registering platform device 'mmc.0'. Parent at platform Registering platform device 'mmc.1'. Parent at platform DaVinci I2C DEBUG: 18:46:01 Jul 23 2008 Registering platform device 'i2c'. Parent at platform ch0 default output COMPOSITE, mode PAL VPBE Encoder Initialized LogicPD encoder initialized SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub musb_hdrc: version 2.2a/db-0.4.8 [cppi-dma] [host] [debug=0] musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn) musb_hdrc: MHDRC RTL version 1.300 musb_hdrc: USB Host mode controller at c7802000 using DMA, IRQ 12 musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected Registering platform device 'dm_spi.0'. Parent at platform NetWinder Floating Point Emulator V0.97 (double precision) JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. yaffs Jul 23 2008 18:45:29 Installing. Initializing Cryptographic API Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 mailto:[EMAIL PROTECTED],0 with framebuffer size 2025KB
Re: EVMDM6446 and dvsdk_1_30_00_40
Hello Murali Phil, Thanks for your suggestions. As mentioned by Murali the space was the issue. I just checked I still those get warning messages but that has no effect on working of those encodedecode demos. regards, -Ketan - Original Message From: Karicheri, Muralidharan [EMAIL PROTECTED] To: ketan deshpande [EMAIL PROTECTED]; Linux DaVinci davinci-linux-open-source@linux.davincidsp.com Sent: Tuesday, 30 September, 2008 9:39:07 PM Subject: RE: EVMDM6446 and dvsdk_1_30_00_40 Hi, Your problem is nothing to do with following logs. It means you need to enable video port to use AEW/AF drivers. For capture this is not an issue. Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6 Look at the cause of following errors which shouldn’t happen:- Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 I think for vid1 kernel args, you have a space before 2500K. video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K ^ Murali Karicheri Software Design Engineer Texas Instruments Inc. Germantown, MD 20874 Phone : 301-515-3736 email: [EMAIL PROTECTED] From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ketan deshpande Sent: Tuesday, September 30, 2008 5:27 AM To: Linux DaVinci Subject: EVMDM6446 and dvsdk_1_30_00_40 Hello Everybody, I am following the sprue66d.pdf for using the DVEVM with DVSDK_1_30_00_40 But it fails saying *** Encodedecode demo started. Encodedecode Error: Failed FBIOPUT_VSCREENINFO on /dev/fb/3 (Invalid argument) Encodedecode Error: Failed ioctl FBIOPUT_VSCREENINFO on /dev/fb/0 Capturing 720x480 video (cropped to 720x480) Total I-frames: 0, P-frames: 0, B-frames: 0, IDR-frames: 0 rejected: 0 *** on further investigation we found that kernel itself was having some issues opening the video port. following is the part of dmesg; *** Registering platform device 'davincifb.0'. Parent at platform davincifb davincifb.0: dm_osd0_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid0_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid0_fb: [EMAIL PROTECTED],0 with framebuffer size 2500KB davincifb davincifb.0: dm_osd1_fb: [EMAIL PROTECTED],0 with framebuffer size 675KB davincifb davincifb.0: dm_vid1_fb: Initial window configuration is invalid. davincifb davincifb.0: dm_vid1_fb: [EMAIL PROTECTED],0 with framebuffer size 1020KB watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec Registering platform device 'davinci_resizer.2'. Parent at platform Registering platform device 'davinci_previewer.2'. Parent at platform Linux video capture interface: v1.00 Registering platform device 'vpfe.1'. Parent at platform DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected DaVinci I2C WARNING: i2c: NACK detected vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded Registering platform device 'DavinciDisplay.1'. Parent at platform Trying to register davinci display video device. layer=c73dfc00,layer-video_dev=c73dfd64 Trying to register davinci display video device. layer=c73dfa00,layer-video_dev=c73dfb64 davinci_init:DaVinci V4L2 Display Driver V1.0 loaded Davici AEW Driver cannot be loaded VIDEO PORT is not enabledData Flow path from CCDC is disabled Davinci AF driver cannot be loaded VIDEO PORT is not enabled CCDC needs to be configured6Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 *** following is my bootarg Kernel command line: console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=142.102.22.174:/home/ketan/workdir/filesys,nolock mem=116M ip=142.102.22.85:142.102.22.174:142.102.22.39:255.255.254.0:dm6446evm::off dm9000eth=mac:00.0e.99.02.5b.71 video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=ntsc Has anybody else observed the same issue? Any idea how to resolve that? regards, -Ketan Be the first one to try the new Messenger 9 Beta! Click here. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/___ Davinci-linux-open-source mailing list
