You need to set static IP address as: ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> for example ip=172.18.1.222:172.18.1.49:172.18.0.254:255.255.0.0:::off
Regards, Jitendra -----Original Message----- From: [EMAIL PROTECTED] on behalf of Mohamed AbdElwahed Sent: Thu 10/23/2008 4:21 PM To: davinci-linux-open-source@linux.davincidsp.com Subject: How to disable DHCP requestes and assign a static IP to the board during booting? When I boot the board from ramfile system it keep displaying this message for long time: Requesting DHCP.. Even if I am using setenv bootargs 'console=ttyS0,115200n8 ip=192.168.0.20 root=/dev/ram0 rw initrd=0x85000000,6M' How can I disable DHCP or statically assign the ip to the development board in the u-boot ? target board DVM6446 --------------------------------- any help, useful documents, URL links is highly appreciated thanks in advance > From: [EMAIL PROTECTED]> Subject: Davinci-linux-open-source Digest, Vol 34, > Issue 99> To: davinci-linux-open-source@linux.davincidsp.com> Date: Thu, 23 > Oct 2008 05:02:22 -0500> > Send Davinci-linux-open-source mailing list > submissions to> davinci-linux-open-source@linux.davincidsp.com> > To > subscribe or unsubscribe via the World Wide Web, visit> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source> > > or, via email, send a message with subject or body 'help' to> [EMAIL > PROTECTED]> > You can reach the person managing the list at> [EMAIL > PROTECTED]> > When replying, please edit your Subject line so it is more > specific> than "Re: Contents of Davinci-linux-open-source digest..."> > > > Today's Topics:> > 1. dm355 spi (BJ Opp)> 2. RE: basic question(s)... > (Kamoolkar, Mugdha)> 3. Re: RTSC Server Package Wizard ([EMAIL PROTECTED])> > 4. Hi (Madhu K)> 5. Re: Codec Engine Code Overlays with more than one > codec?> (Vladimir Pantelic)> 6. Re: dm355 spi (Andrea Gasparini)> 7. dm644x > - fbdev in kernel 2.6.25-davinci1 (Gabriele Filosofi)> > > > ----------------------------------------------------------------------> > > Message: 1> Date: Wed, 22 Oct 2008 21:08:09 -0700> From: BJ Opp <[EMAIL > PROTECTED]>> Subject: dm355 spi> To: > "davinci-linux-open-source@linux.davincidsp.com"> > <davinci-linux-open-source@linux.davincidsp.com>> Message-ID:> <[EMAIL > PROTECTED]>> Content-Type: text/plain; charset="us-ascii"> > Hello all,> > > I'm aware that spi on the dm355 has been discussed previously on this list > since I've also been included in it but I have a question. I had worked with > a previous release of the dm355 kernel where there was no spi support and > made use of Josh Hintze's (sp?) spi driver to talk to a device on my custom > board. I was under the impression that the 'latest' release of the dm355 > kernel (~may 2008) actually had spi support built into it where you could > access it like the i2c bus via a device node. I've picked my way through the > kernel and can't seem to find any such functionality. The only chatter I've > seen on this mailing list seems to lean toward people pushing others to use > /dev/mtd to talk spi but that really doesn't make any sense unless they mean > to use that when trying to talk to a nand or other such block device.> > Has > anybody had any experience with spi on the 'new' dm355 kernel? And even > further, has anybody worked with spi1? If need be I can try to leverage the > code I already have (again, thanks to Josh's efforts) but I want to make > sure I'm not missing something here. I've also applied the sdio patch which > makes reference to spi which is another reason why I believe I'm missing > something. Thanks for any direction.> > BJ> > > > > ------------------------------> > Message: 2> Date: Thu, 23 Oct 2008 > 09:52:31 +0530> From: "Kamoolkar, Mugdha" <[EMAIL PROTECTED]>> Subject: RE: > basic question(s)...> To: "Tivy, Robert" <[EMAIL PROTECTED]>, Ed Sutter> > <[EMAIL PROTECTED]>,> "davinci-linux-open-source@linux.davincidsp.com"> > <davinci-linux-open-source@linux.davincidsp.com>> Message-ID:> <[EMAIL > PROTECTED]>> Content-Type: text/plain; charset="us-ascii"> > To add to that, > all tools you need for building DSP-side are available standalone as well > (outside of CCS):> Target Content: > https://www-a.ti.com/downloads/sds_support/targetcontent/index.html> CodeGen > tools: https://www-a.ti.com/downloads/sds_support/CodeGenerationTools.htm> > > Generally good to look at for high level information about everything:> > http://tiexpressdsp.com/wiki/index.php?title=Main_Page> > http://wiki.davincidsp.com/index.php?title=Main_Page> > Regards,> Mugdha> > > -----Original Message-----> From: [EMAIL PROTECTED] [mailto:[EMAIL > PROTECTED] On Behalf Of Tivy, Robert> Sent: Thursday, October 23, 2008 5:33 > AM> To: Ed Sutter; davinci-linux-open-source@linux.davincidsp.com> Subject: > RE: basic question(s)...> > > I don't know about "standard library/hookup", > but DSP/BIOS and DSPLink are widely used for the ARM<->DSP communication. > DSPLink is kind of low level, so you could also use Codec Engine from TI for > simplifying and/or abstracting the interface between the DSP and ARM, and in > doing so could probably forgo the need for CCS.> > - Rob> > > -----Original > Message-----> > From: [EMAIL PROTECTED]> > [mailto:[EMAIL PROTECTED]> > ] On > Behalf Of Ed Sutter> > Sent: Wednesday, October 22, 2008 12:14 PM> > To: > davinci-linux-open-source@linux.davincidsp.com> > Subject: basic > question(s)...> > > > Hi,> > More questions for any of you patient enough to > answer...> > I'm trying to get to know the OMAP35xx development environment > a bit > > better.> > > > What is the typical mode of development for > OMAP35xx based projects?> > I'm guessing that the answer to this question is > dependent on what it > > is I need to develop.> > > > Do most folks dig > right in and do both linux/arm and C64 development?> > > > Is there a > standard library/hookup between linux on the ARM and the > > DSP?> > > > If > I need to do some DSP programming do I have to purchase CCS or are > > there > other alternatives?> > > > Thanks in advance...> > Ed> > > > > _______________________________________________> > 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> > > > ------------------------------> > Message: 3> Date: Thu, 23 Oct 2008 > 10:57:08 +0530> From: [EMAIL PROTECTED]> Subject: Re: RTSC Server Package > Wizard> To: Albert Burbea <[EMAIL PROTECTED]>> Cc: > "davinci-linux-open-source@linux.davincidsp.com"> > <davinci-linux-open-source@linux.davincidsp.com>> Message-ID: <[EMAIL > PROTECTED]>> Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";> > format="flowed"> > Hi,> > You need to include the h264dec codec package > path.> It shall be> $DVSDK_INSTALL_DIR/dm6467_dvsdk_combos_1_35/packages/> > > thanks and regards> Girish> > Quoting Albert Burbea <[EMAIL PROTECTED]>:> > > > Hi everybody> > I am trying to build a codec/server bundle. I succeed to > run the example> > viddec provided in ceutils_1_06.> > when I try to build > the h264dec provided from TI, I succeed to build the> > codec, but when I > build the server I consistenly encounter the following> > error:> >> > > Package, ti.sdo.codecs.h264dec, not found with module H264DEC... modify > your> > XDCPATH to include the package's repository.> >> > Now, I checked > all the points in the FAQ, and I think I am OK. I build the> > server using > the following script> >> > [EMAIL PROTECTED] albertb_tests]$ cat > rtsc_svr_file.sh> > export MOZILLA_FIVE_HOME="/usr/lib/xulrunner-1.9pre"> > > export LD_LIBRARY_PATH="$MOZILLA_FIVE_HOME"> > export > LD_LIBRARY_PATH="$MOZILLA_FIVE_HOME/plugins:$LD_LIBRARY_PATH"> > export > DVSDK_INSTALL_DIR=${ACTIVE_DVSDK}> > export> > > XDCPATH="home/albertb/albertb_tests/packages;$DVSDK_INSTALL_DIR/ceutils_1_06/packages;$DVSDK_INSTALL_DIR/codec_engine_2_10_01/packages;$DVSDK_INSTALL_DIR/xdais_6_10_01/packages;$DVSDK_INSTALL_DIR/bios_5_32_01/package"> > > echo "XDC PATH IS "> > echo $XDCPATH> > echo> > xs > ti.sdo.codecutils.genserver -f="./test3.xml"> > and here is test3.xml> >> > > [EMAIL PROTECTED] albertb_tests]$ cat test3.xml> > <?xml > version="1.0"?><rtsc_server_package_wizard>> > <version>0.2.3</version>> > > <packageName>ti.sdo.codecs.h264dec</packageName>> > > <serverName>ti.sdo.servers.h264dec_unitserver_evmdm6467</serverName>> > > <outputRepository>/home/albertb/albertb_tests/codecs</outputRepository>> > > <platform>ti.platforms.evmDM6467</platform>> > <module>H264DEC</module>> > > </rtsc_server_package_wizard>> > the codec files are under > /home/albertb/albertb_tests/codecs, and the "body"> > of the codec is under> > >> /home/albertb/albertb_tests/codecs/ti/sdo/codecs/h264dec/> > Yet, it does > not build the server.... I begin to be quite desperate.> > Any help?> > > Albert> > --> > Albert Burbea> > Harishonim 8> > Ramat Gan 52502, Israel> > > Tel/Fax + 972-3-7526016> > Mobile: +972-52-3541842> >> > > > > > > ------------------------------> > Message: 4> Date: Wed, 22 Oct 2008 > 22:41:26 -0700> From: "Madhu K" <[EMAIL PROTECTED]>> Subject: Hi> To: > davinci-linux-open-source@linux.davincidsp.com> Message-ID:> <[EMAIL > PROTECTED]>> Content-Type: text/plain; charset="iso-8859-1"> > hi,i need > dm9000 ethernet miniport driver on dm355> -------------- next part > --------------> An HTML attachment was scrubbed...> URL: > http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081022/162cb33f/attachment-0001.htm> > > ------------------------------> > Message: 5> Date: Thu, 23 Oct 2008 > 09:21:30 +0200> From: Vladimir Pantelic <[EMAIL PROTECTED]>> Subject: Re: > Codec Engine Code Overlays with more than one codec?> To: > undisclosed-recipients: ;> Cc: > davinci-linux-open-source@linux.davincidsp.com> Message-ID: <[EMAIL > PROTECTED]>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed> > > Itay Chamiel wrote:> > Hi,> > > The only solution I have found so far is to > manually modify the > > auto-generated linker command file, moving the two > data sections into a > > single UNION with a shared run address. Once I did > that, the project > > linked, and ran correctly (both codecs simultaneously) > with a > > measurable performance increase. Unfortunately, this is no good > as a > > permanent fix because the command file gets overwritten at each > full build.> > > > Since the article I linked to above has no explanation of > this, and the > > codec authors themselves do not currently know how to > solve this problem > > short of repackaging the two codecs as a single > package, I'd like to > > know if the community has answers to this > question.> > what about removing the overlay related stuff from the codecs > link.xdt and adding them UNIONised in the servers link.cmd > file?> > > > > > > ------------------------------> > Message: 6> Date: Thu, 23 Oct 2008 > 09:34:20 +0200> From: Andrea Gasparini <[EMAIL PROTECTED]>> Subject: Re: > dm355 spi> To: davinci-linux-open-source@linux.davincidsp.com> Cc: BJ Opp > <[EMAIL PROTECTED]>> Message-ID: <[EMAIL PROTECTED]>> Content-Type: > text/plain; charset="iso-8859-1"> > Hi, > > BJ Opp spiffera, Thursday 23 > October 2008:> > The only chatter I've seen on this mailing list seems to> > > lean toward people pushing others to use /dev/mtd to talk spi but that> > > really doesn't make any sense unless they mean to use that when trying> > to > talk to a nand or other such block device.> > Well, AFAIK in MV kernel there > isn't a userspace general interface.> That's because you may want to > implement a device driver in kernel space.> > > Implementing a kernel driver > is quite simple, though: you only have to > configure your spi port, filing > the struct davinci_spi_config_t of your > platform data, and after that use > function like spi_write(), > spi_write_then_read(), spi_read(), and so > on...> > You saw talks on /dev/mtd, because the tipical example of spi > device driver > is mtd/devices/at25xxA_eeprom.c> Take it as reference for > SPI functions, and simply discard the mtd part, if > you don't need it.> > > -- > Andrea Gasparini > ---- ImaVis S.r.l. ----> web: www.imavis.com> > > > > ------------------------------> > Message: 7> Date: Thu, 23 Oct 2008 > 12:01:30 +0200> From: Gabriele Filosofi <[EMAIL PROTECTED]>> Subject: dm644x > - fbdev in kernel 2.6.25-davinci1> To: > "davinci-linux-open-source@linux.davincidsp.com"> > <davinci-linux-open-source@linux.davincidsp.com>> Message-ID:> <[EMAIL > PROTECTED]>> > Content-Type: text/plain; charset="us-ascii"> > Hi,> > By > modifying some VPBE registers I was able to display the colorbar on my QVGA > LCD, so the hardware setup is ok.> > Now I have an RGB656 image that is > 320x240. What would be the best way to get it statically onto the screen?> > > By copying (cp image /dev/fb/0) or cutting (cat image > /dev/fb/0) I get > nothing coming out of the display.> Is it not the fb stuff ready to be used > in git kernel 2.6.25-davinci1? Is there anything I need to do?> > Should I > write a program that opens up the OSD0 and then set the OSD dimensions to > 320x240 and then write the image file directly to /dev/fb/0?> > kindly help > me to come out from this problem.> > Thanks and regards,> > Gabriele> > > > -------------- next part --------------> An HTML attachment was scrubbed...> > URL: > http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081023/10de5725/attachment.htm> > > ------------------------------> > > _______________________________________________> Davinci-linux-open-source > mailing list> Davinci-linux-open-source@linux.davincidsp.com> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source> > > > End of Davinci-linux-open-source Digest, Vol 34, Issue 99> > ********************************************************* _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
