Eric last night released an Armv7l app that I compiled for him on my Raspberry Pi 2, It should work on any Armv7l Linux host,
but because of problems with restricting it to just that, it's getting sent to Armv6l hosts too, where it probably won't work. (It doesn't work on the original Raspberry Pi)

Please report any problems/observations in this thread.

Claggy

Example of the error the Armv7l app gets when attempting to run on an Armv6l equiped Pi Model B:

<core_client_version>7.2.47</core_client_version>
<![CDATA[
<message>
process got signal 4
</message>
<stderr_txt>
setiathome_v7 7.28 Revision: 2929 g++ (Debian 4.6.3-14+rpi1) 4.6.3
libboinc: BOINC 7.7.0

Work Unit Info:
...............
WU true angle range is : 0.008161

</stderr_txt>
]]>

Claggy

Can Android devices get it?

---

News about SETI opt app releases: https://twitter.com/Raistmer

Can Android devices get it?

Why? They have their own apps that don't have functions disabled for compatibility.

for Linux

Claggy

Eric last night released an Armv7l app that I compiled for him on my Raspberry Pi 2, It should work on any Armv7l Linux host,
but because of problems with restricting it to just that, it's getting sent to Armv6l hosts too, where it probably won't work. (It doesn't work on the original Raspberry Pi)

Please report any problems/observations in this thread.

Claggy

Will this work on a standard Raspberry Pi 2 with Raspbian Wheezy ?
I read somewhere that the BOINC version that comes with Wheezy does not recognize NEON support on the Pi 2 and so you will end up with applications without NEON support.
If it doesn't work with standard Raspbian Wheezy, what do you need to do to get this working ?
I'll order a Pi 2 the moment I know I can get this working without too much effort.

Thanks,

Tom

Eric last night released an Armv7l app that I compiled for him on my Raspberry Pi 2, It should work on any Armv7l Linux host,
but because of problems with restricting it to just that, it's getting sent to Armv6l hosts too, where it probably won't work. (It doesn't work on the original Raspberry Pi)

Please report any problems/observations in this thread.

Claggy

Will this work on a standard Raspberry Pi 2 with Raspbian Wheezy ?

According an Email from Eric, he had to remove all sorts of restrictions to enable hosts to get work, it'll mean hosts like Pi 1's where the app doesn't work will also get work:

http://setiweb.ssl.berkeley.edu/beta/plan_class_spec.xml

For example, see the armv7l planclass has no restictions, while the Android apps require some CPU support for each app:

<plan_class>
<name>ati_opencl_pre129</name>
<gpu_type>amd</gpu_type>
<ngpus>1</ngpus>
<cal/>
<max_core_client_version>69999</max_core_client_version>
<max_driver_version>1</max_driver_version>
<min_driver_version>1112000</min_driver_version>
<max_cal_target>888</max_cal_target>
<min_cal_target>5</min_cal_target>
<gpu_ram_used_mb>252</gpu_ram_used_mb>
<cpu_frac>0.01</cpu_frac>
<gpu_peak_flops_scale>0.03</gpu_peak_flops_scale>
<cpu_feature>sse2</cpu_feature>
</plan_class>

<plan_class>
<name>armv6-soft-nopie</name>
<min_ncpus>1</min_ncpus>
<projected_flops_scale>0.01</projected_flops_scale>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv6-neon-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>neon</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv6-vfp-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfp</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv7-neon-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>neon</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv3-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv3</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv3d16-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv3</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>thumb-vfpv3d16-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>thumb</cpu_feature>
<cpu_feature>vfpv3</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv4-nopie</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv4</cpu_feature>
<max_android_version>49999</max_android_version>
</plan_class>

<plan_class>
<name>armv6-soft</name>
<min_ncpus>1</min_ncpus>
<projected_flops_scale>0.0001</projected_flops_scale>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv6-neon</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>neon</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv6-vfp</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfp</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv7-neon</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>neon</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv3</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv3</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv3d16</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv3</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>thumb-vfpv3d16</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>thumb</cpu_feature>
<cpu_feature>vfpv3</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv7-vfpv4</name>
<min_ncpus>1</min_ncpus>
<cpu_feature>vfpv4</cpu_feature>
<min_android_version>40100</min_android_version>
</plan_class>

<plan_class>
<name>armv7l</name>
<min_ncpus>1</min_ncpus>
</plan_class>

I read somewhere that the BOINC version that comes with Wheezy does not recognize NEON support on the Pi 2 and so you will end up with applications without NEON support.
If it doesn't work with standard Raspbian Wheezy, what do you need to do to get this working ?
I'll order a Pi 2 the moment I know I can get this working without too much effort.

Thanks,

Tom

There is only one application, it does Optimal function choices and chooses the fastest, so having a Boinc that doesn't detect Neon support doesn't matter:

Work Unit Info:
...............
WU true angle range is : 8.570428
features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)

v_GetPowerSpectrum 0.003416 0.00000 test
vfp_GetPowerSpectrum 0.001395 0.00000 test
neon_GetPowerSpectrum 0.002554 0.00000 test
vfp_GetPowerSpectrum 0.001395 0.00000 choice

v_ChirpData 0.186635 0.00000 test
fpu_ChirpData 0.017552 0.94721 test
fpu_opt_ChirpData 0.207660 0.00000 test
v_ChirpData 0.186635 0.00000 choice

v_Transpose 0.183671 0.00000 test
v_Transpose2 0.099641 0.00000 test
v_Transpose4 0.052981 0.00000 test
v_Transpose8 0.091511 0.00000 test
v_pfTranspose2 0.077891 0.00000 test
v_pfTranspose4 0.049890 0.00000 test
v_pfTranspose8 0.081498 0.00000 test
v_vfpTranspose2 0.088555 0.00000 test
v_pfTranspose4 0.049890 0.00000 choice

FPU opt folding 0.006970 0.00000 test
opt VFP folding 0.006053 0.19453 test
opt NEON folding 0.005141 0.00000 test
opt NEON folding 0.005141 0.00000 choice

Test duration 19.84 seconds

Claggy

I read somewhere that the BOINC version that comes with Wheezy does not recognize NEON support on the Pi 2 and so you will end up with applications without NEON support.
If it doesn't work with standard Raspbian Wheezy, what do you need to do to get this working ?
I'll order a Pi 2 the moment I know I can get this working without too much effort.

Thanks,

Tom

There is only one application, it does Optimal function choices and chooses the fastest, so having a Boinc that doesn't detect Neon support doesn't matter:

Claggy

Thanks, that is great news.
Time to order a Pi 2 !

Tom

And Parallella?

---

News about SETI opt app releases: https://twitter.com/Raistmer

And Parallella?

Running on the Armv7l's on both my Parallellas, and have been for months:

host 74266

host 74287

Claggy

Reported the 'Boinc for Arm on Linux doesn't report the CPU model, only the vendor.' problem to the boinc_dev list (again):

http://lists.ssl.berkeley.edu/pipermail/boinc_dev/2015-July/021851.html

Claggy

Patched Boinc on both my Pi Model B, and Pi 2 with the latest changeset so they both dispay their CPU model.

http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=75533

http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=74138

Who know's how long this will take to reach the repository versions.

Claggy

Is this test still ongoing ?
My Pi 2 is up and running again, but there are no Multibeam tasks available at this moment.

Tom

Is this test still ongoing ?
My Pi 2 is up and running again, but there are no Multibeam tasks available at this moment.

Tom

The Linux Armv7l app is still deployed, Both my Parallellas received work on the 15th.

Claggy

Is this test still ongoing ?
My Pi 2 is up and running again, but there are no Multibeam tasks available at this moment.

Tom

The Linux Armv7l app is still deployed, Both my Parallellas received work on the 15th.

Claggy

I guess a new tape was loaded: tasks are available again !

Tom