<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Intel Is Branching Out With Embedded SoCs</title>
	<atom:link href="http://gigaom.com/2008/07/24/intel-is-branching-out-with-embedded-socs/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/07/24/intel-is-branching-out-with-embedded-socs/</link>
	<description>The Business of Technology</description>
	<pubDate>Thu, 04 Dec 2008 23:39:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tsahi Levent-Levi</title>
		<link>http://gigaom.com/2008/07/24/intel-is-branching-out-with-embedded-socs/#comment-890678</link>
		<dc:creator>Tsahi Levent-Levi</dc:creator>
		<pubDate>Sun, 27 Jul 2008 10:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=15310#comment-890678</guid>
		<description>Tony - Intel are focused on Embedded Linux on their embedded SoC offering.
That said, I am not sure if this is going to be a "common OS" such as Monta Vista Linux or will it be a proprietary embedded Linux version (something they have already done in other embedded processors).
I think that for SoCs to succeed in the coming years, they need to &lt;a href="http://blog.radvision.com/voipsurvivor/2008/07/14/multi-core-for-multimedia-clients-is-all-about-diversification/" rel="nofollow"&gt;diversify what they are capable of doing&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Tony - Intel are focused on Embedded Linux on their embedded SoC offering.<br />
That said, I am not sure if this is going to be a &#8220;common OS&#8221; such as Monta Vista Linux or will it be a proprietary embedded Linux version (something they have already done in other embedded processors).<br />
I think that for SoCs to succeed in the coming years, they need to <a href="http://blog.radvision.com/voipsurvivor/2008/07/14/multi-core-for-multimedia-clients-is-all-about-diversification/" rel="nofollow">diversify what they are capable of doing</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://gigaom.com/2008/07/24/intel-is-branching-out-with-embedded-socs/#comment-890415</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 25 Jul 2008 15:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=15310#comment-890415</guid>
		<description>First off, this "revolution" has been going on for a long time, without Intel's help.

So can Intel succeed?  Maybe, but with what common OS?  The only real common OS that can span all the way from (fairly small) embedded all the way to servers is Linux.  And with Linux, x86 compatibility isn't that important.  (Windows is a family of OS's- WinCE isn't the same OS as Vista; Linux does it with one kernel).

I don't see Windows taking over embedded, either.  So Linux is #1, then Windows, VxWorks, etc.

Many (most?) of these embedded devices will not have a display -- the interface will be through the browser; home routers are an example (and use ARM).  And both the browser is cross-platform and most server tools (e.g. web servers) are cross platform.

I'm also skeptical about the "common user interface" - different tasks should be best with different user interfaces.  Playing music is different from configuring a router.

Finally, I took a quick look at the first Intel SoC.  It does look like a nice chip for high end embedded, but it's nothing remarkable for the industry -- others have been doing this for years.  It does have some interesting features for Intel, such as CAN bus support (which leads some to speculate that Intel is going after the automotive market).  At first glance, it looks like competition for Marvell and such, and I'm not sure Intel can take them on.  Also, "7 years availability" doesn't sound great to me - for embedded, that's not a long time, and the embedded CPU/MPU/MCU/DSP companies typically provide a much longer lifetime (&#62;10 years).  Heck, Freescale is still selling the 68000.</description>
		<content:encoded><![CDATA[<p>First off, this &#8220;revolution&#8221; has been going on for a long time, without Intel&#8217;s help.</p>
<p>So can Intel succeed?  Maybe, but with what common OS?  The only real common OS that can span all the way from (fairly small) embedded all the way to servers is Linux.  And with Linux, x86 compatibility isn&#8217;t that important.  (Windows is a family of OS&#8217;s- WinCE isn&#8217;t the same OS as Vista; Linux does it with one kernel).</p>
<p>I don&#8217;t see Windows taking over embedded, either.  So Linux is #1, then Windows, VxWorks, etc.</p>
<p>Many (most?) of these embedded devices will not have a display &#8212; the interface will be through the browser; home routers are an example (and use ARM).  And both the browser is cross-platform and most server tools (e.g. web servers) are cross platform.</p>
<p>I&#8217;m also skeptical about the &#8220;common user interface&#8221; - different tasks should be best with different user interfaces.  Playing music is different from configuring a router.</p>
<p>Finally, I took a quick look at the first Intel SoC.  It does look like a nice chip for high end embedded, but it&#8217;s nothing remarkable for the industry &#8212; others have been doing this for years.  It does have some interesting features for Intel, such as CAN bus support (which leads some to speculate that Intel is going after the automotive market).  At first glance, it looks like competition for Marvell and such, and I&#8217;m not sure Intel can take them on.  Also, &#8220;7 years availability&#8221; doesn&#8217;t sound great to me - for embedded, that&#8217;s not a long time, and the embedded CPU/MPU/MCU/DSP companies typically provide a much longer lifetime (&gt;10 years).  Heck, Freescale is still selling the 68000.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
