from:"Deepak Mundra"

Re: Embedded web browser

2009-11-06 Thread Deepak Mundra

On Thu, Nov 5, 2009 at 9:53 PM, Leon Woestenberg  wrote:

> Hello James,
>
> On Thu, Nov 5, 2009 at 4:23 PM, James McGloin
>  wrote:
> > Can anyone suggest to me a suitable open source web browser that can be
> > ported to the DM355 or DM6446.
> >
> > lighttpd.
> >
> As James pointed out to me, I was not reading.
> Glad he chose lighttpd as the server though :-)
>
> I suggest Midori as a lightweight browser but there are (lots) more.
>
>
Thanks for the pointer .. .. I read that it is under EXPAT licesnse  .. and
I din find option to cross build to arm in configure file


> Regards
> --
> Leon
>
> ___
> 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: ping problem on DM6446

2009-09-15 Thread Deepak Mundra

lt)
> Setting Up Clocks for DM420 OSD
> Console: switching to colour frame buffer device 90x30
> fb0: dm_osd0_fb frame buffer device
> fb1: dm_vid0_fb frame buffer device
> fb2: dm_osd1_fb frame buffer device
> fb3: dm_vid1_fb frame buffer device
> Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
> Platform driver 'serial8250' needs updating - please use dev_pm_ops
> serial8250.0: ttyS0 at MMIO 0x1c2 (irq = 40) is a 16550A
> console [ttyS0] enabled
> serial8250 serial8250.0: unable to register port at index 1 (IO0 MEM1c20400
> IRQ4
> 1): -22
> serial8250 serial8250.0: unable to register port at index 2 (IO0 MEM1c20800
> IRQ4
> 2): -22
> brd: module loaded
> at24 1-0050: 32768 byte 24c256 EEPROM (writable)
> davinci_emac_probe: using random MAC addr: 76:ef:60:a9:74:0b
> emac-mii: probed
> dm9000 Ethernet Driver, V1.31
> Platform driver 'dm9000' needs updating - please use dev_pm_ops
> console [netcon0] enabled
> netconsole: network logging started
> i2c /dev entries driver
> TCP cubic registered
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> Clocks: disable unused uart1
> Clocks: disable unused uart2
> Clocks: disable unused ide
> Clocks: disable unused asp0
> Clocks: disable unused mmcsd
> Clocks: disable unused spi
> Clocks: disable unused usb
> Clocks: disable unused vlynq
> Clocks: disable unused pwm0
> Clocks: disable unused pwm1
> Clocks: disable unused pwm2
> Clocks: disable unused timer1
> Looking up port of RPC 13/2 on 172.16.1.244
> rpcbind: server 172.16.1.244 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 15/1 on 172.16.1.244
> rpcbind: server 172.16.1.244 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> Root-NFS: Server returned error -5 while mounting /home/rohan/dir
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "nfs" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(2,0)
>
>
>
> --- On *Mon, 14/9/09, Deepak Mundra * wrote:
>
>
> From: Deepak Mundra 
> Subject: Re: ping problem on DM6446
> To: "rohan tabish" 
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Date: Monday, 14 September, 2009, 12:07 PM
>
>
>
> Hi,
>
>   Is it from uboot level or file system level ? which file system are
> you using ...
>
>
> On Mon, Sep 14, 2009 at 11:52 AM, rohan tabish 
> http://mc/compose?to=rohan_ja...@yahoo.co.uk>
> > wrote:
>
>> Hey guys i am using DM6446.I think there is something wrong with the board
>> the board is able to ping all the other PC's on the network but is other
>> computer are unable to ping the board.The board is also unable to ping
>> itself.
>>
>>
>> With Regard's
>>
>> Rohan Tabish
>>
>>
>> ___
>> Davinci-linux-open-source mailing list
>> Davinci-linux-open-source@linux.davincidsp.com<http://mc/compose?to=davinci-linux-open-sou...@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: ping problem on DM6446

2009-09-14 Thread Deepak Mundra

Hi,

  Is it from uboot level or file system level ? which file system are
you using ...


On Mon, Sep 14, 2009 at 11:52 AM, rohan tabish wrote:

> Hey guys i am using DM6446.I think there is something wrong with the board
> the board is able to ping all the other PC's on the network but is other
> computer are unable to ping the board.The board is also unable to ping
> itself.
>
>
> With Regard's
>
> Rohan Tabish
>
>
> ___
> 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: Implementing a graphic driver for davinci that supports the CodecEngine 2 Bitblit.

2009-09-10 Thread Deepak Mundra

Hi Craig,

Thanks for the pointer.. this topic was interesting .. Even i am waiting for
response from TI engineers.

On Thu, Sep 10, 2009 at 5:47 AM, Craig Matsuura wrote:

> I guess if I move to the latest directfb 1.4.2 (not 2.0) I will have image
> providers. Any thoughts on the idea of using the BitBlit for the codec
> engine 2?
>
>
> Thanks,
> Craig
>
>
> On Friday 04 September 2009 9:39:02 am Craig Matsuura wrote:
> > Denis,
> >
> >
> >
> >
> >
> > I have posted several times regarding davinci support and found a Bitblit
> (2D acceleration) service for the the Codec Engine 2. Do you know if anyone
> > has started a driver to support this service? (
> http://wiki.davincidsp.com/index.php/Bitblit_Users_Guide).
> >
> >
> >
> >
> >
> > I started down the path to use the driver support in directfb for
> davinci, but I need a 24 bit vid0 (RGB) framebuffer and I also need to use
> the codec engine so I abandon the idea of using the driver in directfb. Now
> that I see there appears to be some 2D acceleration support for Codec Engine
> 2 I want to pursue this as a solution.
> >
> >
> >
> >
> >
> > Can you take a look at the site (
> http://wiki.davincidsp.com/index.php/Bitblit_Users_Guide) and see if it
> makes any sense to create a driver for this new service. If so I would be
> happy to help in implementing a driver (assuming I can still do 24 bit RGB
> on vid0). This seems to be the best solution for my needs, your thoughts?
> >
> >
> >
> >
> >
> > My main motive for this is the Codec Engine 2 and performance of drawing
> to a 1280x720x24 (rgb) framebuffer. Our UI needs require a 720p interface
> and the only way to get this is via the vid0 as the osd0 has a silicon bug
> when displaying at 1280x720x16.
> >
> >
> >
> >
> >
> > Also, I am considering creating ImageProviders that will use the Codec
> Engine codecs for jpeg and other format decoding.
> >
> >
> >
> >
> >
> > Thanks,
> > Craig
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
>
>
> --
>
>
> Craig Matsuura - Principal Engineer
> Control4
> 11734 South Election Road - Suite 200
> Salt Lake City, UT 84020-6432
> PH: 801-523-3161
> FX: 801-523-3199
>
> ___
> 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: RE: I can't boot linux2.6.18 uImage in dm355

2009-05-15 Thread Deepak Mundra

Dear zuowenping,

 can you please check if following patch is applied.. even i had faced same
issue in my dm6446 board when i was trying to boot 2.6.23 kernel .. some 1
gave me this patch and it worked for me.. Just check if this patch is
already applied .. AND iam not sure if this works for dm355


arch/arm/boot/compressed/Makefile   |4 
 arch/arm/boot/compressed/head-davinci.S |   19 +++
 2 files changed, 23 insertions(+), 0 deletions(-)

diff --git a/arch/arm/boot/compressed/Makefile
b/arch/arm/boot/compressed/Makefile
index 1a0ea5d..fcf69da 100644
--- a/arch/arm/boot/compressed/Makefile
+++ b/arch/arm/boot/compressed/Makefile
@@ -54,6 +54,10 @@ ifeq ($(CONFIG_MACH_OMAP_PERSEUS2),y)
 OBJS+= head-omap.o
 endif

+ifeq ($(CONFIG_ARCH_DAVINCI),y)
+OBJS+= head-davinci.o
+endif
+
 ifeq ($(CONFIG_CPU_BIG_ENDIAN),y)
 OBJS+= big-endian.o
 endif
diff --git a/arch/arm/boot/compressed/head-davinci.S
b/arch/arm/boot/compressed/head-davinci.S
new file mode 100644
index 000..5cd3fc9
--- /dev/null
+++ b/arch/arm/boot/compressed/head-davinci.S
@@ -0,0 +1,19 @@
+/*
+ * linux/arch/arm/boot/compressed/head-davinci.S
+ *
+ * DaVinci specific tweaks.  This is merged into head.S by the linker.
+ *
+ */
+
+#include 
+#include 
+#include 
+
+.section".start", "ax"
+
+__davinci_start:
+#ifdef CONFIG_MACH_DAVINCI_EVM
+/* support for booting without u-boot */
+movr7, #(MACH_TYPE_DAVINCI_EVM & ~0xf)
+orrr7, r7, #(MACH_TYPE_DAVINCI_EVM & 0xf)
+#endif


On 5/15/09, zuowenping  wrote:
>
>  dear all:
> when i run command make ARCH=arm CROSS_COMPILE=arm_v5t_le-
> checksetconfig,some errors occurs:
> #
> # configuration written to .config
> #
>
> python /mnt/lsp/ti-davinci/linux-2.6.18_pro500/scripts/kconfig/checksetflags 
> -z -v --config-file .config --flag-file 
> /mnt/lsp/ti-davinci/linux-2.6.18_pro500/scripts/kconfig/baseconfig
> Could not find platform independent libraries 
> Could not find platform dependent libraries 
> Consider setting $PYTHONHOME to [:]
> 'import site' failed; use -v for traceback
> Traceback (most recent call last):
>
>   File 
> "/mnt/lsp/ti-davinci/linux-2.6.18_pro500/scripts/kconfig/checksetflags", line 
> 3, in ?
> import os
> ImportError: No module named os
> make[1]: *** [checksetconfig] Error 1
> make: *** [checksetconfig] Error 2
>
>
>
> if i ignore  these errors,I can compile and got a uImage,but it cann't
> boot up linux too!
>
>
> 2009-05-15
> ------
>  zuowenping
> --
> *发件人：* B, Ravi
> *发送时间：* 2009-05-15  11:47:43
> *收件人：* JayaKumar, PremKumar; zuowenping; Deepak Mundra
> *抄送：* davinci-linux-open-source
> *主题：* RE: I can't boot linux2.6.18 uImage in dm355
>
> Hi
>
>
>
> Go to menuconfig, kernel Features-> select “allow old ABI binaries to run
> with this kernel” or  disable the “ARM EABI to compile the kernel”. Then do
> clean build. This should resolve the issue.
>
>
>
> Regards
>
> Ravibabu
>
>
>  --
>
> *From:* davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:
> davinci-linux-open-source-boun...@linux.davincidsp.com] *On Behalf Of 
> *JayaKumar,
> PremKumar
> *Sent:* Friday, May 15, 2009 8:16 AM
> *To:* zuowenping; Deepak Mundra
> *Cc:* davinci-linux-open-source
> *Subject:* RE: I can't boot linux2.6.18 uImage in dm355
>
>
>
> I faced similar issue when switching between kernel builds for different
> platforms. In such cases, a proper/full clean before build helped in getting
> the right uImage built. Probably, you can try that too.
>
>
>
> make distclean
>
> make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig
>
> make ARCH=arm CROSS_COMPILE=arm_v5t_le- checksetconfig
>
> make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
>
>
>
> Regards,
>
> Prem
>
> Texas Instruments
>
> India
>
>
>  --
>
> *From:* davinci-linux-open-source-bounces+premkumar.j=ti.com@
> linux.davincidsp.com 
> [mailto:davinci-linux-open-source-bounces+premkumar.j
> =ti@linux.davincidsp.com] *On Behalf Of *zuowenping
> *Sent:* Friday, May 15, 2009 6:39 AM
> *To:* Deepak Mundra
> *Cc:* davinci-linux-open-source
> *Subject:* Re: Re: I can't boot linux2.6.18 uImage in dm355
>
>
>
> thanks Deepak:
>
> I have configed kernel by the command :
>
>   make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig
>
>   make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
>
> use the default configs f

Re: I can't boot linux2.6.18 uImage in dm355

2009-05-14 Thread Deepak Mundra

Dear zuowenping

 do make menuconfig

 Enable kernel hacking->kernel debuging->low level debug functions
and compile the kernel and post the kernel output here


Regards
Deepak

On 5/14/09, Steve Chen  wrote:
>
> On Thu, 2009-05-14 at 13:49 +0800, zuowenping wrote:
> > My develop envirment :
> > DaVinciLSP_02_00_00_110 ,mvltools5_0_0801921  and dm355 evm
> > I have built the kernel by reference the pdf " TMS320DM355 DVEVM v1.30
> > Getting Started Guide" ,
> > DM355 EVM # printenv
> > bootdelay=3
> > baudrate=115200
> > bootfile=uImage
> > bootcmd=nboot 0x8070 0 0x40;bootm 0x8070
> > fileaddr=8070
> > ipaddr=10.0.0.53
> > bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
> nfsroot=10.0.0.89:/nfs/restore_dm355,nolock mem=116M
> video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,
> 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE
> davinci_enc_mngr.ch0_mode=pal
> > serverip=10.0.0.89
> > filesize=2191c0
> > stdin=serial
> > stdout=serial
> > stderr=serial
> > videostd=pal
> >
> > Environment size: 491/16380 bytes
> > why not success?
> > Any clues will be appreciated!
>
>
> Just want to make sure I understand, you can boot the board with the
> binary that comes with DVSDK, but you can not boot the board with the
> binary generated by following the "Getting Started Guide"
>
> If that is the case,   what are the commands you used to configure and
> build the kernel and what error did you see during boot up?
>
>
> Regards,
>
> Steve
>
>
>
> ___
> 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: THS8200 Module and DM6446EVM Initial Setup

2009-04-23 Thread Deepak Mundra

On 4/21/09, Jerry Johns  wrote:
>
>  Yup, we have done the shorting of the register
>
> I do get video on the monitor, and the picture shown is spatially correct
> (i.e, the pixels are where they’re supposed to be)
>
> However, the colors are extremely different; Here’s a snippet of my posting
> on the TI E2E Community Forum:
>
>  I recently just purchased a THS8200 Daughter card (Rev A hardware) and
> have been trying to get it to work with the DM6446 EVM. I'm using DVSDK 1.30
> (dvsdk_1_30_00_40) along with LSP 1.20. Support for the THS already exists
> in the kernel, and the relevant mode is "COMPONENT1" and the two resolutions
> it supports are "720P-60" and "1080I-30".
>
> I've tried the following bootargs:
> *video=davincifb:vid1=off:vid0=1280x720x16,4000K:osd0=1280x720,2025K:osd1=1280x720,2025K
> davinci_enc_mngr.ch0_output=COMPONENT1 davinci_enc_mngr.ch0_mode=720P-60
> console=ttyS0,115200n8 noinitrd ip=dhcp root=/dev/nfs
> nfsroot=$(nfshost):$(rootpath),nolock mem=120M*
>
> In the kernel, I've written a small test application that mmaps the FBDEV
> driver - sets the attribute OSD layer to make the OSD 0 completely
> transparent so that only VID0 is visible. I've been able to confirm that
> images i write into memory look spatially correct on my VGA display (i.e
> physically correct images).
>
> However, the colors are all quite out of sync! I've tried enabling the
> default color pattern generator mode in the VPBE, and it confirms my
> suspicions. I've also played with the YCCTL register (YCP bit for CbCr
> arrangment) as well as swapping YCOUT/COUT pins (YCSWAP bit in VIDCTL
> register) to no avail.
>
> To rule out the TV, i've enabled the THS8200 VESA test mode pattern, and
> the color bars show up correctly.
>
> I haven't made any modifications to the kernel - does the 720P-60 mode
> work? The PSP documents seem to indicate that this is tested..
>
>
>
> Any help would be appreciated,
>
> Thank you,
>
>
>
> *Jerry Johns*
>
> *Design Engineer*
>
> *Nuvation Research Corp - Canada*
>
> *Tel: (519) 746-2304 ext. 221*
>
> *www.nuvation.com* 
>
>
>
>
>
> ___
> Davinci-linux-open-source mailing list
> Davinci-linux-open-source@linux.davincidsp.com
> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>
>
Dear Jerry

Pleas go through

http://focus.ti.com/apps/docs/techdocsabstract.tsp?appId=79&abstractName=spraan0

Download pdf and zip file search for kernel directory and the ths8200
related files in that .. Hope this will help you.

Regards

Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: u boot and framebuffer interface

2009-04-14 Thread Deepak Mundra

On 4/13/09, Deepika Makhija  wrote:
>
>  Thanks for help.
> Now I am able to display logo, after enabling Framebuffer Console support
> in kernel config.
>
> Device Drivers -> Graphics Support -> Console display driver support  --->
> <*> Framebuffer Console support
>
> Background for the logo is blue by default, I am successfully able to
> replace logo, but failed to change the background color.
> Can you please help me on that.
>
> Regards,
> Deepika
>
> Deepak Mundra wrote:
>
> Hi Seems like your driver configuration is not proper, may be your offset..
> are images coming properly on display ??? .. And please from next time mail
> in mailing list .. it will help other people also
>
> Regards
> deepak
>
> On 4/10/09, Deepika Makhija  wrote:
>
>> Hello,
>>
>> Response is inline to previous help.
>>
>> Deepak Mundra wrote:
>>
>>  hi,
>>
>>
>> On 4/10/09, Deepika Makhija  wrote:
>>>
>>> Hi,
>>>
>>> Mine is VGA 1024x768 output to touchscreen LCD.
>>> I didn't knew that Davinci Kernel, displays logo during boot, some random
>>> display patterns (Vertical lines of different colors) are observed on LCD
>>> during kernel boot up
>>>
>>
>>  did you mean by color baar pattern ?
>>
>> Deepika :
>> No Not the color bar pattern. While u-boot is loaded some random lines are
>> observed, every time different :(
>>
>>   then in driver/video/davincifb.c  check if dispc_reg_out(VENC_VDPRO,
>> 0x100); is enabled .. this value is set to generate colorbar pattern .. if
>> this is line is ther just comment. and try to boot
>>
>> or second thing could be to make sure logo display is enabled in kernel
>>
>> # make menuconfig
>> Device drivers -> Graphics support -> Logo configuration ->bootup logo and
>> select 224 pattern.
>>
>> Deepika :
>> Default Kernel Configuration enables all three options i.e
>> [*]   Standard black and white Linux logo
>> [*]   Standard 16-color Linux logo
>> [* ]   Standard 224-color Linux logo
>>
>> I tried which each of them one by one, but no LOGO appeared, only
>> black(blank) screen.
>>
>>
>>  process (after FB is initialized). Can u help  me in that, i mean guide
>>> if i m missing something in that case
>>>
>>> Thanks,
>>> Deepika
>>>
>>> Deepak Mundra wrote:
>>>
>>>And davinci kernel already has logo display during boot up
>>> ryt, so you can replace that logo with your logo .. this will make logo to
>>> be displayed immediately after frame buffer is initialized in kernel and
>>> before filesystem is loaded..
>>>
>>> On 4/10/09, Deepak Mundra  wrote:
>>>
>>>> Hi,
>>>>
>>>>  Just to confirm .. are you using VGA output or composit .. coz a s
>>>> i mentioned earlier for me it is taking time in ths8200 chip initialization
>>>> code.. coz it uses i2c writes almost in 20+ adress which was taking time ..
>>>> and i felt like it is coz of i2c driver used in uboot 1.2.0 .. So my
>>>> suggetion is that in case if you are not using ths8200 chip you can go 
>>>> ahead
>>>> with that .. and i feel that in latest uboot it should work fine.. you can
>>>> go throgh following link for davincifb support in uboot 1.3.x+ ..i had to 
>>>> do
>>>> little work to pul it down to 1.2.0 ..
>>>>
>>>>
>>>> http://github.com/neuros/u-boot/commit/689195c1865b79f745bcf145a809464dec2f391f
>>>>
>>>>
>>>>
>>>> Thanks & Regards
>>>> Deepak.
>>>>
>>>>
>>>> On 4/10/09, Deepika Makhija  wrote:
>>>>
>>>>> Hello Deepak,
>>>>>
>>>>> Thanks for your inputs. Actually I wanted to display a logo, till the
>>>>> system boots up. I am working on DM355 based product, in which it few 
>>>>> sec's
>>>>> to initialize the everything (ubl,U-boot,kernel,filesystem), so i thought 
>>>>> to
>>>>> display something till the board is up, but if this adds 3/4 sec delay in
>>>>> boot up process than it is of no use for me. I guess, I have to think of
>>>>> some other option like initialize video interface earlier in kernel and
>>>>> display LOGO from the kernel, because loading filesystem from NAND eats up
>>>>> much of the booting time.
&

Re: Issues with 2.6.23 kernel on DM6446 custom board

2009-04-11 Thread Deepak Mundra

On 4/10/09, Deepak Mundra  wrote:
>
> Dear All,
>
> In addition, i would like to attached a few debug prints associated
> with the scenario's described in my previous email:
> > A. When we boot through this kernel(with USB drivers as a kernel
> component):
> >   1. We see that the boot process detects the on board USB Hub, and
> > the boot process fails at the kernel IP-Config routines(the board is
> > configured
> >   to get an IP address through DHCP)
> >   2. The serial console does not seem to respond
> >   3. At this point, If we connect / dicsonnect  a USB Keyboard,Mouse
> > device, the driver prints the appropriate messages indicating that
> > these devices have been connected / disconnected.
>
> For this scenario, The boot up messages are like this :
> ;
> ;
> ;
> usbcore: registered new interface driver usbfs
> usbcore: registered new interface driver hub
> usbcore: registered new device driver usb
> musb_hdrc: version 6.0, cppi-dma, host, debug=0
> musb_hdrc: USB Host mode controller at c800 using DMA, IRQ 12
> musb_hdrc musb_hdrc: MUSB HDRC host driver
> musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
> usb usb1: configuration #1 chosen from 1 choice
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 1 port detected
> ;
> ;
> More boot messages..
> ;
> 0x0005-0x0025 : "kernel"
> <5>0x0025-0x0100 : "filesystem"
> 0x0025-0x0100 : "filesystem"
> <5>usbmon: debugfs is not available
> usbmon: debugfs is not available
> <6>Initializing USB Mass Storage driver...
> Initializing USB Mass Storage driver...
> <6>usbcore: registered new interface driver usb-storage
> usbcore: registered new interface driver usb-storage
> <6>USB Mass Storage support registered.
> USB Mass Storage support registered.
> <6>mice: PS/2 mouse device common for all mice
> mice: PS/2 mouse device common for all mice
> <6>usbcore: registered new interface driver usbhid
> usbcore: registered new interface driver usbhid
> <6>drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
> <6>TCP cubic registered
> TCP cubic registered
> <6>NET: Registered protocol family 1
> NET: Registered protocol family 1
> <6>NET: Registered protocol family 17
> NET: Registered protocol family 17
> <5>Sending DHCP requests .Sending DHCP requests ... timed out!
>  timed out!
> <3>IP-Config: Retrying forever (NFS root)...
> IP-Config: Retrying forever (NFS root)...
> <5>Sending DHCP requests .Sending DHCP requests ... timed out!
>  timed out!
> <3>IP-Config: Retrying forever (NFS root)...
> IP-Config: Retrying forever (NFS root)...
> <5>Sending DHCP requests .Sending DHCP requests ... timed out!
>  timed out!
> <3>IP-Config: Retrying forever (NFS root)...
> IP-Config: Retrying forever (NFS root)...
>
> As you can see, The IP-Config  DHCP requests keep failing, IP is not
> assigned and the board cannot proceed to boot from NFS. Why would the
> USB function cause the IP-Config DHCP routines to fail??
>
>
> > B. When we boot through this kernel with the USB drivers compiled as
> > modules ( HID support compiled within kernel)
> >  1. The boot process, IP-Config, launching of shell happens successfully.
> >  2. From the shell launched on the serial console, if we insmod
> > musb_hdrc.ko, insmod command does not seem to return to console prompt
> > and the serial console freezes like described in (A) above. Again
> > devices
> > connected / disconnected are still reported correctly on the
> > frozen serial console.The USB devices seem to work properly, causing
> > the serial console to freeze.
>
> In this case, the boot messages are like this:
>
> start of boot.
> ;
> ;
> ;
> ;
> ;
> <6>NET: Registered protocol family 1
> NET: Registered protocol family 1
> <6>NET: Registered protocol family 17
> NET: Registered protocol family 17
> <5>Sending DHCP requests .Sending DHCP requests ...,, OK
>  OK
> IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer
> from 0.0.0.0, my address is 192.168.1.194
> my address is 192.168.1.194
> IP-Config: Complete:IP-Config: Complete:
>  device=eth0
>  device=eth0, addr=192.168.1.194, addr=192.168.1.194,
> mask=255.255.255.0, mask=255.255.255.0, gw=192.168.1.1,
> gw=192.168.1.1, .
> ;
> ;
> ;
> ;
> 192.168.1.194 login: root
> #insmod ./musb_hdrc.ko
> r...@192.168.1.194:~# insmod ./musb_hdrc.ko
> <6>musb_hdrc: v

Re: Issues with 2.6.23 kernel on DM6446 custom board

2009-04-10 Thread Deepak Mundra

er at c805 using DMA, IRQ 12
musb_hdrc: USB Host mode controller at c805 using DMA, IRQ 12
<6>musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: MUSB HDRC host driver
<6>musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
<6>usb usb1: configuration #1 chosen from 1 choice
usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
hub 1-0:1.0: 1 port detected
r...@192.168.1.194:~# <6>usb 1-1: new high speed USB device using
musb_hdrc and address 2
usb 1-1: new high speed USB device using musb_hdrc and address 2
<6>usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: configuration #1 chosen from 1 choice
<6>hub 1-1:1.0: USB hub found
hub 1-1:1.0: USB hub found
<6>hub 1-1:1.0: 4 ports detected
hub 1-1:1.0: 4 ports detected
;
;
;
[Does not return to # prompt, serial console does not respond]
At this point if i connect,disconnect a USB Keyboard/Mouse/Flash drive.
;
;
<6>usb 1-1.1: new low speed USB device using musb_hdrc and address 3
usb 1-1.1: new low speed USB device using musb_hdrc and address 3
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>input: USB Mouse as /class/input/input0
input: USB Mouse as /class/input/input0
<6>inputinput: USB HID v1.10 Mouse [USB Mouse] on usb-musb_hdrc-1.1
: USB HID v1.10 Mouse [USB Mouse] on usb-musb_hdrc-1.1
<6>usb 1-1.1: USB disconnect, address 3
usb 1-1.1: USB disconnect, address 3
<6>usb 1-1.1: new low speed USB device using musb_hdrc and address 4
usb 1-1.1: new low speed USB device using musb_hdrc and address 4
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>input: Logitech Logitech USB Keyboard as /class/input/input1
input: Logitech Logitech USB Keyboard as /class/input/input1
<6>inputinput: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard]
on usb-musb_hdrc-1.1
: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on
usb-musb_hdrc-1.1
<6>usb 1-1.1: USB disconnect, address 4
usb 1-1.1: USB disconnect, address 4
<6>usb 1-1.1: new high speed USB device using musb_hdrc and address 5
usb 1-1.1: new high speed USB device using musb_hdrc and address 5
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>usb 1-1.1: USB disconnect, address 5
usb 1-1.1: USB disconnect, address 5
;
;
;
[Still we are not returned to prompt]

Pointer will be appreciated!!

regards,
Deepak

On 4/10/09, Deepak Mundra  wrote:
>
> Dear All,
>
> We are working on getting the Linux 2.6.23 kernel working on our Custom
> Board.
> Due to a certain legacy driver ( written only for 2.6.23) we are
> forced to use 2.6.23.
> So far most of the Interfaces on our hardware are working perfectly
> fine with the 2.6.23 kernel. However an issue still remains with the
> USB function. I wil describe this to you:
>
> 1. Our board has a onboard hub chip.
> 2. We compile the 2.6.23 kernel with DaVinci musb drivers, USB HID
> device support.
>
> A. When we boot through this kernel(with USB drivers as a kernel
> component):
>   1. We see that the boot process detects the on board USB Hub, and
> the boot process fails at the kernel IP-Config routines(the board is
> configured
>   to get an IP address through DHCP)
>   2. The serial console does not seem to respond
>   3. At this point, If we connect / disconnect  a USB Keyboard,Mouse
> device, the driver prints the appropriate messages indicating that
> these devices have been connected / disconnected.
>
> B. When we boot through this kernel with the USB drivers compiled as
> modules ( HID support compiled within kernel)
>  1. The boot process, IP-Config, launching of shell happens successfully.
>  2. From the shell launched on the serial console, if we insmod
> musb_hdrc.ko, insmod command does not seem to return to console prompt
> and the serial console freezes like described in (A) above. Again
> devices
> connected / disconnected are still reported correctly on the
> frozen serial console.The USB devices seem to work properly, causing
> the serial console to freeze.
>
> Observing the above two, here is what we tried:
>
> C. With the kernel with the USB drivers compiled as modules and:
>  1. Boot the kernel with the usb musb support compiled as module
>  2. Wait for shell to appear on serial console, start sshd daemon
> from the console shell
>  3. Login to the board via ssh, and insmod musb_hdrc.ko - here the
> insmod returns to the shell!! However, the serial console freezes like
> (A) above.
>  4. USB dev

Issues with 2.6.23 kernel on DM6446 custom board

2009-04-10 Thread Deepak Mundra

Dear All,

We are working on getting the Linux 2.6.23 kernel working on our Custom
Board.
Due to a certain legacy driver ( written only for 2.6.23) we are
forced to use 2.6.23.
So far most of the Interfaces on our hardware are working perfectly
fine with the 2.6.23 kernel. However an issue still remains with the
USB function. I wil describe this to you:

1. Our board has a onboard hub chip.
2. We compile the 2.6.23 kernel with DaVinci musb drivers, USB HID
device support.

A. When we boot through this kernel(with USB drivers as a kernel component):
  1. We see that the boot process detects the on board USB Hub, and
the boot process fails at the kernel IP-Config routines(the board is
configured
  to get an IP address through DHCP)
  2. The serial console does not seem to respond
  3. At this point, If we connect / disconnect  a USB Keyboard,Mouse
device, the driver prints the appropriate messages indicating that
these devices have been connected / disconnected.

B. When we boot through this kernel with the USB drivers compiled as
modules ( HID support compiled within kernel)
 1. The boot process, IP-Config, launching of shell happens successfully.
 2. From the shell launched on the serial console, if we insmod
musb_hdrc.ko, insmod command does not seem to return to console prompt
and the serial console freezes like described in (A) above. Again
devices
connected / disconnected are still reported correctly on the
frozen serial console.The USB devices seem to work properly, causing
the serial console to freeze.

Observing the above two, here is what we tried:

C. With the kernel with the USB drivers compiled as modules and:
 1. Boot the kernel with the usb musb support compiled as module
 2. Wait for shell to appear on serial console, start sshd daemon
from the console shell
 3. Login to the board via ssh, and insmod musb_hdrc.ko - here the
insmod returns to the shell!! However, the serial console freezes like
(A) above.
 4. USB devices connected / disconnected are detected properly
 5. The ssh terminal looks to be healthy, allowing running of applications.

Could some one point out what the issue could be?
I am looking to fix this behaviour in my 2.6.23 kernel tree, and use
the usb function as a kernel compiled functionality.

I understand the 2.6.23 kernel tree may not be of focus at the moment,
but a few pointers on the possible solutions would help me
tremendously as i am trying to get this fixed.

Look forward to some suggestions/pointers.

regards,
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: USB Keyboard/Mouse on DVEVM6446

2009-03-09 Thread Deepak Mundra

Hi André Costa

Can you please tel me the version of kernel u r using .. is it 2.6.10 ?

Thanks
Deepak

2009/3/9 Andre Vinicius Mulho Costa 

> The problem was very simple! =)
>
> I just turned off the board and switched jumper j7 from 1-2 (host-mode) to
> 2-3(device-mode).
>
> Thanks
> André Costa
>
>
> On Fri, Mar 6, 2009 at 10:50 AM, Andre Vinicius Mulho Costa <
> andre.costa@gmail.com> wrote:
>
>> Hi Everyone,
>>
>> I'm trying to use a USB keyboard on DVEVM6446 without success.
>> I'm using mv_pro_4.0, and enabled Device Drivers> Usb Support > USB
>> Human Interface Device (Full HID) support in the kernel menuconfig.
>>
>>
>> When I plug the keyboard, nothing happens (keyboard leds remain off),
>> and when I plug a mouse the red led under it turns on, but in both cases the
>> only device that the command "lsusb" return is:
>>Bus 001 Device 001: ID 04d6: Mentor Graphics
>>
>>
>> Does anybody ever seen a Keyboard or a Mouse working on DVEVM6446 board?
>>
>> Thanks so much for the help,
>>
>> André Costa
>>
>>
>>
>
>
> ___
> 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

USB issue in 2.6.23 kernel

2009-03-08 Thread Deepak Mundra

Dear all,

Im using 2.6.23 /2.6.23-rc4 kernels .. but in both kernels i am not able
to use usb .. if i enable usb-host [ Inventra Highspeed Dual Role Controller
(TI, ...)  ]   it will hang during DHCP and if i disable it will boot
sucessfuly without usb support.. And i also tried with making it as module
and inserting after i boot ,, but when i insert module it will hang with
following debug messages


insmod /lib/modules/2.6.23-davinci1/kernel/drivers/usb/musb
<6>musb_hdrc: version 6.0, pio, host, debug=0
musb_hdrc: version 6.0, pio, host, debug=0
<7>musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn)
<7>musb_hdrc: MHDRC RTL version 1.300
<7>musb_hdrc: setup fifo_mode 2
<7>musb_hdrc: 7/9 max ep, 3392/4096 memory
<7>musb_hdrc: hw_ep 0shared, max 64
<7>musb_hdrc: hw_ep 1tx, max 512
<7>musb_hdrc: hw_ep 1rx, max 512
<7>musb_hdrc: hw_ep 2tx, max 512
<7>musb_hdrc: hw_ep 2rx, max 512
<7>musb_hdrc: hw_ep 3shared, max 1024
<7>musb_hdrc: hw_ep 4shared, max 256
<6>musb_hdrc: USB Host mode controller at c8052000 using PIO, IRQ 12
musb_hdrc: USB Host mode controller at c8052000 using PIO, IRQ 12
<6>musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: MUSB HDRC host driver
<6>musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
<7>usb usb1: default language 0x0409
<7>usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
<6>usb usb1: Product: MUSB HDRC host driver
usb usb1: Product: MUSB HDRC host driver
<6>usb usb1: Manufacturer: Linux 2.6.23-davinci1 musb-hcd
usb usb1: Manufacturer: Linux 2.6.23-davinci1 musb-hcd
<6>usb usb1: SerialNumber: musb_hdrc
usb usb1: SerialNumber: musb_hdrc
<7>usb usb1: uevent
<7>usb usb1: usb_probe_device
<6>usb usb1: configuration #1 chosen from 1 choice
usb usb1: configuration #1 chosen from 1 choice
<7>usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>usb 1-0:1.0: uevent
<7>usb 1-0:1.0: uevent
<7>hub 1-0:1.0: usb_probe_interface
<7>hub 1-0:1.0: usb_probe_interface - got id
<6>hub 1-0:1.0: USB hub found
hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
hub 1-0:1.0: 1 port detected
<7>hub 1-0:1.0: standalone hub
<7>hub 1-0:1.0: individual port power switching
<7>hub 1-0:1.0: no over-current protection
<7>hub 1-0:1.0: Single TT
<7>hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
<7>hub 1-0:1.0: power on to power good time: 10ms
<7>hub 1-0:1.0: local power source is good
<7>hub 1-0:1.0: enabling power on all ports
<7>hub 1-0:1.0: state 7 ports 1 chg  evt 
<7>hub 1-0:1.0: state 7 ports 1 chg  evt 0002
<7>hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s

please give me somepointers regarding this..

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

2.6.23 kernal and frambuffer error : fb0 cannot allocate framebuffer

2009-03-05 Thread Deepak Mundra

Dear all,


 I am using 2.6.23 kernel and trying to get 1024x768 resolution using
davincifb.c i was able to do this by modifying mmzone.h and memory.h in
2.6.10 kernel and off course davincifb.c file ..but in 2.6.23 kernel
memory.h and mmzone.h are bit different.. normaly if you dont modify these
files you will get error

dm_vid0_fb: cannot allocate frambuffer

and i have fixed this issue by adding MAX_ORDER 100 in mmzone.h and
DMA_MAX_SIZE 100 in memory.h files,,  but if i do same change in 2.6.23
kernel i am not able get desired output.. has anybody tried 1024x768 or
above resolution in 23 kernel ???

Thanks & Regards
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Auto mounting USB STICK in DM6446

2009-02-19 Thread Deepak Mundra

Dear all,

   I am able to mount the usb stick manulay using mount command.. but i
want to do this automatically when i connect a usb stick..
I looked into hotplug script , udev rules and also mailing list but it did
not help me .. I am using 2.6.10 kernel and hotplug is enabled in the
kernel... please i need help.

Thanks and Regards
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Problem in Writing NOR U-BOOT

2009-02-18 Thread Deepak Mundra

Dear All,

 I am using TI DVFlasher program on my linux system where i am able to flash
u-boot into NAND but if i write u-boot into NOR
 i get following message

TI UBL Version: 1.00, Flash type: NOR
Booting PSP Boot Loader
PSPBootMode = NOR
Starting NOR Copy...
NOR Initialization:
Command Set: AMD
Manufacturer: AMD
Size (in bytes): 0x0100
NOR Boot success.
   DONE

and then the system is halting for ever.

I have tried with Serial flash utility also .. in that also same problem ..
I am using AMD NOR .. please need help..

Thanks & Regards
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: u boot and framebuffer interface

2009-02-05 Thread Deepak Mundra

On Wed, Feb 4, 2009 at 8:05 PM,  wrote:

>
> Greetings,
>
> Although there are video commands for u-boot, they require framebuffer
> drivers to be written for them.
> No drivers have been written for DM644x as of yet.
>
> Trust me when I say that going to the U-boot mailing list and asking
> someone to do it for you would
> be not very well accepted at all... you'll get the 'if you need it then
> write it and submit patch' answer.
>
> You can keep checking the git tree in hopes that someone will post it and
> have it accepted,
> or you can hit the datasheets and setup the minimum required registers to
> be able to write
> a rgb16 bitmap to a memory location.
>
> It's more work tracking down the register sets than actually writing the
> code.
> Just stick it in the board init in u-boot and zero out the memory before
> activating it.
>
> Note that when the linux framebuffer driver kicks in, your image may
> disappear.
> Also, the DM644x chips can't assign any framebuffer memory over 128MB mark,
> so keep it before 0x8800.
>
> U-Boot git tree:
> http://git.denx.de/?p=u-boot.git;a=summary
>
> Regards,
> David
>
> --
> DAVID A. KONDRAD
> Software Design Engineer
> On-Q/Legrand
> Telephone (800) 321-2343 x311
> www.onqlegrand.com
>
>

Thanks for the replay.. in u-boot board_init function i have added

 board_setup_psc_on(0, LPSC_VPSSMSTR);
 board_setup_psc_on(0, LPSC_VPSSSLV);

I know this will just power on VPSS and as YUSUF told we have to Configuring
few of the VPBE (and may be OSD)registers .. But my question is which all
register we have to configure.. I have basic knowledge about OSD, VPBE
Registers.. I have wokred around in kernel with them..

And second thing , about the linux framebuffer kicking of u-boot splash
image is not a problem for me.. I cane mange with that :) .. I need splash
screen at u-boot level

Once again thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: u boot and framebuffer interface

2009-02-03 Thread Deepak Mundra

On Wed, Feb 4, 2009 at 11:01 AM, Nitin Mahajan  wrote:

> HI!
>
> ___
> From: Deepak Mundra 
> To: "davinci-linux-open-source@linux.davincidsp.com" <
> davinci-linux-open-source@linux.davincidsp.com>
> Sent: Tuesday, February 3, 2009 19:11:30
> Subject: u boot and framebuffer interface
>
> Dear All,
>
>  How can i open frame buffer in u-boot and display a white screen(or bmp
> image).. What i want is ,After switching on board when u-boot executes i
> want to display something on screen ie before executing the kernel.. If some
> one has done this before please guide me through..
>
> Check if this is what you are looking for?
>
> http://www.denx.de/wiki/view/DULG/UBootSplashScreen
>
> regards
>
> -Nitin
>
>
>
>



Thax for the reply but  i have gone through that already and i have enabled
bmp command..but i was not able to enable bmp display because i requires LCD
or VIDEO support to be enabled in u-boot .. which i am not able to do..

Has any one able to use bmp display command in u-boot ?

Thanks
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

u boot and framebuffer interface

2009-02-03 Thread Deepak Mundra

Dear All,

 How can i open frame buffer in u-boot and display a white screen(or bmp
image).. What i want is ,After switching on board when u-boot executes i
want to display something on screen ie before executing the kernel.. If some
one has done this before please guide me through..

Thanks in Advance
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

SETTING VID1 to RGB888/24bit

2009-01-21 Thread Deepak Mundra

Dear all,

 Im trying to to use vid1 /[/dev/fb/3] as RGB888 display screen .. i know by
default it is set to 4:2:2 how can i change it to RGB888?

And i need the boot argument for the same (in case if i have to do something
in kernel).. Please can somebody guide me through this

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

I2c write error

2008-11-16 Thread Deepak Mundra

HI,

   I am using DM6446 and THS8200 based custom board. To configure THS8200, I
am tried to R/W from DM6446 at address 0x20 and 0x21. While using 0x20, I
was able to read and write failed, on other end, while using 0x21, I was
failed in both cases. Any help or pointers is appreciated.

Following is log for I2C address 0x21:
i2c_adapter i2c-0: THS8200 encoder initialized
i2c_adapter i2c-0: i2c read error
i2c_adapter i2c-0: Resetting THS8200 card
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: i2c write error = ff87
i2c_adapter i2c-0: Failed to Program CDCE Clock Synthesiser

(Can someone also explain me this CDCE Clock Synthessier failure ?)


Thanks,

Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Purpose of each kernel tree

2008-11-16 Thread Deepak Mundra

Hi all,
 I have extracted the mvl package, which i received from TI. It has two
kernel tree :
1. /opt/mv_pro_4.0.1_New/montavista/pro/devkit/lsp/ti-davinci
2. /opt/mv_pro_4.0.1_New/montavista/pro/devkit/lsp/ti-davinci_evm-arm_v5t_le
Kindly explain the purpose of each kernel tree..

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: Help in writiing JFFS2 Filesystem into NAND /Uboot

2008-11-13 Thread Deepak Mundra

Hi David,

 I added write.yaffs command to u-boot (using provided patch)
my boot arg is

bootargs=mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
init=/bin/sh noatime rootfstype=yaffs ip=dhcp

(I am using dm6446 so using yaffs instead of yaffs2)

but whiling booting init is failing with following error ..

yaffs: dev is 32505859 name is "mtdblock3"
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
VFS: Mounted root (yaffs filesystem).
Freeing init memory: 136K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Is this because of yaffs image??? is there any sample yaffs image
which i can try with?


Thanks
deepak

On 11/12/08, David Chan <[EMAIL PROTECTED]> wrote:
> You should extend the uboot to support nand write.yaffs2 command, then you
> can just write like jffs2.
> The other way is do it under linux like below:
> boot to nfs
> # flash_eraseall /dev/mtd3
> # mkdir /mnt/nand
> # mount yaffs2 /dev/mtdblock3 /mnt/nand
> # cp -a your fileroot /mnt/nand
> # sync;sync;sync
> # umount /dev/mtdblock3
> reboot and set to use filesystem under yaffs2
>
> 08 at 10:23 PM, Deepak Mundra <[EMAIL PROTECTED]> wrote:
>
>>
>>
>> 2008/11/11 David Chan <[EMAIL PROTECTED]>
>>
>>>
>>>
>>> for nand flash you'd better to use yaff2. If you really decide to use
>>> jffs2 please modify the uboot to enable ecc check.
>>> That's because ecc is not enabled by uboot. Then kernel give a ecc check.
>>> While you write file.jffs2 to the nand, you will meet bad block and bit
>>> reverse.All leads to ecc error.
>>> My suggestion is to use yaffs2 or write mtd under linux environment.
>>>
>>
>> Thanks for ur reply..  I downloaded yafss2 tool to make yaffs2 image ...
>>
>> Now how can i write this image to nand (AT which memory location ? is it
>> 0x46?)
>> i have copied yaffs2 image to 0x8070 location ..
>> and how can i set bootargs for that?
>>
>> is it
>>
>> setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
>> init=/bin/sh noatime rootfstype=yaffs2 ip=off
>>
>> Nd finally u told "or write mtd under linux environment." Can u please
>> give
>> some pointer to this
>>
>> Thanks once again
>> Deepak
>>
>>
>>
>>
>>
>>>
>>>
>>> David
>>>
>>>> Message: 3
>>>> Date: Tue, 11 Nov 2008 17:32:41 +0530
>>>> From: "Deepak Mundra" <[EMAIL PROTECTED]>
>>>> Subject: Help in writiing JFFS2 Filesystem into NAND /Uboot
>>>> To: "davinci-linux-open-source@linux.davincidsp.com"
>>>>
>>>> Message-ID:
>>>><[EMAIL PROTECTED]>
>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>>
>>>>
>>>> Hi,
>>>>
>>>> Has any one tried writing jfss2 filesystem on to nand using uboot ???
>>>>
>>>> I am using following stem but MTD->READ is returning error
>>>>
>>>>
>>>> 1]nand erase 0x46 sizeof_filesystem_image
>>>>
>>>> 2]transfer jffs2 filsystem image to 0x8070
>>>>
>>>> 3]nand write 0x8070 0x46 sizeof_filesystem_image
>>>>
>>>> 4]In kernel i set boot args as follow
>>>>
>>>>
>>>> setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
>>>> init=/bin/sh noatime rootfstype=jffs2
>>>> setenv bootcmd 'nboot 0x8070 0 0x6;bootm'
>>>>
>>>> ANd while booting i am getting  errors like MTD->READ, ECC error etc
>>>>
>>>>
>>>> Thanks
>>>> Deepak
>>>> -- next part --
>>>> An HTML attachment was scrubbed...
>>>> URL:
>>>> http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/2008/7673cb90/attachment-0001.htm
>>>>
>>>> --
>>>>
>>>> Message: 4
>>>> Date: Tue, 11 Nov 2008 18:27:50 +0530
>>>> From: "Prabhaharan R-TLS,Chennai" <[EMAIL PROTECTED]>
>>>> Subject: Davinci DMS355 - Video Encoder
>>>> To: "Stephen Berry" <[EMAIL PROTECTED]>,"Karicheri, Muralidharan"
>>>><[EMAIL PROTECTED]>
>>>> Cc: davinci-linux-open-source
>>>>
>>>> Message-ID:
>

PING issue in u-boot 1.2.0

2008-11-12 Thread Deepak Mundra

Hi all,

I am using u-boot 1.2.0 version..

I am trying to ping to  a system after setting ipaddr ..but resulting
in host not alive

But if i load a kernel with ip=off
and set ip using
ifconfig eth0 ipaddr
then i am able to ping to the other system ..

is there any FIX required in U-boot 1.2.0 source ???

Thanks
Deepak

___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: Help in writiing JFFS2 Filesystem into NAND /Uboot

2008-11-11 Thread Deepak Mundra

2008/11/11 David Chan <[EMAIL PROTECTED]>

>
>
> for nand flash you'd better to use yaff2. If you really decide to use jffs2
> please modify the uboot to enable ecc check.
> That's because ecc is not enabled by uboot. Then kernel give a ecc check.
> While you write file.jffs2 to the nand, you will meet bad block and bit
> reverse.All leads to ecc error.
> My suggestion is to use yaffs2 or write mtd under linux environment.
>

Thanks for ur reply..  I downloaded yafss2 tool to make yaffs2 image ...

Now how can i write this image to nand (AT which memory location ? is it
0x46?)
i have copied yaffs2 image to 0x8070 location ..
and how can i set bootargs for that?

is it

setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
init=/bin/sh noatime rootfstype=yaffs2 ip=off

Nd finally u told "or write mtd under linux environment." Can u please give
some pointer to this

Thanks once again
Deepak





>
>
> David
>
>> Message: 3
>> Date: Tue, 11 Nov 2008 17:32:41 +0530
>> From: "Deepak Mundra" <[EMAIL PROTECTED]>
>> Subject: Help in writiing JFFS2 Filesystem into NAND /Uboot
>> To: "davinci-linux-open-source@linux.davincidsp.com"
>>
>> Message-ID:
>><[EMAIL PROTECTED]>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>>
>> Hi,
>>
>> Has any one tried writing jfss2 filesystem on to nand using uboot ???
>>
>> I am using following stem but MTD->READ is returning error
>>
>>
>> 1]nand erase 0x46 sizeof_filesystem_image
>>
>> 2]transfer jffs2 filsystem image to 0x8070
>>
>> 3]nand write 0x8070 0x46 sizeof_filesystem_image
>>
>> 4]In kernel i set boot args as follow
>>
>>
>> setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
>> init=/bin/sh noatime rootfstype=jffs2
>> setenv bootcmd 'nboot 0x8070 0 0x6;bootm'
>>
>> ANd while booting i am getting  errors like MTD->READ, ECC error etc
>>
>>
>> Thanks
>> Deepak
>> -- next part --
>> An HTML attachment was scrubbed...
>> URL:
>> http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/2008/7673cb90/attachment-0001.htm
>>
>> --
>>
>> Message: 4
>> Date: Tue, 11 Nov 2008 18:27:50 +0530
>> From: "Prabhaharan R-TLS,Chennai" <[EMAIL PROTECTED]>
>> Subject: Davinci DMS355 - Video Encoder
>> To: "Stephen Berry" <[EMAIL PROTECTED]>,"Karicheri, Muralidharan"
>><[EMAIL PROTECTED]>
>> Cc: davinci-linux-open-source
>>
>> Message-ID:
>><
>> [EMAIL PROTECTED]>
>>
>> Content-Type: text/plain; charset="us-ascii"
>>
>>
>> Hello Stephen and Murali,
>>
>>
>>
>> Currently I am working on the Video encoder driver for Davinci DMS 355.
>> The driver is being implemented using the Montavista TI Linux code. As
>> per the existing encoder driver architecture, we can add the customized
>> new driver to the drivers/media folder and we have set the encoder
>> output name in the driver as well in the boot arguments. I have taken
>> the THS8200_encoder.c as reference. Since, the encoder that I am going
>> to use is through I2c, I have selected the ths8200_encoder.c as base.
>>
>>
>>
>> I have set the encoder output as KCDA210. Also, I have made changes in
>> the davinci_platform.c for VPBE module settings. In the boot arguments,
>> when I give the encoder manager output name as KCDA210, the system is
>> booting and working fine. If, I make any changes in the encoder file
>> that I have created, then the system is not booting. The system gets
>> hanged during the kernel un-compression. If I revert those changes back,
>> then the system is booting properly.
>>
>>
>>
>> For example, err |= i2c_write();
>>
>>
>>
>> If I make the change as err = i2c_write();, instead of ORing the output,
>> then the system gets hanged during the boot.
>>
>>
>>
>> I am not sure that the hanging is because of this change. But, if I
>> revert these changes back, the system works fine.
>>
>>
>>
>> Boot arguments that I am using,
>>
>> setenv bootargs console=ttyS0,115200n8 noinitrd rw
>> ip=10.100.135.51:10.100.135.126:10.100.135.1:255.255.255.0:::off
>> root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M
>> video=davincifb:vid0=720x576x16,2500K:vi

Help in writiing JFFS2 Filesystem into NAND /Uboot

2008-11-11 Thread Deepak Mundra

Hi,

Has any one tried writing jfss2 filesystem on to nand using uboot ???

I am using following stem but MTD->READ is returning error


1]nand erase 0x46 sizeof_filesystem_image

2]transfer jffs2 filsystem image to 0x8070

3]nand write 0x8070 0x46 sizeof_filesystem_image

4]In kernel i set boot args as follow


setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/mtdblock3 rw
init=/bin/sh noatime rootfstype=jffs2
setenv bootcmd 'nboot 0x8070 0 0x6;bootm'

ANd while booting i am getting  errors like MTD->READ, ECC error etc


Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Help needed in Loading UBL/U-BOOT on A fresh board

2008-11-09 Thread Deepak Mundra

Hi ,

 I am trying to bring up a new board.. can any 1 tel me from where can i
download a tool which will erase nor/nand through serial/UART ..I am using
Davinci DM6446 board ..

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Error in booting through Serial port using UART

2008-11-08 Thread Deepak Mundra

Hi i am trying to bring up the board using serial port /dev/ttyS1
i hav downlaoded dv-rbl_ubl tool from davinci mailing list .. and i am able
to read BOOTME message etc from davinci but it is failing in reading UBL
message Rboot->.. The error which i get is as follows.

Using port /dev/ttyS1 to connect to DaVinci- okay
Read 3000 bytes from: rboot.bin  - okay
Waiting for BOOTME message from Davinci (press key to stop) .. BOOTME-
okay
Sending ACK  - okay
Waiting for BEGIN message from Davinci  BEGIN- okay
Sending empty CRC table  - okay
Waiting for crc DONE message from DavinciDONE- okay
Sending rboot.bin- okay
Waiting for data DONE message from Davinci   DONE- okay
Waiting for UBL message from Davinci
Error: UBL message timed out, exiting


Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

resizer on dm6446 /ioctl segmentation fault

2008-11-04 Thread Deepak Mundra

Hi,
I m trying to run resizer demo on dm64X board.. i have edited demo
application accordingly.. but while running the code i am getting
segmentation fault in following  ioctl call


if (ioctl(rszfd, RSZ_S_PARAM, NULL) < 0)

(where rszfd=open("/dev/davinci_resizer","O_RDWR")

Thank you

Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: writing compiling executing arm-dsp hello world program

2008-10-23 Thread Deepak Mundra

Hi
I tried with that also ,but no luck.. Is there any hello world dsp side
source code ? and now i switched over to codec engine .. i am trying to edit
viddec_copy codec and use it in video_copy application provided in example
.. I just wanted to know 2 things ..

if i edit codecs/viddec_copy/viddec_copy.c file and make my new codec .. how
can i load this codec into DSP and how can i make apps/video_copy/
appliction to use it .. and second thing

how can i print

179 GT_1trace( curTrace, GT_2CLASS, "VIDDECCOPY_TI_process> "
180"Processed %d bytes.\n", minSamples );

statements present in viddec_copy.c .. how ca i enable debug prints.. i have
already posted about this please go trhough it


Thank you
Deepak


On Thu, Oct 23, 2008 at 9:10 PM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Can you also disable PROBE and try once more? PROBE is not supported
> anymore, and we have even removed it from the configurations in recent
> releases.
>
> Regards,
> Mugdha
>
>
>  --
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Kamoolkar,
> Mugdha
> *Sent:* Thursday, October 23, 2008 9:07 PM
> *To:* Deepak Mundra
> *Cc:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* RE: writing compiling executing arm-dsp hello world program
>
>  Deepak,
>
> You can try using DSPLink 1.51 if you want. That's the current latest GA
> release out there. But if you are going to use it with Codec Engine also,
> please be sure to pick up the correct Codec Engine version that is
> compatible with DSPLink 1.51 GA.
> The release is available at:
> https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html
>
> In DSPLink 1.60 (coming soon), we have made several fixes and enhancements
> to allow users to load and start DSP with a completely non-DSPLink DSP
> executable, i.e. use DSPLink simply as a DSP boot-loader, if the PROC-only
> configuration is used. This release will be available very soon (before the
> end of this month).
>
> Regards,
> Mugdha
>
>
>  --
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Thursday, October 23, 2008 5:08 PM
> *To:* Kamoolkar, Mugdha
> *Cc:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* Re: writing compiling executing arm-dsp hello world program
>
> HI in some site i found this
>
> 1.40.xx uses dynamic configuration ($(DSPLINK)/config/all/CFG_ instead of static configuration
> $(DSPLINK)/config/all/CFG_
> and im using 140-05 p1 version .. and there is no txt file in that
> directory , only .c file exist . and where can i find p2,p3,p4,p5 patch ..
> because i even found that 140-05P5 is present version..
> Thank you
>
> On Tue, Oct 21, 2008 at 5:02 PM, Deepak Mundra <[EMAIL PROTECTED]>wrote:
>
>> Hi
>> dsp link version is dsplink_140-05p1..
>>
>> The steps which i followed was
>>
>> 1]  cd dsplink/etc/host/scripts/Linux
>> ./dsplinkcfg
>>
>> The selected configuration is:
>>
>>   GPP OS = Linux
>>   DSP OS = DspBios
>>   GPPDISTRIBUTION= davinci_mvlpro4.0
>>   GPPOSVERSION   = 2.6
>>   DSPDISTRIBUTION= c64xxp_5.xx_linux
>>
>>   GPPPLATFORM= Davinci
>>   DSPPLATFORM= Davinci
>>
>>   USE_PROC   = 1
>>   USE_POOL   = 0
>>   USE_NOTIFY = 0
>>   USE_MPCS   = 0
>>   USE_RINGIO = 0
>>   USE_MPLIST = 0
>>   USE_CHNL   = 0
>>   USE_MSGQ   = 0
>>
>>   TRACE  = 0
>>   PROFILE= 0
>>   PROBE  = 1
>>
>>
>> 2] run sh -f buildmodule.sh
>> 3]cd packages/dsplink/gpp/src
>> 4] gmake -s  and also  cd  ackages/dsplink/gpp/src/sample/hello && gmake
>> -s
>>
>>
>> 5]cd ackages/dsplink/dsp/src && gmake -s but couldntnt buld samples
>> because i had only enabled PROC in build config
>>
>> so i did  cd hello && gmake -s
>>
>> 6] now copied gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko ,, hellogpp
>> and hello.out to board
>> 7] on board loaded modules ../loadmodules.sh
>> 8]./hellogpp hello.out
>>
>> NOw where am i missing that library link .. ? and
>>
>> i was not able to make packages/dsplink/dsp/src/data
>>
>> error was
>> /dsplink/dsp/src/data/dsplinkdata.h", line 94: error #20:
>>   identifier "DSPLINKDATA_CTRL_PADDING" is undefined
>>   Uint16 padding[DSPLINKDATA_CTRL_PADDING] ;
>>  ^
>

How can i print DSP/Debug prints in codecs ??

2008-10-23 Thread Deepak Mundra

Dear all,

 I a trying to work around with codecs and modify according to
my needs  .. I have compiled dsplink with
following options

  GPP OS = Linux
  DSP OS = DspBios
  GPPDISTRIBUTION= davinci_mvlpro4.0
  GPPOSVERSION   = 2.6
  DSPDISTRIBUTION= c64xxp_5.xx_linux

  GPPPLATFORM= Davinci
  DSPPLATFORM= Davinci

  USE_PROC   = 1
  USE_POOL   = 1
  USE_NOTIFY = 1
  USE_MPCS   = 1
  USE_RINGIO = 1
  USE_MPLIST = 1
  USE_CHNL   = 1
  USE_MSGQ   = 1

  TRACE  = 0
  PROFILE= 2
  PROBE  = 1


So my question is how can i print debug printfs from DSP .. lets say i have
changed

ti.sdo.ce.examples.codecs.viddec_copy

and i am using apps/video_copy/dualcpu/evdm6446 application..

I want to print somthing like this

[DSP] @0x014e:[T:0x] servers.video_copy.evmDM6446 - main>
Welcome to DSP server's main().

this output was from server/video_copy/video_copy.x64P file which same above
mentioned application uses...

but why below printf not printing  which was in
ti.sdo.ce.examples.codecs.viddec_copy.c file

179 GT_1trace( curTrace, GT_2CLASS, "VIDDECCOPY_TI_process> "
180"Processed %d bytes.\n", minSamples );


Thank you
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: writing compiling executing arm-dsp hello world program

2008-10-23 Thread Deepak Mundra

HI in some site i found this

1.40.xx uses dynamic configuration ($(DSPLINK)/config/all/CFG_wrote:

> Hi
> dsp link version is dsplink_140-05p1..
>
> The steps which i followed was
>
> 1]  cd dsplink/etc/host/scripts/Linux
> ./dsplinkcfg
>
> The selected configuration is:
>
>   GPP OS = Linux
>   DSP OS = DspBios
>   GPPDISTRIBUTION= davinci_mvlpro4.0
>   GPPOSVERSION   = 2.6
>   DSPDISTRIBUTION= c64xxp_5.xx_linux
>
>   GPPPLATFORM= Davinci
>   DSPPLATFORM= Davinci
>
>   USE_PROC   = 1
>   USE_POOL   = 0
>   USE_NOTIFY = 0
>   USE_MPCS   = 0
>   USE_RINGIO = 0
>   USE_MPLIST = 0
>   USE_CHNL   = 0
>   USE_MSGQ   = 0
>
>   TRACE  = 0
>   PROFILE= 0
>   PROBE  = 1
>
>
> 2] run sh -f buildmodule.sh
> 3]cd packages/dsplink/gpp/src
> 4] gmake -s  and also  cd  ackages/dsplink/gpp/src/sample/hello && gmake -s
>
>
> 5]cd ackages/dsplink/dsp/src && gmake -s but couldntnt buld samples because
> i had only enabled PROC in build config
>
> so i did  cd hello && gmake -s
>
> 6] now copied gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko ,, hellogpp
> and hello.out to board
> 7] on board loaded modules ../loadmodules.sh
> 8]./hellogpp hello.out
>
> NOw where am i missing that library link .. ? and
>
> i was not able to make packages/dsplink/dsp/src/data
>
> error was
> /dsplink/dsp/src/data/dsplinkdata.h", line 94: error #20:
>   identifier "DSPLINKDATA_CTRL_PADDING" is undefined
>   Uint16 padding[DSPLINKDATA_CTRL_PADDING] ;
>  ^
>
> 1 error detected in the compilation of "dsplinkdata.c".
>
> Thank you
>
> On Tue, Oct 21, 2008 at 4:13 PM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:
>
>>  Deepak,
>>
>> The first scenario seems valid. But DSP_ENOTFOUND error from
>> PROC_start indicates that DSPLink is not able to find a symbol it was
>> looking for. Have you linked in the re-built (in PROC-only mode) dsplink.lib
>> on DSP-side? Also, which version of DSPLink is this?
>>
>> The second scenario (NUM_ARGS 2) that you have given below is not valid if
>> you are still passing NULL to args. If you say number of arguments is 2, you
>> need to provide 2 arguments. Hence the DSP_EINVALIDARG error in PROC_load.
>>
>> Regards,
>> Mugdha
>>
>>
>>  --
>> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
>> *Sent:* Tuesday, October 21, 2008 3:57 PM
>>
>> *To:* Kamoolkar, Mugdha
>> *Cc:* davinci-linux-open-source@linux.davincidsp.com
>> *Subject:* Re: writing compiling executing arm-dsp hello world program
>>
>>  Hi thanks for the reply
>> enabled only proc and in hello.c file i have set
>>
>> #define NUM_ARGS 0 and using in PROC_Load as bellow
>>
>>  44if (DSP_SUCCEEDED(status)) {
>>  45   status = PROC_Load(ID_PROCESSOR, dspExecutable, NUM_ARGS, NULL);
>>  46   if (DSP_FAILED (status)) {
>>  47  printf("PROC_Load failed. Status: [0x%x]\n",
>> (unsigned)status);
>>  48   } else {
>>  49  printf("PROC_Load successful\n");
>>  50   }
>>  51   fflush(stdout);
>>  52}
>>
>>
>> then im getting following error
>>
>> 
>> Entered Hello_Create()
>> 
>> PROC_Setup successful
>> PROC_Attach successful
>> PROC_Load successful
>> PROC_Start failed. Status: [0x8000802d]
>> 
>> Leaving Hello_Create()
>> 
>> Create phase failed. Status: [0x8000802d]
>> 
>> Entered Hello_Delete()
>> 
>> PROC_Stop() failed (output). Status: [0x8000801b]
>> PROC_Detach() successful.
>> PROC_Destroy successful.
>> 
>> Leaving Hello_Delete()
>> 
>> 
>>
>>
>>
>>
>>
>> if i set  #define NUM_ARGS 2
>> i get different error
>>
>>
>>
>>
>> = Hello Tes

Re: writing compiling executing arm-dsp hello world program

2008-10-23 Thread Deepak Mundra

Hi , sorry for previous mail

I am not able to figure it out why it is not able to start PROC .. in code
composer my dsp binary running properly ..

After i inserted DEBUG version of dsplinkk.ko i got following extra
assertion error


Entered Hello_Create()

PROC_Setup successful
PROC_Attach successful
PROC_Load successful
PROC_Start failed. SAssertion failed ((procState->dspState ==
ProcState_Started) || (procState->dspState == ProcState_Stoppe
d) || (procState->dspState == ProcState_Idle)). File : ldrv_proc.c Line :
548
tatus: [0x8000802d]

Leaving Hello_Create()

Create phase failed. Status: [0x8000802d]

Entered Hello_Delete()

PROC_Stop() failed (output). Status: [0x8000801b]
PROC_Detach() successful.
PROC_Destroy successful.

Leaving Hello_Delete()



Thank you
Deepak

On Thu, Oct 23, 2008 at 9:14 AM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Deepak,
>
> Looping in open-source list ...
>
> It is best to write to open-source list for all such questions. Please do
> not write directly to any person on the list. It is generally frowned upon,
> since usually all the people on the list do not have the bandwidth for
> personal support.
>
> Regards,
> Mugdha
>
>
>  --
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, October 22, 2008 7:47 PM
> *To:* Kamoolkar, Mugdha
>
> *Subject:* Re: writing compiling executing arm-dsp hello world program
>
>
> Hi Mugdha,
>   I am trying to implement or run blit function on dsp (provided by
> directfb ) .. so i am working on it .. directfb people havnt released
> hardware accelerated driver for davinci yet .. So can you give me some hint
> how can i start with
>
> Thanks
> Deepak
> On Tue, Oct 21, 2008 at 4:13 PM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:
>
>>  Deepak,
>>
>> The first scenario seems valid. But DSP_ENOTFOUND error from
>> PROC_start indicates that DSPLink is not able to find a symbol it was
>> looking for. Have you linked in the re-built (in PROC-only mode) dsplink.lib
>> on DSP-side? Also, which version of DSPLink is this?
>>
>> The second scenario (NUM_ARGS 2) that you have given below is not valid if
>> you are still passing NULL to args. If you say number of arguments is 2, you
>> need to provide 2 arguments. Hence the DSP_EINVALIDARG error in PROC_load.
>>
>> Regards,
>> Mugdha
>>
>>
>>  --
>>  *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
>> *Sent:* Tuesday, October 21, 2008 3:57 PM
>>
>> *To:* Kamoolkar, Mugdha
>> *Cc:* davinci-linux-open-source@linux.davincidsp.com
>> *Subject:* Re: writing compiling executing arm-dsp hello world program
>>
>>   Hi thanks for the reply
>> enabled only proc and in hello.c file i have set
>>
>> #define NUM_ARGS 0 and using in PROC_Load as bellow
>>
>>  44if (DSP_SUCCEEDED(status)) {
>>  45   status = PROC_Load(ID_PROCESSOR, dspExecutable, NUM_ARGS, NULL);
>>  46   if (DSP_FAILED (status)) {
>>  47  printf("PROC_Load failed. Status: [0x%x]\n",
>> (unsigned)status);
>>  48   } else {
>>  49  printf("PROC_Load successful\n");
>>  50   }
>>  51   fflush(stdout);
>>  52}
>>
>>
>> then im getting following error
>>
>> 
>> Entered Hello_Create()
>> 
>> PROC_Setup successful
>> PROC_Attach successful
>> PROC_Load successful
>> PROC_Start failed. Status: [0x8000802d]
>> 
>> Leaving Hello_Create()
>> 
>> Create phase failed. Status: [0x8000802d]
>> 
>> Entered Hello_Delete()
>> 
>> PROC_Stop() failed (output). Status: [0x8000801b]
>> PROC_Detach() successful.
>> PROC_Destroy successful.
>> =

Re: writing compiling executing arm-dsp hello world program

2008-10-21 Thread Deepak Mundra

Hi
dsp link version is dsplink_140-05p1..

The steps which i followed was

1]  cd dsplink/etc/host/scripts/Linux
./dsplinkcfg

The selected configuration is:

  GPP OS = Linux
  DSP OS = DspBios
  GPPDISTRIBUTION= davinci_mvlpro4.0
  GPPOSVERSION   = 2.6
  DSPDISTRIBUTION= c64xxp_5.xx_linux

  GPPPLATFORM= Davinci
  DSPPLATFORM= Davinci

  USE_PROC   = 1
  USE_POOL   = 0
  USE_NOTIFY = 0
  USE_MPCS   = 0
  USE_RINGIO = 0
  USE_MPLIST = 0
  USE_CHNL   = 0
  USE_MSGQ   = 0

  TRACE  = 0
  PROFILE= 0
  PROBE  = 1


2] run sh -f buildmodule.sh
3]cd packages/dsplink/gpp/src
4] gmake -s  and also  cd  ackages/dsplink/gpp/src/sample/hello && gmake -s


5]cd ackages/dsplink/dsp/src && gmake -s but couldntnt buld samples because
i had only enabled PROC in build config

so i did  cd hello && gmake -s

6] now copied gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko ,, hellogpp
and hello.out to board
7] on board loaded modules ../loadmodules.sh
8]./hellogpp hello.out

NOw where am i missing that library link .. ? and

i was not able to make packages/dsplink/dsp/src/data

error was
/dsplink/dsp/src/data/dsplinkdata.h", line 94: error #20:
  identifier "DSPLINKDATA_CTRL_PADDING" is undefined
  Uint16 padding[DSPLINKDATA_CTRL_PADDING] ;
 ^

1 error detected in the compilation of "dsplinkdata.c".

Thank you
On Tue, Oct 21, 2008 at 4:13 PM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Deepak,
>
> The first scenario seems valid. But DSP_ENOTFOUND error from
> PROC_start indicates that DSPLink is not able to find a symbol it was
> looking for. Have you linked in the re-built (in PROC-only mode) dsplink.lib
> on DSP-side? Also, which version of DSPLink is this?
>
> The second scenario (NUM_ARGS 2) that you have given below is not valid if
> you are still passing NULL to args. If you say number of arguments is 2, you
> need to provide 2 arguments. Hence the DSP_EINVALIDARG error in PROC_load.
>
> Regards,
> Mugdha
>
>
>  --
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, October 21, 2008 3:57 PM
>
> *To:* Kamoolkar, Mugdha
> *Cc:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* Re: writing compiling executing arm-dsp hello world program
>
>  Hi thanks for the reply
> enabled only proc and in hello.c file i have set
>
> #define NUM_ARGS 0 and using in PROC_Load as bellow
>
>  44if (DSP_SUCCEEDED(status)) {
>  45   status = PROC_Load(ID_PROCESSOR, dspExecutable, NUM_ARGS, NULL);
>  46   if (DSP_FAILED (status)) {
>  47  printf("PROC_Load failed. Status: [0x%x]\n",
> (unsigned)status);
>  48   } else {
>  49  printf("PROC_Load successful\n");
>  50   }
>  51   fflush(stdout);
>  52}
>
>
> then im getting following error
>
> 
> Entered Hello_Create()
> 
> PROC_Setup successful
> PROC_Attach successful
> PROC_Load successful
> PROC_Start failed. Status: [0x8000802d]
> 
> Leaving Hello_Create()
> 
> Create phase failed. Status: [0x8000802d]
> 
> Entered Hello_Delete()
> 
> PROC_Stop() failed (output). Status: [0x8000801b]
> PROC_Detach() successful.
> PROC_Destroy successful.
> 
> Leaving Hello_Delete()
> 
> 
>
>
>
>
>
> if i set  #define NUM_ARGS 2
> i get different error
>
>
>
>
> = Hello Test ==
>
> 
> Entered Hello_Create()
> 
> PROC_Setup successful
> PROC_Attach successful
> PROC_Load failed. Status: [0x8000800b]
> 
> Leaving Hello_Create()
> 
> Create phase failed. Status: [0x8000800b]
> 
> Entered Hello_Delete()
> 
> PROC_Stop() failed (output). Status: [0x8000801b]
&g

Re: writing compiling executing arm-dsp hello world program

2008-10-21 Thread Deepak Mundra

Hi thanks for the reply
enabled only proc and in hello.c file i have set

#define NUM_ARGS 0 and using in PROC_Load as bellow

 44if (DSP_SUCCEEDED(status)) {
 45   status = PROC_Load(ID_PROCESSOR, dspExecutable, NUM_ARGS, NULL);
 46   if (DSP_FAILED (status)) {
 47  printf("PROC_Load failed. Status: [0x%x]\n", (unsigned)status);
 48   } else {
 49  printf("PROC_Load successful\n");
 50   }
 51   fflush(stdout);
 52}


then im getting following error


Entered Hello_Create()

PROC_Setup successful
PROC_Attach successful
PROC_Load successful
PROC_Start failed. Status: [0x8000802d]

Leaving Hello_Create()

Create phase failed. Status: [0x8000802d]

Entered Hello_Delete()

PROC_Stop() failed (output). Status: [0x8000801b]
PROC_Detach() successful.
PROC_Destroy successful.

Leaving Hello_Delete()







if i set  #define NUM_ARGS 2
i get different error




= Hello Test ==


Entered Hello_Create()

PROC_Setup successful
PROC_Attach successful
PROC_Load failed. Status: [0x8000800b]

Leaving Hello_Create()

Create phase failed. Status: [0x8000800b]

Entered Hello_Delete()

PROC_Stop() failed (output). Status: [0x8000801b]
PROC_Detach() successful.
PROC_Destroy successful.

Leaving Hello_Delete()






On Tue, Oct 21, 2008 at 3:05 PM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Deepak,
>
> Please look through DSP/BIOS documentation on POOL module to see how POOL
> instances must be created in BIOS. Also, you can use DSPLink sample
> applications as reference:
> E.g.: /dsplink/dsp/src/samples/message/message_config.c
> static POOL_Obj pools [NUM_POOLS] =
> {
> {
> &SAMPLEPOOL_init,   /* Init
> Function  */
> (POOL_Fxns *) &SAMPLEPOOL_FXNS, /* Pool interface
> functions   */
> SAMPLEPOOL_PARAMS,  /* Pool
> params*/
> NULL/* Pool object: Set within pool
> impl. */
> }
> } ;
> This sets up the POOL. Also look at definitions of SAMPLEPOOL_init,
> SAMPLEPOOL_PARAMS as defined in message_config.c and do a similar thing for
> your application.
> This configuration was not detailed at the web-site you have mentioned, so
> that's why you probably missed it.
>
> If you do not need POOL and want a simple hello world program, you can just
> enable only PROC module in configuration and try out. If you do that the
> POOL configuration is not required, and POOL related error will not be seen.
>
> Regards,
> Mugdha
>
>
>  --
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, October 21, 2008 2:30 PM
>
> *To:* Kamoolkar, Mugdha
> *Cc:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* Re: writing compiling executing arm-dsp hello world program
>
>  Hi .. As mentioned in the site .. i compiled both dsp and gpp side .. and
> copied hellogpp and hello.out to board and also
> dsplink/gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko Using
> loadmodules.sh inserted and ran "./hellogpp hello.out " .. but as i
> mentioned in another mail .. im getting error at POOL CONFIG ..
>
>   The selected configuration is:
>
>   GPP OS = Linux
>   DSP OS = DspBios
>   GPPDISTRIBUTION= davinci_mvlpro4.0
>   GPPOSVERSION   = 2.6
>   DSPDISTRIBUTION= c64xxp_5.xx_linux
>
>   GPPPLATFORM= Davinci
>   DSPPLATFORM= Davinci
>
>   USE_PROC   = 1
>   USE_POOL   = 1
>   USE_NOTIFY = 1
>   USE_MPCS   = 1
>   USE_RINGIO = 1
>   USE_MPLIST = 1
>   USE_CHNL   = 1
>   USE_MSGQ

Re: writing compiling executing arm-dsp hello world program

2008-10-21 Thread Deepak Mundra

Hi .. As mentioned in the site .. i compiled both dsp and gpp side .. and
copied hellogpp and hello.out to board and also
dsplink/gpp/export/BIN/Linux/Davinci/RELEASE/dsplinkk.ko Using
loadmodules.sh inserted and ran "./hellogpp hello.out " .. but as i
mentioned in another mail .. im getting error at POOL CONFIG ..

  The selected configuration is:

  GPP OS = Linux
  DSP OS = DspBios
  GPPDISTRIBUTION= davinci_mvlpro4.0
  GPPOSVERSION   = 2.6
  DSPDISTRIBUTION= c64xxp_5.xx_linux

  GPPPLATFORM= Davinci
  DSPPLATFORM= Davinci

  USE_PROC   = 1
  USE_POOL   = 1
  USE_NOTIFY = 1
  USE_MPCS   = 1
  USE_RINGIO = 1
  USE_MPLIST = 1
  USE_CHNL   = 1
  USE_MSGQ   = 1

  TRACE  = 0
  PROFILE= 0
  PROBE  = 1

Am i missing anything ..

Thank you

On Tue, Oct 21, 2008 at 11:41 AM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  You can rebuild DSP-side:
> http://tiexpressdsp.com/wiki/index.php?title=Building_DSPLink
>
> Regards,
> Mugdha
>
>
>  ------
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, October 21, 2008 11:38 AM
> *To:* Kamoolkar, Mugdha
> *Cc:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* Re: writing compiling executing arm-dsp hello world program
>
>  Thanks for the reply ...
>
> DSP-side configuration mismatch/failure
> 0  -> success
> Positive value -> DSP-side failure code.
> (Uint32) -1-> DSP-side component was not initialized.
>
> DRV configuration status[0x0]
> IPS configuration status[0x0]
> POOL configuration status   [0x0]
> MPCS configuration status   [0x0]
> MPLIST configuration status [0x0]
> MQT configuration status[0x0]
> DATA configuration status   [0x]
> RINGIO configuration status [0x0]
>
>
> Now that makes sense after reading the trouble shooting guide .. this means
> DSP side i havnt enable CHNL option .. Because in GPP SIDE I have enabled
> it.. one thing which i can try is disabling in gpp
>
> using dsplinkcfg script
>
>
> But what about DSP side ? how can i enable it (or rebuild dsp)
>
> Thank you
>
> Deepak
> On Tue, Oct 21, 2008 at 9:31 AM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:
>
>>  Deepak,
>>
>> What error did you get while running?
>> Have you looked at this to see if your error matches any of the ones
>> listed here:
>>
>> http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues
>>
>> Regards,
>> Mugdha
>>
>>
>>  --
>> *From:* [EMAIL PROTECTED] [mailto:
>> [EMAIL PROTECTED] *On Behalf Of *Deepak
>> Mundra
>> *Sent:* Monday, October 20, 2008 6:13 PM
>> *To:* davinci-linux-open-source@linux.davincidsp.com
>> *Subject:* writing compiling executing arm-dsp hello world program
>>
>>   Dear all
>>
>> I have i am trying to run a arm-dsp hello world program .. when i was
>> searching i found the following link .. in which the author has written both
>> arm side and dsp side code ..
>>
>> http://www.dsprelated.com/groups/c6x/show/10556.php
>>
>> But my problem is how to compile these ? i have all tools required for
>> compilation.. i have also tried changing make files of sample dsplink codes
>> and also succeeded :) but got error while running ..So want detailed easy
>> step to compile this ..Please can any one guide me in this..
>>
>> Thanks
>> Deepak
>>
>
>
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: writing compiling executing arm-dsp hello world program

2008-10-21 Thread Deepak Mundra

Hi this code is to print hello world ..

= Hello Test ==


Entered Hello_Create()

PROC_Setup successful
PROC_Attach successful
PROC_Load successful
DSP-side configuration mismatch/failure
0  -> success
Positive value -> DSP-side failure code.
(Uint32) -1-> DSP-side component was not initialized.

DRV configuration status[0x0]
IPS configuration status[0x0]
POOL configuration status   [0x]
MPCS configuration status   [0x0]
MPLIST configuration status [0x0]
MQT configuration status[0x0]
RINGIO configuration status [0x0]


>From the output i can tel that POOL config is not enabled(in DSP ?? or GPP
??)
how can i Enable it . and what is the easy step to compile this hellogpp and
hello.out ..presently im using edited make file of sample source ..

Thank you...


On Tue, Oct 21, 2008 at 9:31 AM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Deepak,
>
> What error did you get while running?
> Have you looked at this to see if your error matches any of the ones listed
> here:
>
> http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues
>
> Regards,
> Mugdha
>
>
>  --
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Deepak
> Mundra
> *Sent:* Monday, October 20, 2008 6:13 PM
> *To:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* writing compiling executing arm-dsp hello world program
>
>  Dear all
>
> I have i am trying to run a arm-dsp hello world program .. when i was
> searching i found the following link .. in which the author has written both
> arm side and dsp side code ..
>
> http://www.dsprelated.com/groups/c6x/show/10556.php
>
> But my problem is how to compile these ? i have all tools required for
> compilation.. i have also tried changing make files of sample dsplink codes
> and also succeeded :) but got error while running ..So want detailed easy
> step to compile this ..Please can any one guide me in this..
>
> Thanks
> Deepak
>
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: writing compiling executing arm-dsp hello world program

2008-10-20 Thread Deepak Mundra

Thanks for the reply ...

DSP-side configuration mismatch/failure
0  -> success
Positive value -> DSP-side failure code.
(Uint32) -1-> DSP-side component was not initialized.

DRV configuration status[0x0]
IPS configuration status[0x0]
POOL configuration status   [0x0]
MPCS configuration status   [0x0]
MPLIST configuration status [0x0]
MQT configuration status[0x0]
DATA configuration status   [0x]
RINGIO configuration status [0x0]


Now that makes sense after reading the trouble shooting guide .. this means
DSP side i havnt enable CHNL option .. Because in GPP SIDE I have enabled
it.. one thing which i can try is disabling in gpp

using dsplinkcfg script


But what about DSP side ? how can i enable it (or rebuild dsp)

Thank you

Deepak
On Tue, Oct 21, 2008 at 9:31 AM, Kamoolkar, Mugdha <[EMAIL PROTECTED]> wrote:

>  Deepak,
>
> What error did you get while running?
> Have you looked at this to see if your error matches any of the ones listed
> here:
>
> http://tiexpressdsp.com/wiki/index.php?title=Troubleshooting_DSPLink_configuration_issues
>
> Regards,
> Mugdha
>
>
>  --
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Deepak
> Mundra
> *Sent:* Monday, October 20, 2008 6:13 PM
> *To:* davinci-linux-open-source@linux.davincidsp.com
> *Subject:* writing compiling executing arm-dsp hello world program
>
>  Dear all
>
> I have i am trying to run a arm-dsp hello world program .. when i was
> searching i found the following link .. in which the author has written both
> arm side and dsp side code ..
>
> http://www.dsprelated.com/groups/c6x/show/10556.php
>
> But my problem is how to compile these ? i have all tools required for
> compilation.. i have also tried changing make files of sample dsplink codes
> and also succeeded :) but got error while running ..So want detailed easy
> step to compile this ..Please can any one guide me in this..
>
> Thanks
> Deepak
>
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

writing compiling executing arm-dsp hello world program

2008-10-20 Thread Deepak Mundra

Dear all

I have i am trying to run a arm-dsp hello world program .. when i was
searching i found the following link .. in which the author has written both
arm side and dsp side code ..

http://www.dsprelated.com/groups/c6x/show/10556.php

But my problem is how to compile these ? i have all tools required for
compilation.. i have also tried changing make files of sample dsplink codes
and also succeeded :) but got error while running ..So want detailed easy
step to compile this ..Please can any one guide me in this..

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: DirectFB On DVM6446

2008-10-16 Thread Deepak Mundra

Ya even i could compilec64x.ko ..  I had to apply some patches etc ..
problem is with that .bin file .. :(

Anyways if u find any thing related to this please inform
Thanks

2008/10/17 Soohyung Cho <[EMAIL PROTECTED]>

> I could compile and get the c64x.ko.
> But the real problem is there's no c64x_drv.bin(DSP firmware ?).
> When c64x.ko is loaded into kernel space, it try to open a
> c64x_drv.bin and stop being loaded.
> Look DirectFB/gfxdrivers/davinci/kernel-module/c64x/c64x.c.
> I couldn't find source codes or a binary for a c64x_drv.bin anywhere.
>
>
> 2008/10/16 Deepak Mundra <[EMAIL PROTECTED]>:
> > Hi any1 found solution for enabling hardware acceleration for directfb
> ???
> >
> > Thanks
> >
> > On Thu, Sep 4, 2008 at 8:19 PM, Paul Stuart <[EMAIL PROTECTED]>
> > wrote:
> >>
> >> Can't help you with that one. I'm using this on the dm355 so I have a
> >> stripped down version of the driver. /dev/c64 isn't in my world-view…
> >>
> >> I have seen quite a bit of chatter about the problem you are having, so
> I
> >> suspect some searching will turn up an answer.
> >>
> >>
> >>
> >> 
> >>
> >> From: Deepak Mundra [mailto:[EMAIL PROTECTED]
> >> Sent: Wednesday, September 03, 2008 10:22 PM
> >> To: Paul Stuart
> >> Cc: [EMAIL PROTECTED]; Albert Burbea;
> >> davinci-linux-open-source@linux.davincidsp.com
> >>
> >> Subject: Re: DirectFB On DVM6446
> >>
> >>
> >>
> >> Thax for the directfbrc info,  just wanted to know r u able to open
> >> /dev/c64x ??? for me its giving warning telling no such device or
> address ..
> >> but the device file is there in /dev directory .. directfb people told i
> >> need c64x.ko module which i am not able to compile :(
> >>
> >> Thanks
> >>
> >> On Wed, Sep 3, 2008 at 10:38 PM, Paul Stuart <[EMAIL PROTECTED]>
> >> wrote:
> >>
> >> For the 6446 you should use --with-gfx-drivers=davinci
> >>
> >> The other, not well documented item that is essential for making it
> work,
> >> is the directfbrc file that directfb loads at runtime. To explicitly use
> the
> >> davinci driver, the directfbrc file needs to have:
> >>
> >> system=devmem
> >> video-phys=8700
> >> video-length=
> >> accelerator = 6400
> >>
> >> The "accelerator = 6400" is the magic in this case for making it load
> the
> >> Davinci driver without probing
> >>
> >> This is going to create another set of woes for you, but at least you'll
> >> be using the davinci driver :)
> >>
> >> paul
> >>
> >> -Original Message-
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On
> Behalf Of
> >> Lloyd Sargent
> >> Sent: Wednesday, September 03, 2008 9:38 AM
> >> To: Albert Burbea
> >> Cc: davinci-linux-open-source@linux.davincidsp.com
> >> Subject: Re: DirectFB On DVM6446
> >>
> >> On Wednesday 03 September 2008 02:13, you wrote:
> >> > Hi Lloyd
> >> > could you please tell us how ?
> >> > And how do u use it ?
> >> > Albert
> >>
> >> ./configure  --disable-sdl --with-gfxdrivers=none --disable-mmx
> >> --disable-vnc
> >>
> >> Give this a shot and let me know if you run into problems. It has been
> >> several
> >> years since I built it on the Davinci...
> >>
> >> Cheers,
> >>
> >> Lloyd
> >>
> >> ___
> >> 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

Re: DirectFB On DVM6446

2008-10-16 Thread Deepak Mundra

Hi any1 found solution for enabling hardware acceleration for directfb ???

Thanks

On Thu, Sep 4, 2008 at 8:19 PM, Paul Stuart <[EMAIL PROTECTED]>wrote:

>  Can't help you with that one. I'm using this on the dm355 so I have a
> stripped down version of the driver. /dev/c64 isn't in my world-view…
>
> I have seen quite a bit of chatter about the problem you are having, so I
> suspect some searching will turn up an answer.
>
>
>  ------
>
> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, September 03, 2008 10:22 PM
> *To:* Paul Stuart
> *Cc:* [EMAIL PROTECTED]; Albert Burbea;
> davinci-linux-open-source@linux.davincidsp.com
>
> *Subject:* Re: DirectFB On DVM6446
>
>
>
> Thax for the directfbrc info,  just wanted to know r u able to open
> /dev/c64x ??? for me its giving warning telling no such device or address ..
> but the device file is there in /dev directory .. directfb people told i
> need c64x.ko module which i am not able to compile :(
>
> Thanks
>
> On Wed, Sep 3, 2008 at 10:38 PM, Paul Stuart <[EMAIL PROTECTED]>
> wrote:
>
> For the 6446 you should use --with-gfx-drivers=davinci
>
> The other, not well documented item that is essential for making it work,
> is the directfbrc file that directfb loads at runtime. To explicitly use the
> davinci driver, the directfbrc file needs to have:
>
> system=devmem
> video-phys=8700
> video-length=
> accelerator = 6400
>
> The "accelerator = 6400" is the magic in this case for making it load the
> Davinci driver without probing
>
> This is going to create another set of woes for you, but at least you'll be
> using the davinci driver :)
>
> paul
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Lloyd
> Sargent
> Sent: Wednesday, September 03, 2008 9:38 AM
> To: Albert Burbea
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: DirectFB On DVM6446
>
> On Wednesday 03 September 2008 02:13, you wrote:
> > Hi Lloyd
> > could you please tell us how ?
> > And how do u use it ?
> > Albert
>
> ./configure  --disable-sdl --with-gfxdrivers=none --disable-mmx
> --disable-vnc
>
> Give this a shot and let me know if you run into problems. It has been
> several
> years since I built it on the Davinci...
>
> Cheers,
>
> Lloyd
>
> ___
> 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

Can't determine sensor slave IDs when connecting web cam t

2008-10-14 Thread Deepak Mundra

Hi

  I am using 64xx board with 2.6.26 kernel ... I have compiled ov51x-jpeg
driver for my camera.. it is detecting the camera ..even camera led glows ..
buta it fails to initialize..

dmesg is as follows .. please help

usb 1-1: new full speed USB device using musb_hdrc and address 12
usb 1-1: configuration #1 chosen from 1 choice
ov51x_jpeg: USB OV519 video device found
ov51x_jpeg: Can't determine sensor slave IDs
ov51x_jpeg: OV519 Config failed
ov51x_jpeg: Camera initialization failed
ov51x: probe of 1-1:1.0 failed with error -5

Thanks
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

v4l2-common.h file not found

2008-10-10 Thread Deepak Mundra

Hi everybody ..
I am using 2.6.10 kernel and trying to compile one driver module  ..
i am able to enable v4l2 option in config also ..
But the problem is when i make driver module it gives error telling that
media/v4l2-common.h no such file ... even manually i searched that file but
no luck .. please help me in solving this

Thanks
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

c64x_drv.bin file ???

2008-09-09 Thread Deepak Mundra

Hi how or where can i get c64x_drv.bin firmaware module for davainci ?

I have compiled c64x.ko module but while inserting it is asking for that bin
file ..

Thank you
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

problem booting with kernel 2.6.23 and 2.6.26 on dm644x

2008-09-08 Thread Deepak Mundra

Hi i am trying to compile 2.6.23 and 2.6.26(presently using 2.6.10 , which
is working fine)  with first one im getting stuck after Uncompressing kernal
image

 Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing
Linux.
.. done, booting the kernel.


and with 26 kernel im getting following error

Starting kernel ...

Uncompressing
Linux...
done, boo
ting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0356).

Available machine support:

ID (hex)NAME
0385DaVinci EVM

Please check your kernel config and/or bootloader.

please help me


commands which i used

make ARCH=arm CROSS_COMPILE=arm_v5t_le-  davinci_evm_dm644x_defconfig
make ARCH=arm CROSS_COMPILE=arm_v5t_le-  uImage

Thanks
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Re: DirectFB On DVM6446

2008-09-04 Thread Deepak Mundra

2008/9/5 Mat Laibowitz <[EMAIL PROTECTED]>

> Hi. Thanks for the info in this thread.
> I am also trying to get directfb running.
> I can configure it, compile it, and install it.
>
> But it always says that there is no system found when i try to run it.
> As in:
>  # dfbinfo
> --dfb:system=devmem,video-phys=0x8300,video-length=691200,accelerator=6400
>
>~~| DirectFB 1.2.3 |~~
> (c) 2001-2008  The world wide DirectFB Open Source Community
> (c) 2000-2004  Convergence (integrated media) GmbH
>   
>
> (*) DirectFB/Core: Single Application Core. (2008-09-05 00:06)
> (!) DirectFB/core/system: No system found!
> (#) DirectFBError [DirectFBCreate() failed]: No (suitable) implementation
> found!
> ~ #
>
If you have cross compiled directfb with prefix in host machine ,you will
find Directfb-1.2.3 directory in your $prefix/lib/directory ..so when you
run directfb it will look for sytem,gfxdriver etc in this path .. so One
solution can be this one

copy $prefix/lib/Directfb-1.2.3 directory to board and make sure even board
has same $prefix path ... i mean... let say i have cross compiled Directfb
on host machine with prefix=/opt/my_directfb

then from host machine copy /opt/my_directfb/lib/Directfb-1.2.3 folder to
boards /opt/my_directfb/lib directory (you can create this directory if
doesent exit in board)

I know there must me another solution.. But for time being you can try this
:)

Regards
Deepak


>
> I have also compiled c64x.ko, but I would be okay first just getting it to
> run at all. The basic framebuffers are working at /dev/fb0 etc.
> I am using kernel 2.6.22 on a custom board but it has dvevm software ported
> to it (only v1.10 right now).
>

Nice to hear that you have compiled c64x.ko if everything goes fine i
request you to guide me through that compilation .. cause i am still not
able to compile it :(



>
>
> I have a directfbrc file at /etc (and several other places) on the target
> but I don't think it gets parsed.
>


Ok first thing you copy directfbrc file to $home/.directfbrc let say if you
are root then
/root/.directfbrc .. please notice that  . (dot) is required here. and in
directfbrc file make sure
system, video-phys etc are not commented ..


>
>
> Any thoughts about getting the 'system' found? It should be there, it all
> compiled and installed without error.
>
> Thanks,
> -mat
>
> 2008/9/4 Paul Stuart <[EMAIL PROTECTED]>
>
>   Can't help you with that one. I'm using this on the dm355 so I have a
>> stripped down version of the driver. /dev/c64 isn't in my world-view…
>>
>> I have seen quite a bit of chatter about the problem you are having, so I
>> suspect some searching will turn up an answer.
>>
>>
>>  --
>>
>> *From:* Deepak Mundra [mailto:[EMAIL PROTECTED]
>> *Sent:* Wednesday, September 03, 2008 10:22 PM
>> *To:* Paul Stuart
>> *Cc:* [EMAIL PROTECTED]; Albert Burbea;
>> davinci-linux-open-source@linux.davincidsp.com
>>
>> *Subject:* Re: DirectFB On DVM6446
>>
>>
>>
>> Thax for the directfbrc info,  just wanted to know r u able to open
>> /dev/c64x ??? for me its giving warning telling no such device or address ..
>> but the device file is there in /dev directory .. directfb people told i
>> need c64x.ko module which i am not able to compile :(
>>
>> Thanks
>>
>> On Wed, Sep 3, 2008 at 10:38 PM, Paul Stuart <[EMAIL PROTECTED]>
>> wrote:
>>
>> For the 6446 you should use --with-gfx-drivers=davinci
>>
>> The other, not well documented item that is essential for making it work,
>> is the directfbrc file that directfb loads at runtime. To explicitly use the
>> davinci driver, the directfbrc file needs to have:
>>
>> system=devmem
>> video-phys=8700
>> video-length=
>> accelerator = 6400
>>
>> The "accelerator = 6400" is the magic in this case for making it load the
>> Davinci driver without probing
>>
>> This is going to create another set of woes for you, but at least you'll
>> be using the davinci driver :)
>>
>> paul
>>
>>
>>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:
>> [EMAIL PROTECTED] On Behalf Of
>> Lloyd Sargent
>> Sent: Wednesday, September 03, 2008 9:38 AM
>> To: Albert Burbea
>> Cc: davinci-linux-open-source@linux.davincidsp.com
>> Subject: Re: DirectFB On DVM6446
>>
>> On Wednesday 03 September 2008 02:13, you wrote:
>> &

Re: DirectFB On DVM6446

2008-09-03 Thread Deepak Mundra

Thax for the directfbrc info,  just wanted to know r u able to open
/dev/c64x ??? for me its giving warning telling no such device or address ..
but the device file is there in /dev directory .. directfb people told i
need c64x.ko module which i am not able to compile :(

Thanks

On Wed, Sep 3, 2008 at 10:38 PM, Paul Stuart <[EMAIL PROTECTED]>wrote:

> For the 6446 you should use --with-gfx-drivers=davinci
>
> The other, not well documented item that is essential for making it work,
> is the directfbrc file that directfb loads at runtime. To explicitly use the
> davinci driver, the directfbrc file needs to have:
>
> system=devmem
> video-phys=8700
> video-length=
> accelerator = 6400
>
> The "accelerator = 6400" is the magic in this case for making it load the
> Davinci driver without probing
>
> This is going to create another set of woes for you, but at least you'll be
> using the davinci driver :)
>
> paul
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Lloyd
> Sargent
> Sent: Wednesday, September 03, 2008 9:38 AM
> To: Albert Burbea
> Cc: davinci-linux-open-source@linux.davincidsp.com
> Subject: Re: DirectFB On DVM6446
>
> On Wednesday 03 September 2008 02:13, you wrote:
> > Hi Lloyd
> > could you please tell us how ?
> > And how do u use it ?
> > Albert
>
> ./configure  --disable-sdl --with-gfxdrivers=none --disable-mmx
> --disable-vnc
>
> Give this a shot and let me know if you run into problems. It has been
> several
> years since I built it on the Davinci...
>
> Cheers,
>
> Lloyd
>
> ___
> 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

Re: DirectFB On DVM6446

2008-09-03 Thread Deepak Mundra

Hi i have cross compiled directfb for davinci DVM644
 so before that you need freetype , libpng,sdl (in case if you require ) to
be cross compiled

SO first export PATH=Toolchain path
export LIBPNG_CONFIG=cross compiled libpng config path
export SDL_CONFIG=cross compiled sdl config path
export FREETYPE_CONFIG=cros compiled freetype config path
export LD_LIBRARY_PATH=/toolchainpath/usr/lib:/$prefix/lib
export
PKG_CONFIG_PATH=/toolchainpath/usr/lib/pkgconfig:/$prefix/lib/pkgconfig

and configure

./configure --host=arm-linux --prefix=/opt/directfb --enable-shared
--disable-static --enable-sdl  --disable-jpeg --disable-x11 --disable-osx
--without-tests --with-tools
--with-gfxdrivers=ati128,cle266,cyber5k,davinci,ep9x,i810,i830,mach64,neomagic,nsc,nvidia,radeon,savage,sh7722,sis315,tdfx,unichrome,vmware

and finaly make and make install

But still not able to use graphics accelerator with davinci_gfx driver :(
.. working on that to

Regards
DEEPAK


2008/9/3 Albert Burbea <[EMAIL PROTECTED]>

> Hi Lloyd
> could you please tell us how ?
> And how do u use it ?
> Albert
>
>
> On 9/2/08, Lloyd Sargent <[EMAIL PROTECTED]> wrote:
>>
>> On Sunday 31 August 2008 10:44, Paul Stuart wrote:
>> > Anyway, you mentioned that you compiled it on the board. Is that
>> > correct, or did you cross compile it? The reason I ask is it's probably
>> > "just" a path issue. Does LD_LIBRARY_PATH contain the directory you've
>> > installed directFB into?
>>
>> I agree, this sounds like a simple path issue. I have built directFB on
>> the
>> Davinci (not cross-compiled) and it just works - if the paths are set
>> correctly. Otherwise you get complaints about missing libraries.
>>
>> Cheers,
>>
>> Lloyd
>>
>> ___
>> Davinci-linux-open-source mailing list
>> Davinci-linux-open-source@linux.davincidsp.com
>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>>
>
>
>
> --
> Albert Burbea
> Harishonim 8
> Ramat Gan 52502, Israel
> Tel/Fax + 972-3-7526016
> Mobile: +972-52-3541842
> ___
> 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

compiling c64x.ko for directfb 1.2.0

2008-09-02 Thread Deepak Mundra

Hi i am running directfb on davinci 64xx ..

I am trying to open /dev/c64x but it is giving following error

opening '/dev/c64x' failed--> No such device or address


I went through directfb mailing list and  found that i need c64x.ko  which
can be compiled using makefile.kernal in kernal module of gfxdriver/davinci/
but i got following error

In file included from
/path_to_src/DirectFB-1.2.0/gfxdrivers/davinci/kernel-module/c64x/c64x.c:31:
include/linux/cdev.h:24: warning: "struct inode" declared inside parameter
list
include/linux/cdev.h:24: warning: its scope is only this definition or
declaration, which is probably not what you want
DirectFB-1.2.0/gfxdrivers/davinci/kernel-module/c64x/c64x.c:116: error:
parse error before string constant
DirectFB-1.2.0/gfxdrivers/davinci/kernel-module/c64x/c64x.c:116: warning:
type defaults to `int' in declaration of `MODULE_FIRMWARE'
/DirectFB-1.2.0/gfxdrivers/davinci/kernel-module/c64x/c64x.c:116: warning:
function declaration isn't a prototype

Why i am not able to find MODULE_FIRMWARE. Is this because of conflicts
between kernel and directfb  versions or something else

Thanks in advance
Deepak
___
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

49 matches

Mail list logo