Dear Minkyu Kang, In message <1f3430fb0907200415n1482bc40s33a44cf3ca439...@mail.gmail.com> you wrote: > > > Find out which part of your code triggers the use of the _dvmd_lnx.o > > code and avoid this; from the error message it seems to be some > > (long) division. > > yes, we tried it. > but, can't find about it...
Why not? Using "nm" it should be trivial to find out from which source file such a reference is coming from, and either using "gcc -S" or "objdump -SD" or "gdb" should be suifficient to locate the C code that is to blame for it. > Omap3 also has raise function at cpu/arm_cortexa8/omap3/board.c(303 line) Ah... thanks for pointing out. Dirk Behme should be able to tell us about it. Dirk, can we please get rid of this raise() and abort() stuff? Even if in the end we should agree that we should keep these, it definitely makes no sense to add this in a CPU specific file. > I think this is a matter of coretexA8, and want to use this workaround > function > until fix the problem. I am pretty much sure that this has nothing to do with CortexA8 per se. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de To the systems programmer, users and applications serve only to provide a test load. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
