Linked by Thom Holwerda on Mon 11th Nov 2013 22:30 UTC
OSNews, Generic OSes

Tizen holds the promise on shipping on lots of different devices. Samsung has already been shipping the Samsung NX-300M Camera for the last month or so but Today at the Tizen Developer Summit, Samsung has officially announced that this camera is actually running Tizen!

So, Tizen is now shipping... On a camera. On a related note, Samsung has let out some details of Tizen 3.0, planned for next year. It's going 64bit, will gain multiuser support, and will switch from X to Wayland.

Thread beginning with comment 576734
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by sb56637
by ddc_ on Tue 12th Nov 2013 19:21 UTC in reply to "RE[3]: Comment by sb56637"
Member since:

Sure, but any implementation of X11 protocol would be much of overhead for a fullscreen OS, particularly on camera where even 2D acceleration beyond single hardware scaler is clutter.

Reply Parent Score: 3

RE[5]: Comment by sb56637
by tylerdurden on Tue 12th Nov 2013 21:27 in reply to "RE[4]: Comment by sb56637"
tylerdurden Member since:

I think a lot of it has to do with perception. X being bloated was an issue when machines had 8 megs of ram. But I assume the camera is using a fast SOC with plenty of memory, so it makes sense to get things to market quicker and which people can develop for today.

It's not ideal, but the speed of modern silicon buys a lot of latitude.

Reply Parent Score: 5

RE[6]: Comment by sb56637
by twitterfire on Wed 13th Nov 2013 10:21 in reply to "RE[5]: Comment by sb56637"
twitterfire Member since:

But I assume the camera is using a fast SOC with plenty of memory

So we have a decent SOC, what can we do with it? I know, let's make it run slow and make the camera sluggish.

Reply Parent Score: 2

RE[6]: Comment by sb56637
by ddc_ on Wed 13th Nov 2013 14:30 in reply to "RE[5]: Comment by sb56637"
ddc_ Member since:

Oh, you apparently misunderstood me. Let's imagine Samsung developed in-house wonderful power-efficient memory-preserving X11 implementation, which outperforms every other X11 implementation in every aspect. Now, let's be generous and say it only implements a subset of X11. Still, it is a huge waste of camera's processing power, because it doesn't add value to the camera: it doesn't help with focus, color management, lens positioning... It only has to deal with displaying photos, where it doesn't actually help, because all camera needs to display photos is:

1. hardware-accelerated scaler (zoom in/out),
2. hardware-accelerated compositor (a simplistic one, allowing to overlap an image on top of another: osd, button labels, dialogs),
3. specialized DSP (for junk cameras - effects, frames, other similar childish toys; though one used for more or less tricky stuff like autofocus, balance, denoise filter, JPEG optimiser, etc. may be reused here, as it must be otherwise idle at display time).

I believe, Samsung does X11 on this camera not to improve camera, but to improve user experience with camera-related tasks on their phones.

Reply Parent Score: 3