Been relying msgs. I am out of my depth on these technical things. Here is Luke's (One of the top Rhombus-Tech people.) thoughts:

-------- Original Message --------
Subject: Re: [Arm-netbook] Fwd: Re: Ya Nanonote
Date: Thu, 28 Feb 2013 00:48:07 +0000
From: luke.leighton <[email protected]>
Reply-To: Linux on small ARM machines <[email protected]>
To: Linux on small ARM machines <[email protected]>

On Thu, Feb 28, 2013 at 12:35 AM, Alexander Stephen Thomas Ross
<[email protected]> wrote:

Werner (One of the top people.) thoughts:

 yeah.  the EOMA modules are not intended to be used as the sole
driver of all peripherals, unless all those peripherals are USB-based
and/or I2C-based.  reasons:
a) limited pin-count of the mass-volume connectors that are being re-used
b) audio and other such interfaces are impossible to pin down.  do you
use AC97?  I2C? I2S? SPDIF? Analog?  if so, how many channels?  what
bit-rates?  what frequencies?
c) primarily with b in mind, a future card with an unknown capability
could simply not have audio (or any other interface not on the list).
therefore, peripherals have to be taken care of by peripheral chips,
or by an Embedded Controller [e.g. the STM32F].

so he's kinda missing the point.  EOMA is a long-term strategy, not an
optimise-the-design-around-a-single-processor strategy.  an EOMA I/O
board and its associated casework and mechanical design could
literally be made for 10 to 15 years and *never* have to be upgraded
*ever*.  the only upgrading that's ever required: the CPU card.

l.

_______________________________________________
arm-netbook mailing list [email protected]
http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook
Send large attachments to [email protected]



_______________________________________________
Qi Hardware Discussion List
Mail to list (members only): [email protected]
Subscribe or Unsubscribe: 
http://lists.en.qi-hardware.com/mailman/listinfo/discussion

Reply via email to