[MeeGo-ivi] Thoughts on hardware and ivi system architacture

[Cory T. Tusar]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/23/2011 06:26 PM, Kevron Rees wrote:
> 2 - We need hardware that is always on.
> 
> In my local setups, I've stopped using bigger, faster hardware in favor
> of speedy-but-low-power solutions.  This hardware stays on 24/7 and can
> stay on for several days without me driving before it will drain the
> battery below the threshold needed to start the engine.  At that point,
> the device can safely sleep until I start the car again.

Not all IVI is automotive-based, though.  Is the assumption that the
hardware can rely on a battery for days between "full power" sessions
truly valid?

As way of background, the last project I was involved with was part of
an IFE (In-Flight Entertainment) system, running a customized Moblin 2.1
(including a sprinkling of the IVI packages).  I'd most definitely
classify it as "IVI", but when the aircraft is not running there's no
auxiliary power source to rely upon (let alone attempt to gracefully go
to sleep).

- --Cory


- -- 
Cory T. Tusar
Senior Software Engineer
Videon Central, Inc.
2171 Sandy Drive
State College, PA 16803
(814) 235-1111 x316
(814) 235-1118 fax


"There are two ways of constructing a software design.  One way is to
 make it so simple that there are obviously no deficiencies, and the
 other way is to make it so complicated that there are no obvious
 deficiencies."  --Sir Charles Anthony Richard Hoare
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk2LSqIACgkQHT1tsfGwHJ/mKgCfTlrVGovE3yFldw7ED0o9hgyf
3OYAn1UHeDUj5cYkGjf/ywEHTpjRQ0Zw
=h3mJ
-----END PGP SIGNATURE-----