Identifying the Board to BOINC

[Janos]

[Claggy]

Can you post the Boinc startup from the Event log please, the first 30 lines should do.

Claggy

[Janos]

[Claggy]

I assume that was from the Repository, I was hoping Boinc 7.2.42 would be in it, looking at the packages Saucy Salamander gets 7.2.7+dfsg-1,
while Trusty Tahr gets 7.2.42+dfsg-1, I was going to suggest a PPA you could add, but armhf failed to build on it, i'll email LocutusOfBorg later.

I'm thinking that we need (for now) a parallella primary platform, with arm-unknown-linux-gnueabihf (or armv7-unknown-linux-gnueabihf) as alternate,
i'll email the devs later and suggest it.

Claggy

[9600]

[Janos]

[MarkjBOINC]

I have Trusty installed and BOINC 7.2.42. I tried defining the epiphany as coprocessor via cc_config which didn't seem to work. I emailed the alpha mailing list and DA has said he has checked in a fix. He didn't say what so I presume it's in the core client. Unfortunately it might take a while to get it through the repo unless somebody wants to compile their own client on the Parallella.

While it may pass through to project servers we'll still need project apps to add Epiphany support but it's a first step.

[MarkjBOINC]

There is a 7.4.13 BOINC client available from LocutusofBorg's ppa. It now has the ability if you define your own coprocessor to request work for it, so I discovered by accident. I managed to ask Einstein@home for work for an Epiphany16, of course there wasn't any. So it looks like it's telling the project it has a coprocessor now.

The backend plumbing needs to be put in place for it to work and of course we'll need some apps that can use the Epiphany.

As Claggy mentioned they have also been working on OpenCL detection for devices so if Linux can find the OpenCL.so then BOINC should also be able to report that. You'll have to install the OpenCL stuff from Brown Deer to get it though.

MarkJ