Hi As you mentioned the Raspberry Pi: BOINC is available in the repo of Raspian, a Debian wheezy fork, and it uses the platform string 'arm-unknown-linux-gnueabihf'.
It does make sense IMHO to differentiate in the platform string between hard float (as with Raspbian) and soft float ABI platforms for the ARM CPU (e.g. the native Debian wheezy for ARMv6 CPUs), because they are not binary compatible. The project has to know what kind of executable it can send to the client, and the natural way to do so is via the platform string. Cheers HB Von meinem iPad gesendet Am 03.07.2013 um 21:10 schrieb yoyo <[email protected]>: > Hello, > > are there some rules which platform string a Boinc client on a ARM > device (not Android) should sent? > Here http://boinc.berkeley.edu/trac/wiki/BoincPlatforms only Android is > mentioned. > > But what about RasPi, Odroid or my NAS server which runs: > # uname -a > Linux nas02 2.6.33.2 #1 Fri Apr 26 05:33:12 CST 2013 armv5tel unknown > > # cat /proc/cpuinfo > Processor name : Feroceon 88F6282 rev 1 (v5l) @ 2 GHz > BogoMIPS : 1985.74 > Features : swp half thumb fastmult edsp > CPU implementer : 0x56 > CPU architecture: 5TE > CPU variant : 0x2 > CPU part : 0x131 > CPU revision : 1 > > Hardware : Feroceon-KW ARM > Revision : 0000 > Serial : 0000000000000000 > > I know these platform strings, but which ones are prefered?: > - arm-linux-gnu > - arm-unknown-linux-gnueabi > - arm-unknown-linux-gnueabihf > > What does other projects use? > > kind regards, > yoyo > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
