[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 173: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 174: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Parallella Community Supercomputing for Everyone 2018-11-14T16:22:52+00:00 https://parallella.org/forums/feed.php?f=13 2018-11-14T16:22:52+00:00 2018-11-14T16:22:52+00:00 https://parallella.org/forums/viewtopic.php?t=184&p=20102#p20102 <![CDATA[Programming Q & A • Re: Downloading/Building the SDK and Reporting Issues]]>
/bin/sh ./libtool --tag=CC --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -I/mnt/exp2/buildroot/unisrc-2016.11/bfd/../zlib -fdebug-prefix-ap=/mnt/exp2/buildro
ot=/opt/adapteva/esdk.2016.11/src -O2 -fPIC -rpath /opt/adapteva/esdk.2016.11/tools/e-gnu.armv7l/armv7l-unknown-linux-gnueabihf/epiphany-elf/lib -release `cat libtool-soversion` -static-libstdc++ -static-libgcc -o libbfd.la archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo coff-bfd.lo compress.lo corefile.lo format.lo hash.lo init.lo libbfd.lo linker.lo merge.lo opncls.lo reloc.lo section.lo simple.lo stab-syms.lo stabs.lo syms.lo targets.lo binary.lo ihex.lo srec.lo tekhex.lo verilog.lo `cat ofiles` -ldl -L./../zlib -lz -ldl
./libtool: line 5195: cd: ./../zlib: No such file or directory
libtool: link: cannot determine absolute directory name of `./../zlib'

As far as I can tell this zlib is part of the SDK and not related to my system libraries. Has anyone else run into this or know how to get it fixed?

Statistics: Posted by zmc — Wed Nov 14, 2018 4:22 pm


]]>
2018-10-30T05:56:50+00:00 2018-10-30T05:56:50+00:00 https://parallella.org/forums/viewtopic.php?t=4351&p=20098#p20098 <![CDATA[Programming Q & A • Re: dma and mutex problems - is it worth perservering]]>
That's a pity because if the combination would have been great.

Your post actually explains something else I've seen, a small chunk of data missing at the end of the array after the DMA interrupt has fired.

I'll give your OpenSHMEM a go. I've been (slowly) writing an image processing system for a blog post about COPRTHR-2 but I was reluctant to talk about code that doesn't always work and add a caveat "ignore the DMA - it's flaky".

nick

Statistics: Posted by nickoppen — Tue Oct 30, 2018 5:56 am


]]>
2018-10-29T15:47:13+00:00 2018-10-29T15:47:13+00:00 https://parallella.org/forums/viewtopic.php?t=4351&p=20097#p20097 <![CDATA[Programming Q & A • Re: dma and mutex problems - is it worth perservering]]>
So, I would avoid DMA.

Statistics: Posted by jar — Mon Oct 29, 2018 3:47 pm


]]>
2018-10-23T10:38:09+00:00 2018-10-23T10:38:09+00:00 https://parallella.org/forums/viewtopic.php?t=4351&p=20092#p20092 <![CDATA[Programming Q & A • dma and mutex problems - is it worth perservering]]>
I'm having a final push to get my image processing framework written. I want to have each core processing 1 sixteenth of the image blocked down into work units that will fit inside the core's memory. While one work unit is being processed I want to use dma to transfer the next one so it is available when the processing on the previous one is done. I'm trying to use e_mutex_lock and e_mutex_unlock to coordinate the processing and the dma. My code is here: .

I've posted some questions previously about issues I'm having with dma and there have been some vague mentions of "hardware errata" possibly being responsible for the dma stalling. Now that I'm using e_mutex_(un)lock the problems seem to be getting worse.

I also have noticed that there does not seem to be any examples of e_mutex_lock on git hub or in the parallella examples.

Is it worth persevering with dma and e_mutex?

nick

Statistics: Posted by nickoppen — Tue Oct 23, 2018 10:38 am


]]>
2018-05-10T04:03:23+00:00 2018-05-10T04:03:23+00:00 https://parallella.org/forums/viewtopic.php?t=4289&p=19979#p19979 <![CDATA[Programming Q & A • Re: Updating gcc versions]]> Statistics: Posted by slackmoehrle — Thu May 10, 2018 4:03 am


]]>
2018-04-30T16:15:55+00:00 2018-04-30T16:15:55+00:00 https://parallella.org/forums/viewtopic.php?t=4289&p=19974#p19974 <![CDATA[Programming Q & A • Re: Updating gcc versions]]> Statistics: Posted by olajep — Mon Apr 30, 2018 4:15 pm


]]>
2018-04-29T21:53:25+00:00 2018-04-29T21:53:25+00:00 https://parallella.org/forums/viewtopic.php?t=4289&p=19972#p19972 <![CDATA[Programming Q & A • Updating gcc versions]]> Statistics: Posted by slackmoehrle — Sun Apr 29, 2018 9:53 pm


]]>
2018-04-16T16:08:50+00:00 2018-04-16T16:08:50+00:00 https://parallella.org/forums/viewtopic.php?t=4282&p=19965#p19965 <![CDATA[Programming Q & A • Re: Hi mining coders! Choose ME!]]> Statistics: Posted by cyberneticart — Mon Apr 16, 2018 4:08 pm


]]>
2018-04-13T13:47:01+00:00 2018-04-13T13:47:01+00:00 https://parallella.org/forums/viewtopic.php?t=4061&p=19964#p19964 <![CDATA[Programming Q & A • Re: ePython error on first run for multicore code]]> Statistics: Posted by olajep — Fri Apr 13, 2018 1:47 pm


]]>
2018-04-13T13:28:30+00:00 2018-04-13T13:28:30+00:00 https://parallella.org/forums/viewtopic.php?t=4061&p=19963#p19963 <![CDATA[Programming Q & A • Re: ePython error on first run for multicore code]]> Statistics: Posted by bikasgaur — Fri Apr 13, 2018 1:28 pm


]]>
2018-04-05T15:48:00+00:00 2018-04-05T15:48:00+00:00 https://parallella.org/forums/viewtopic.php?t=4282&p=19962#p19962 <![CDATA[Programming Q & A • Re: Hi mining coders! Choose ME!]]> Statistics: Posted by minerkid — Thu Apr 05, 2018 3:48 pm


]]>
2018-03-22T09:43:52+00:00 2018-03-22T09:43:52+00:00 https://parallella.org/forums/viewtopic.php?t=4254&p=19955#p19955 <![CDATA[Programming Q & A • Re: Atomic operations for synchronizing eCore with shared me]]> Statistics: Posted by upcFrost — Thu Mar 22, 2018 9:43 am


]]>
2018-03-01T14:47:39+00:00 2018-03-01T14:47:39+00:00 https://parallella.org/forums/viewtopic.php?t=4282&p=19943#p19943 <![CDATA[Programming Q & A • Re: Hi mining coders! Choose ME!]]> The codes are for OpenCl processors, not only AMD! We must understand that this OpenCl code could be applied to Epiphany processors. The second link is the most important! Every Cryptonight currencyes are ASICS and GPU resistant (GPU not completely). They made this algo to spare miners over the globe. So, this miner is very good! And in this case is fully OpenCL. Please could you make tests? I am starting this week to make the study on a NanoPi Fire3 that has an OpenCl GPU. Many thanks and I hope that your Epiphany will fly! Ciao!

1) https://en.bitcoin.it/wiki/OpenCL_miner
2) https://github.com/xmrig/xmrig-amd

Statistics: Posted by cyberneticart — Thu Mar 01, 2018 2:47 pm


]]>
2018-02-28T17:11:39+00:00 2018-02-28T17:11:39+00:00 https://parallella.org/forums/viewtopic.php?t=4282&p=19942#p19942 <![CDATA[Programming Q & A • Re: Hi mining coders! Choose ME!]]> Statistics: Posted by cyberneticart — Wed Feb 28, 2018 5:11 pm


]]>
2018-02-28T13:36:20+00:00 2018-02-28T13:36:20+00:00 https://parallella.org/forums/viewtopic.php?t=4282&p=19941#p19941 <![CDATA[Programming Q & A • Re: Hi mining coders! Choose ME!]]>
Do you have a way to measure the power consumption of your current mining setup so we can do a comparison?

Statistics: Posted by zmc — Wed Feb 28, 2018 1:36 pm


]]>