[PStamatiou]

As a hobbyist photographer this definitely sounds interesting in terms of allowing more control over the camera (especially automated uses, build your own timelapse, get past the 30s long exposure instead of having to buy a $150 canon timer remote, et cetera). But doing anything with image manipulation and transfer (maybe there's a reason Eye-fi hasn't moved into the DSLR space -- no CF version, only Class 6 speeds) seems like a daunting task for the pi..

For those more familiar with the Raspberry Pi, does it actually have enough performance to move big RAW files around? A 5D3 will output ~30MB RAWs and in a shoot you may end up with 500+ of them. Having a Pi transfer/move/adjust them sounds like a slog.

[sliverstorm]

The Pi does about 10MB/s over the network, I believe.

As for image manipulation, sadly, the Pi is fairly fast by embedded standards, but running general-purpose software on a full-blown OS takes a lot away.

For comparison, the original Xbox used an x86 of the same clock speed.

[archivator]

> running general-purpose software on a full-blown OS takes a lot away

Which is why we any predefined image manipulation should avoid the ARM core and jump straight to the rather powerful GPU. I think it even supports OpenCL, so there should be software out there that could work with it.

[sitkack]

The GPU on the Pi can't/won't support OpenCL. That doesn't stop one from writing a GPGPU program in GLSL.

[polshaw]

    >For comparison, the original Xbox used an x86 of the same clock speed

which is fairly useless as a point of comparison, as not only is it the completely different arm architecture, but it is also Arm V6 (arm11), whereas even our smartphones have been arm v7 (cortex A8, A9, A15) for the last couple of years. If i had to equate it to an x86 clock speed, i'd say 400mhz was possibly a fraction generous.

[sliverstorm]

Sure, they aren't the same, but they ought to be in the same ballpark.