<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div>I think I2C-tools is what you need as sample code to access I2C in Linux. Here is the link<br>http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-3.0.1.tar.bz2<br>There are a lot of tools to access, set/get/dump register, read/write the I2C eeprom...<br>But please use them with care, especially when you try to read/write the device at address 0x50 ( it's is bootstrap eeprom). <br>You might not boot up your board after playing with this device :-)<br>Quan Nguyen<br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;">----- Thư gốc ----<br>Từ: Duy-Ky Nguyen <duykynguyen@hotmail.com><br>Đến: linuxppc-embedded@ozlabs.org<br>Gửi ngày: Thứ Sáu, 10 tháng 10, 2008
6:11:22<br>Chủ đề: API access I2C<br><br>Hello,<br><br>I have an eva board MPC8313E-RDB with 3 I2C device at address 48, 50, 68.<br>I'm able to read data from those 3 devices<br><br>I follow linux/Documentation/i2c/dev-interface to create a C code to access <br>those 3 devices in Linux env, but all are failed !!!<br><br>I really appreciate your help where to find info or sample code running in <br>Linyux to access I2C devices<br><br>Thanks so much,<br><br>Duy-Ky<br><br>----- Original Message ----- <br>From: <<a ymailto="mailto:linuxppc-embedded-request@ozlabs.org" href="mailto:linuxppc-embedded-request@ozlabs.org">linuxppc-embedded-request@ozlabs.org</a>><br>To: <<a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a>><br>Sent: Thursday, October 09, 2008 2:05 PM<br>Subject: Linuxppc-embedded Digest, Vol 50, Issue 14<br><br><br>> Send Linuxppc-embedded mailing
list submissions to<br>> <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>><br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-embedded" target="_blank">https://ozlabs.org/mailman/listinfo/linuxppc-embedded</a><br>> or, via email, send a message with subject or body 'help' to<br>> <a ymailto="mailto:linuxppc-embedded-request@ozlabs.org" href="mailto:linuxppc-embedded-request@ozlabs.org">linuxppc-embedded-request@ozlabs.org</a><br>><br>> You can reach the person managing the list at<br>> <a ymailto="mailto:linuxppc-embedded-owner@ozlabs.org" href="mailto:linuxppc-embedded-owner@ozlabs.org">linuxppc-embedded-owner@ozlabs.org</a><br>><br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Linuxppc-embedded
digest..."<br>><br>><br>> Today's Topics:<br>><br>> 1. Re: performance: memcpy vs. __copy_tofrom_user (Leon Woestenberg)<br>> 2. Re: performance: memcpy vs. __copy_tofrom_user (Matt Sealey)<br>> 3. Toolchain for ppc-440 without FPU (Ademir Zanetti Junior)<br>> 4. Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup<br>> (100005/1) (Remi Lefevre)<br>> 5. MTD map drivers (FSL UPM NAND) (Alemao)<br>> 6. RE: Toolchain for ppc-440 without FPU (Ayman El-Khashab)<br>><br>><br>> ----------------------------------------------------------------------<br>><br>> Message: 1<br>> Date: Thu, 9 Oct 2008 14:04:53 +0200<br>> From: "Leon Woestenberg" <<a ymailto="mailto:leon.woestenberg@gmail.com" href="mailto:leon.woestenberg@gmail.com">leon.woestenberg@gmail.com</a>><br>> Subject: Re: performance: memcpy vs. __copy_tofrom_user<br>> To:
"Dominik Bozek" <<a ymailto="mailto:domino@mikroswiat.pl" href="mailto:domino@mikroswiat.pl">domino@mikroswiat.pl</a>><br>> Cc: <a ymailto="mailto:linuxppc-dev@ozlabs.org" href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a>, Paul Mackerras <<a ymailto="mailto:paulus@samba.org" href="mailto:paulus@samba.org">paulus@samba.org</a>>,<br>> <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Message-ID:<br>> <<a ymailto="mailto:c384c5ea0810090504x570cb6aai6d136a150e74ac05@mail.gmail.com" href="mailto:c384c5ea0810090504x570cb6aai6d136a150e74ac05@mail.gmail.com">c384c5ea0810090504x570cb6aai6d136a150e74ac05@mail.gmail.com</a>><br>> Content-Type: text/plain; charset=ISO-8859-1<br>><br>> Hello all,<br>><br>> On Thu, Oct 9, 2008 at 1:41 PM, Dominik Bozek <<a ymailto="mailto:domino@mikroswiat.pl"
href="mailto:domino@mikroswiat.pl">domino@mikroswiat.pl</a>> <br>> wrote:<br>>> Paul Mackerras wrote:<br>>>> Dominik Bozek writes:<br>>>>> Actually I made couple of other tests on that mpc8313. Most of them are<br>>>>> to ugly to publish them, but... My problem is that I have to boost the<br>>>>> gigabit interface on the mpc8313. I made simple substitution and<br>>>><br>>>> Very interesting. Can you work out where memcpy is being called on<br>>>> the network data? I wouldn't have expected that.<br>>>><br>><br>> Also see this recent thread David Jander on August 25th, "Efficient<br>> memcpy()/memmove() for G2/G3 cores..."<br>> on <a ymailto="mailto:linuxppc-dev@ozlabs.org" href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a>.<br>><br>> <a href="http://ozlabs.org/pipermail/linuxppc-dev/2008-September/062449.html"
target="_blank">http://ozlabs.org/pipermail/linuxppc-dev/2008-September/062449.html</a><br>><br>> BTW, I am interested in this work as well, I'm currently working with<br>> a 8313 and 8315 design, both are e300 cores.<br>><br>> My current goal is PCIe though, but I need fast GbE performance as well.<br>><br>> Also, did you test Freescale's 2.6.24.3 patches that tune the gianfar<br>> interfaces for higher performance?<br>><br>> Regards,<br>> -- <br>> Leon<br>><br>><br>> ------------------------------<br>><br>> Message: 2<br>> Date: Thu, 09 Oct 2008 10:37:55 -0500<br>> From: Matt Sealey <<a ymailto="mailto:matt@genesi-usa.com" href="mailto:matt@genesi-usa.com">matt@genesi-usa.com</a>><br>> Subject: Re: performance: memcpy vs. __copy_tofrom_user<br>> To: Paul Mackerras <<a ymailto="mailto:paulus@samba.org" href="mailto:paulus@samba.org">paulus@samba.org</a>><br>> Cc: <a
ymailto="mailto:linuxppc-dev@ozlabs.org" href="mailto:linuxppc-dev@ozlabs.org">linuxppc-dev@ozlabs.org</a>, Dominik Bozek <<a ymailto="mailto:domino@mikroswiat.pl" href="mailto:domino@mikroswiat.pl">domino@mikroswiat.pl</a>>,<br>> <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Message-ID: <<a ymailto="mailto:48EE2553.30903@genesi-usa.com" href="mailto:48EE2553.30903@genesi-usa.com">48EE2553.30903@genesi-usa.com</a>><br>> Content-Type: text/plain; charset=UTF-8; format=flowed<br>><br>> Paul Mackerras wrote:<br>>> Dominik Bozek writes:<br>>><br>>>> Actually I made couple of other tests on that mpc8313. Most of them are<br>>>> to ugly to publish them, but... My problem is that I have to boost the<br>>>> gigabit interface on the mpc8313. I made simple substitution and<br>>>> __copy_tofrom_user was used
instead of memcpy. I know, it's wrong, but I<br>>>> speedup that way the network interface for about 10%.<br>>><br>>> Very interesting. Can you work out where memcpy is being called on<br>>> the network data? I wouldn't have expected that.<br>><br>> It probably is somewhere.. through some weird and wonderful code path that<br>> needs some serious digging to find. At least in 2.4 memcpy was used and<br>> optimizing it (see Freescale's libmotovec benchmarks) did produce a <br>> sizable<br>> performance improvement. That, and offloading TCP checksumming to AltiVec<br>> helped a lot.<br>><br>> No help at all on an 8313 but, relevant anyway.<br>><br>> Since then zero copy networking and other fancy things like the DMA<br>> engine API (for intel ioat at least but also there is fsl dma support)<br>> there's less to actually optimize now so you're less likely to see the<br>> same
benefits. All these got into mainline because it's essential to<br>> have this kind of architecture to get reasonable speeds out of >gigabit<br>> network links.<br>><br>>> There is actually no strong reason not to use __copy_tofrom_user as<br>>> memcpy, in fact, as long as we are sure that source and destination<br>>> are both cacheable.<br>><br>> I do think there is probably a good benefit in doing things like zeroing<br>> pages in AltiVec and copying entire pages with AltiVec (for instance<br>> when copy-on-write happens in an application) - NetBSD and QNX implement<br>> at least this because it's faster than using the cache management and<br>> works fine on uncacheable pages too (also since you're always aligned to<br>> a page, zeroing 4kb aligned to a 4kb boundary - or whatever your page<br>> size happens to be, the number of errors that can occur are absolutely<br>> tiny and performance can
go through the roof).<br>><br>> Ahem, but nobody here wants AltiVec in the kernel do they?<br>><br>> -- <br>> Matt Sealey <<a ymailto="mailto:matt@genesi-usa.com" href="mailto:matt@genesi-usa.com">matt@genesi-usa.com</a>><br>> Genesi, Manager, Developer Relations<br>><br>><br>> ------------------------------<br>><br>> Message: 3<br>> Date: Thu, 9 Oct 2008 16:08:18 -0300<br>> From: "Ademir Zanetti Junior" <<a ymailto="mailto:ademirzanetti@gmail.com" href="mailto:ademirzanetti@gmail.com">ademirzanetti@gmail.com</a>><br>> Subject: Toolchain for ppc-440 without FPU<br>> To: <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Message-ID:<br>> <<a ymailto="mailto:2204d6480810091208u1776e81fx6597719734751edb@mail.gmail.com"
href="mailto:2204d6480810091208u1776e81fx6597719734751edb@mail.gmail.com">2204d6480810091208u1776e81fx6597719734751edb@mail.gmail.com</a>><br>> Content-Type: text/plain; charset="utf-8"<br>><br>> Hello all,<br>><br>> I am trying to create a toolchain by hand and I am facing some problems <br>> when<br>> I try to configure the glibc 2.7 for a powerpc. When I try to configure <br>> the<br>> glibc to install the headers I get the following error:<br>><br>> configure --prefix=/usr --host=powerpc-440-linux-gnu<br>> --with-headers=${SYSROOT}/usr/include --disable-shared --without-cvs<br>> --with-binutils=/home/azanetti/ml507/powerpc/bin/<br>><br>> checking build system type... i686-pc-linux-gnu<br>> checking host system type... i686-pc-linux-gnu<br>> configure: running configure fragment for add-on nptl<br>> checking sysdep dirs... sysdeps/i386/elf<br>> nptl/sysdeps/unix/sysv/linux/i386/i686
nptl/sysdeps/unix/sysv/linux/i386<br>> sysdeps/unix/sysv/linux/i386 nptl/sysdeps/unix/sysv/linux<br>> nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu<br>> sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet<br>> sysdeps/unix/sysv/i386 nptl/sysdeps/unix/sysv sysdeps/unix/sysv<br>> sysdeps/unix/i386 nptl/sysdeps/unix sysdeps/unix sysdeps/posix<br>> sysdeps/i386/i686/fpu nptl/sysdeps/i386/i686 sysdeps/i386/i686<br>> sysdeps/i386/i486 nptl/sysdeps/i386/i486 sysdeps/i386/fpu <br>> nptl/sysdeps/i386<br>> sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96<br>> sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754<br>> sysdeps/generic/elf sysdeps/generic<br>> checking for a BSD-compatible install... /usr/bin/install -c<br>> checking whether ln -s works... yes<br>> checking for gcc... gcc<br>> checking for suffix of object files... o<br>> checking whether we are using the
GNU C compiler... yes<br>> checking whether gcc accepts -g... yes<br>> checking for gcc option to accept ISO C89... none needed<br>> checking how to run the C preprocessor... gcc -E<br>> checking for g++... g++<br>><br>> .<br>> .<br>> .<br>> checking for long double... yes<br>> checking size of long double... 12<br>> running configure fragment for sysdeps/powerpc/powerpc32/elf<br>> checking for powerpc32 TLS support... no<br>> running configure fragment for sysdeps/unix/sysv/linux/powerpc<br>> checking whether gcc -B/home/azanetti/ml507/powerpc/bin/ -g -O2<br>> -mlong-double-128 uses IBM extended format... no<br>> checking whether gcc -B/home/azanetti/ml507/powerpc/bin/ -g -O2 supports<br>> -mabi=ibmlongdouble... no<br>> configure: error: this configuration requires -mlong-double-128 IBM <br>> extended<br>> format support<br>><br>><br>> I already have the binutils 2.18 compiled on my
PATH. I know that it is<br>> easier to use a script like crosstool to compile it but I do want to<br>> understand what is happening behind the scenes.<br>><br>> Regards.<br>><br>> Ademir<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <br>> <<a href="http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081009/a3dd71d6/attachment-0001.htm" target="_blank">http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081009/a3dd71d6/attachment-0001.htm</a>><br>><br>> ------------------------------<br>><br>> Message: 4<br>> Date: Thu, 9 Oct 2008 21:46:42 +0200<br>> From: "Remi Lefevre" <<a ymailto="mailto:rlefevre@gmail.com" href="mailto:rlefevre@gmail.com">rlefevre@gmail.com</a>><br>> Subject: Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup<br>> (100005/1)<br>> To: "Scott Wood" <<a ymailto="mailto:scottwood@freescale.com"
href="mailto:scottwood@freescale.com">scottwood@freescale.com</a>><br>> Cc: <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Message-ID:<br>> <<a ymailto="mailto:4e0b9cb00810091246i2f200dbn9f8dc9877800e629@mail.gmail.com" href="mailto:4e0b9cb00810091246i2f200dbn9f8dc9877800e629@mail.gmail.com">4e0b9cb00810091246i2f200dbn9f8dc9877800e629@mail.gmail.com</a>><br>> Content-Type: text/plain; charset=ISO-8859-1<br>><br>> Ok, I'm sorry, I have incorrectly set the 60x pipeline depth to 0<br>> instead of 1 in BCR register.<br>> It works fine now. The side effect is interesting to know...<br>><br>> regards,<br>> r?mi<br>><br>><br>> ------------------------------<br>><br>> Message: 5<br>> Date: Thu, 9 Oct 2008 18:04:25 -0300<br>> From: Alemao <<a ymailto="mailto:xcarandiru@gmail.com"
href="mailto:xcarandiru@gmail.com">xcarandiru@gmail.com</a>><br>> Subject: MTD map drivers (FSL UPM NAND)<br>> To: <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Message-ID:<br>> <<a ymailto="mailto:d970ff420810091404j49492e80xcd9250d0ffdcd592@mail.gmail.com" href="mailto:d970ff420810091404j49492e80xcd9250d0ffdcd592@mail.gmail.com">d970ff420810091404j49492e80xcd9250d0ffdcd592@mail.gmail.com</a>><br>> Content-Type: text/plain; charset=ISO-8859-1<br>><br>> Hi all,<br>><br>> Im trying to use a physmap driver for NOR and NAND flash devices.<br>><br>> With NOR, everything ok. It uses CFI driver.<br>><br>> The problem is with NAND, cause it is connected at Freescale<br>> LocalBus UPM, and at a first look, the UPM driver is loading after the<br>> physmap (lines 14-15 in kernel output)<br>><br>> Here some outputs from
the board:<br>><br>> Bootloader (U-Boot 1.2.0):<br>><br>> CPU: e300c1, MPC8360E, Rev: 21 at 499.999 MHz, CSB: 333 MHz<br>> Board: MPC8360KTX<br>> I2C: ready<br>> DDR RAM: 128 MB<br>> FLASH: 16 MB<br>> NAND: 64 MiB<br>> In: serial<br>> Out: serial<br>> Err: serial<br>><br>><br>> Kernel (linux-2.6.17):<br>><br>> 1 physmap nor flash device: 1000000 at ff000000<br>> 2 NOR flash: Found 1 x16 devices at 0x0 in 16-bit bank<br>> 3 Amd/Fujitsu Extended Query Table at 0x0040<br>> 4 number of CFI chips: 1<br>> 5 Using physmap partition definition<br>> 6
Creating 6 MTD partitions on "NOR flash":<br>> 7 0x00000000-0x00040000 : "u-boot"<br>> 8 0x00040000-0x00060000 : "env."<br>> 9 0x00060000-0x00080000 : "sys"<br>> 10 0x00080000-0x000c0000 : "logs"<br>> 11 0x000c0000-0x00860000 : "admin"<br>> 12 0x00860000-0x01000000 : "users"<br>> 13<br>> 14 physmap nand flash device: 4000000 at 60000000<br>> 15 UPM: User-Programmable Machine NAND driver<br>><br>><br>> Device Tree Source:<br>><br>> localbus@e0005000 {<br>> compatible = "fsl,board-localbus";<br>>
#address-cells = <2>;<br>> #size-cells = <1>;<br>> reg = <e0005000 d8>; // BRx, ORx, etc<br>><br>> ranges = <0 0 ff000000 1000000 // nor flash, 16 MB<br>> 1 0 60000000 4000000>; // nand flash, 64 MB<br>><br>> flash@0,0 {<br>> compatible = "atmel,29LV256", "cfi-flash";<br>> reg = <0 0 1000000>;<br>> bank-width = <2>;<br>> device-width = <1>;<br>> };<br>><br>> nand@1,0 {<br>> compatible = "stmicro,NAND512W3A", "fsl,upm-nand";<br>> reg = <1 0 4000000>; //reg = <1 0 1>;<br>> width = <1>;<br>> upm = "A";<br>>
upm-addr-offset = <16>;<br>> upm-cmd-offset = <8>;<br>> gpios = <4 18>;<br>> gpio-parent = <&qe_pio>;<br>> wait-pattern;<br>> wait-write;<br>> };<br>> };<br>><br>> The CFI driver is at linux/drivers/mtd/chips<br>> The UPM driver is at linux/drivers/mtd/nand<br>><br>> So, how can I load the UPM driver before physmap?<br>><br>> Thanks in advance,<br>><br>> --<br>> Alemao<br>><br>><br>> ------------------------------<br>><br>> Message: 6<br>> Date: Thu, 9 Oct 2008 16:05:47 -0500<br>> From: "Ayman El-Khashab" <<a ymailto="mailto:AymanE@tanisys.com" href="mailto:AymanE@tanisys.com">AymanE@tanisys.com</a>><br>> Subject: RE: Toolchain for ppc-440 without FPU<br>> To: "Ademir Zanetti Junior" <<a ymailto="mailto:ademirzanetti@gmail.com"
href="mailto:ademirzanetti@gmail.com">ademirzanetti@gmail.com</a>>,<br>> <<a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a>><br>> Message-ID:<br>> <<a ymailto="mailto:16691A8B34B5D9458EA3A1C37A11555A0137F80B@tanisys-ex2.Tanisys.Local" href="mailto:16691A8B34B5D9458EA3A1C37A11555A0137F80B@tanisys-ex2.Tanisys.Local">16691A8B34B5D9458EA3A1C37A11555A0137F80B@tanisys-ex2.Tanisys.Local</a>><br>> Content-Type: text/plain; charset="us-ascii"<br>><br>> I was compiling for the 440FP under cygwin, I believe that I had to use<br>> --enable-long-long when I configured gcc in order to build glibc.<br>><br>> ________________________________<br>><br>> From: linuxppc-embedded-bounces+aymane=<a ymailto="mailto:tanisys.com@ozlabs.org" href="mailto:tanisys.com@ozlabs.org">tanisys.com@ozlabs.org</a><br>> [mailto:linuxppc-embedded-bounces+aymane=<a
ymailto="mailto:tanisys.com@ozlabs.org" href="mailto:tanisys.com@ozlabs.org">tanisys.com@ozlabs.org</a>] On<br>> Behalf Of Ademir Zanetti Junior<br>> Sent: Thursday, October 09, 2008 2:08 PM<br>> To: <a ymailto="mailto:linuxppc-embedded@ozlabs.org" href="mailto:linuxppc-embedded@ozlabs.org">linuxppc-embedded@ozlabs.org</a><br>> Subject: Toolchain for ppc-440 without FPU<br>><br>><br>> Hello all,<br>><br>> I am trying to create a toolchain by hand and I am facing some problems<br>> when I try to configure the glibc 2.7 for a powerpc. When I try to<br>> configure the glibc to install the headers I get the following error:<br>><br>> configure --prefix=/usr --host=powerpc-440-linux-gnu<br>> --with-headers=${SYSROOT}/usr/include --disable-shared --without-cvs<br>> --with-binutils=/home/azanetti/ml507/powerpc/bin/<br>><br>> checking build system type... i686-pc-linux-gnu<br>> checking host system type...
i686-pc-linux-gnu<br>> configure: running configure fragment for add-on nptl<br>> checking sysdep dirs... sysdeps/i386/elf<br>> nptl/sysdeps/unix/sysv/linux/i386/i686 nptl/sysdeps/unix/sysv/linux/i386<br>> sysdeps/unix/sysv/linux/i386 nptl/sysdeps/unix/sysv/linux<br>> nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu<br>> sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet<br>> sysdeps/unix/sysv/i386 nptl/sysdeps/unix/sysv sysdeps/unix/sysv<br>> sysdeps/unix/i386 nptl/sysdeps/unix sysdeps/unix sysdeps/posix<br>> sysdeps/i386/i686/fpu nptl/sysdeps/i386/i686 sysdeps/i386/i686<br>> sysdeps/i386/i486 nptl/sysdeps/i386/i486 sysdeps/i386/fpu<br>> nptl/sysdeps/i386 sysdeps/i386 sysdeps/wordsize-32<br>> sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32<br>> sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic<br>> checking for a BSD-compatible install... /usr/bin/install
-c<br>> checking whether ln -s works... yes<br>> checking for gcc... gcc<br>> checking for suffix of object files... o<br>> checking whether we are using the GNU C compiler... yes<br>> checking whether gcc accepts -g... yes<br>> checking for gcc option to accept ISO C89... none needed<br>> checking how to run the C preprocessor... gcc -E<br>> checking for g++... g++<br>><br>> .<br>> .<br>> .<br>> checking for long double... yes<br>> checking size of long double... 12<br>> running configure fragment for sysdeps/powerpc/powerpc32/elf<br>> checking for powerpc32 TLS support... no<br>> running configure fragment for sysdeps/unix/sysv/linux/powerpc<br>> checking whether gcc -B/home/azanetti/ml507/powerpc/bin/ -g -O2<br>> -mlong-double-128 uses IBM extended format... no<br>> checking whether gcc -B/home/azanetti/ml507/powerpc/bin/ -g -O2 supports<br>> -mabi=ibmlongdouble... no<br>> configure:
error: this configuration requires -mlong-double-128 IBM<br>> extended format support<br>><br>><br>> I already have the binutils 2.18 compiled on my PATH. I know that it is<br>> easier to use a script like crosstool to compile it but I do want to<br>> understand what is happening behind the scenes.<br>><br>> Regards.<br>><br>> Ademir<br>><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <br>> <<a href="http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081009/c91ac7a9/attachment.htm" target="_blank">http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20081009/c91ac7a9/attachment.htm</a>><br>><br>> ------------------------------<br>><br>> _______________________________________________<br>> Linuxppc-embedded mailing list<br>> <a ymailto="mailto:Linuxppc-embedded@ozlabs.org"
href="mailto:Linuxppc-embedded@ozlabs.org">Linuxppc-embedded@ozlabs.org</a><br>> <a href="https://ozlabs.org/mailman/listinfo/linuxppc-embedded" target="_blank">https://ozlabs.org/mailman/listinfo/linuxppc-embedded</a><br>><br>> End of Linuxppc-embedded Digest, Vol 50, Issue 14<br>> *************************************************<br>> <br><br>_______________________________________________<br>Linuxppc-embedded mailing list<br><a ymailto="mailto:Linuxppc-embedded@ozlabs.org" href="mailto:Linuxppc-embedded@ozlabs.org">Linuxppc-embedded@ozlabs.org</a><br><a href="https://ozlabs.org/mailman/listinfo/linuxppc-embedded" target="_blank">https://ozlabs.org/mailman/listinfo/linuxppc-embedded</a><br></div></div></div><br>
<hr size="1"><FONT face=Arial size=-1>Nước nào thường cho nhiều học bổng du học? Khám phá tại <a href="http://sg.rd.yahoo.com/mail/vn/footer/def/*http://vn.answers.yahoo.com">Yahoo! Hỏi & Đáp</a></font></body></html>