Dear all:<br> I am new to git, I use the following commend to get uboot <br>$git clone rsync://source.denx.net/git/u-boot.git u-boot.git <br><br>And finally I got :<br><br>$sent 115275 bytes received 56318206 bytes 32686.64 bytes/sec<br>total size is 55817433 speedup is 0.99<br>Checking files out...<br> 100% (4356/4356) done<br><br>Is that all? Does it means I got the newest version of uboot?<br><br>$cd uboot.git<br>$make distclean<br>$make omap2420h4_congfig<br>$make <br><br>Oops! I still got<br>***************************************************************************<br> --start-group lib_generic/libgeneric.a board/omap2420h4/libomap2420h4.a cpu/arm1136/libarm1136.a lib_arm/libarm.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.a fs/ext2/libext2fs.a net/libnet.a
disk/libdisk.a rtc/librtc.a dtt/libdtt.a drivers/libdrivers.a drivers/nand/libnand.a drivers/nand_legacy/libnand_legacy.a drivers/sk98lin/libsk98lin.a post/libpost.a post/cpu/libcpu.a common/libcommon.a --end-group -L /usr/local/arm/gcc-4.0.2/bin/../lib/gcc/arm-linux/4.0.2 -lgcc \<br> -Map u-boot.map -o u-boot<br>common/libcommon.a(env_flash.o): In function `env_init':<br>/home/yanming/Desktop/u-boot.git/common/env_flash.c:265: undefined reference to `flash_probe'<br>make: *** [u-boot] Error 1<br>*******************************************************************<br><br>And I fraid I could not find the patch on the mail achieve.<br>but I got <br>http://linux.omap.com/pipermail/linux-omap-open-source/2005-December/006018.html<br>However it seems little help for me.<br><br>Any suggestions? Thanks . Best Regards :-)<br><br><b><i>Wolfgang Denk <wd@denx.de></i></b>
說：<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> In message <EA12F909C0431D458B9D18A176BEE4A507011835@dlee02.ent.ti.com> you wrote:<br>> <br>> > The current U-Boot code is broken, and the board maintainer (Richard<br>> > Woodruff, on Cc:) did not care so far.<br>> <br>> Well, that is partially true. I have not tried to resync for many<br>> months now. Previous patches lagged commit so long that that it was not<br>> necessary workable by the time they were applied. The code has been<br>> pretty dynamic as perhaps a dozen versions of the board appeared in a<br>> very short time.<br><br>Use git, and provide access to your repo.<br><br>> Some of those issues dealt with the cfi_flash code and what was<br>> acceptable. That code has changed much since then and is perhaps worth<br>> trying against again. The NAND tree has also changed a lot and will<br>> take
more effort to re-validate.<br><br>You will run into this again and again the longer you keep<br>disconnected from the development in the main repo. Use git 9or one<br>of the porcelains, for example stgit), and update often.<br><br>Best regards,<br><br>Wolfgang Denk<br><br>-- <br>Software Engineering: Embedded and Realtime Systems, Embedded Linux<br>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de<br>Some people march to the beat of a different drummer. And some people<br>tango!<br></EA12F909C0431D458B9D18A176BEE4A507011835@dlee02.ent.ti.com></blockquote><br><p> ___________________________________________________ <br> 最新版 Yahoo!奇摩即時通訊 7.0，免費網路電話任你打！ <br> http://messenger.yahoo.com.tw/