<?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: Apple developing both A5X and A6 processors, hints iOS 5.1 code</title>
	<atom:link href="http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/</link>
	<description>Feeding Your Gadget and Tech Obsessions</description>
	<lastBuildDate>Wed, 16 May 2012 12:06:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: First Name</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-193036</link>
		<dc:creator>First Name</dc:creator>
		<pubDate>Mon, 12 Mar 2012 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-193036</guid>
		<description><![CDATA[While that is technically true, you could look at the article history and see that it WASN&#039;T modified in the last 5 minutes.]]></description>
		<content:encoded><![CDATA[<p>While that is technically true, you could look at the article history and see that it WASN&#8217;T modified in the last 5 minutes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CyberGusa</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191484</link>
		<dc:creator>CyberGusa</dc:creator>
		<pubDate>Thu, 08 Mar 2012 00:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191484</guid>
		<description><![CDATA[Sorry again, but it&#039;s no small point I&#039;m making.  Things like power leakage use to be a small issue but that&#039;s no longer the case and as they continue to get smaller they are starting to account for a very large amount of inefficiencies they have to deal with.

Simply redesigning the architecture is no longer enough! You can harp on design flexibility all you want but we&#039;re fast approaching the point that it&#039;s becoming a diminishing factor and advancing the underlying technology is becoming the dominant concern.

While also ignoring how the ARM market works depends on fairly rapid end of life cycles of ARM based products.  So anything that can slow that down is hardly insignificant to the ARM markets.

Add the increasing demand for performance, which ARM is only starting to be able to provide puts more emphasis on how far they can push the technology and only cutting edge then counts, which brings it back to my point.

As it stands, Intel stands to get over a year head start over everyone else in progressing to the next nm reduction and dealing with the issues of each reduction faster to get products out to market and all that adds to market momentum that will increasingly make it harder for ARM to keep up.

Keeping ahead of ARM in this way means they can counter the normal advantages of ARM&#039;s simpler designs and normally lower costs.

Present schedule, assuming no further delays, for ARM is to go 28nm this year, but some companies are already stating they can&#039;t do it yet because there is still too much power leakage to make it worth it.  So the progress is already slowing!

Even if it wasn&#039;t they won&#039;t go 20nm for even low end applications till 2013, when Intel will already have it&#039;s full lineup under 22nm, and 20nm for high end applications that would even compete with Intel&#039;s idea of low end offerings won&#039;t come out until 2014.  But by then Intel will be going 14nm already for again it&#039;s entire lineup.

AMD too is experiencing delays, so using similar facilities obviously doesn&#039;t help, with it&#039;s 28nm update and like many in the ARM camp won&#039;t have much out till the later half of this year.  

While some ARM solutions may not even come out till early next year.  Especially those waiting on some of the next gen parts besides just the ARM cores.

Now while other components are progressing at different rates from the CPU core, that&#039;s another reasons Intel has an advantage as they keep most everything in house and can progress those other parts faster as well.

So don&#039;t underestimate them!]]></description>
		<content:encoded><![CDATA[<p>Sorry again, but it&#8217;s no small point I&#8217;m making.  Things like power leakage use to be a small issue but that&#8217;s no longer the case and as they continue to get smaller they are starting to account for a very large amount of inefficiencies they have to deal with.</p>
<p>Simply redesigning the architecture is no longer enough! You can harp on design flexibility all you want but we&#8217;re fast approaching the point that it&#8217;s becoming a diminishing factor and advancing the underlying technology is becoming the dominant concern.</p>
<p>While also ignoring how the ARM market works depends on fairly rapid end of life cycles of ARM based products.  So anything that can slow that down is hardly insignificant to the ARM markets.</p>
<p>Add the increasing demand for performance, which ARM is only starting to be able to provide puts more emphasis on how far they can push the technology and only cutting edge then counts, which brings it back to my point.</p>
<p>As it stands, Intel stands to get over a year head start over everyone else in progressing to the next nm reduction and dealing with the issues of each reduction faster to get products out to market and all that adds to market momentum that will increasingly make it harder for ARM to keep up.</p>
<p>Keeping ahead of ARM in this way means they can counter the normal advantages of ARM&#8217;s simpler designs and normally lower costs.</p>
<p>Present schedule, assuming no further delays, for ARM is to go 28nm this year, but some companies are already stating they can&#8217;t do it yet because there is still too much power leakage to make it worth it.  So the progress is already slowing!</p>
<p>Even if it wasn&#8217;t they won&#8217;t go 20nm for even low end applications till 2013, when Intel will already have it&#8217;s full lineup under 22nm, and 20nm for high end applications that would even compete with Intel&#8217;s idea of low end offerings won&#8217;t come out until 2014.  But by then Intel will be going 14nm already for again it&#8217;s entire lineup.</p>
<p>AMD too is experiencing delays, so using similar facilities obviously doesn&#8217;t help, with it&#8217;s 28nm update and like many in the ARM camp won&#8217;t have much out till the later half of this year.  </p>
<p>While some ARM solutions may not even come out till early next year.  Especially those waiting on some of the next gen parts besides just the ARM cores.</p>
<p>Now while other components are progressing at different rates from the CPU core, that&#8217;s another reasons Intel has an advantage as they keep most everything in house and can progress those other parts faster as well.</p>
<p>So don&#8217;t underestimate them!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petter</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191398</link>
		<dc:creator>Petter</dc:creator>
		<pubDate>Wed, 07 Mar 2012 22:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191398</guid>
		<description><![CDATA[That is still not much of a point, you can pretty much use any IP on SoC with PPC64-core, MIPS-64-core, SuperH core (granted 32-bit) or whatever. If it was necessary say for an app as network processor in high-end gear. For consumer stuff your not doing anything better then ARM Ltd in the field. In a cheapo server, NAS or appliance whatever you can still cram a 32-bit ARM with 40-bit addressing of memory (ARMv7a and A15 at least) for more memory. That of course also means Intel has to compete against gear with high-end old and new 64-bit microprocessors with tools built up around them. Fabs as some of the mentioned businesses are, do have access to low-level stuff like optimizing transistors and design aspects for the fabrication process and so on even for ARM. Intrinsity now Apple did optimize the Hummingbird SoC physically which did things like minimizing leakage. You don&#039;t need to opt for a static design just because you buy IP.

ARM Companies like Broadcom also has their own MIPS64-implementations.

Won&#039;t be general purpose stuff but it&#039;s quite a bit away from that happening on ARM too.

As most ARM-players use TSMC and their physical IP not much is actually 32nm which TSMC doesn&#039;t produce at all. It&#039;s mostly TSMC 40G. 45nm at some others. You can still make an awful a lot of design choices. Including configuration of FP/SIMD-units and everything not in the actual processor as always. Of course Intel will have some design and fabrication lead, if they choice to, but that don&#039;t really mean Atom will be bleeding edge. 32nm on none-released stuff isn&#039;t that impressive, for that matter Samsung does 32nm on their Exynos-series already that is coming out this year too, so we shouldn&#039;t draw any big conclusions mobile SoCs hasn&#039;t been the first applications to be shrunk at TSMC or other fabs. Neither is there much need. GF does 28nm on ARM too using the same equipment as AMD. TI&#039;s latest designs will of course be 28nm too. It&#039;s pretty bleeding edge in their fields.Intel won&#039;t go 22nm until 2013 sometime here, so at most it&#039;s proven 28nm designs against a new 22nm one. Most don&#039;t have massive 28nm lines up and running trouble free yet, dosen&#039;t mean it is not a good design target when products are rolling out in new consumer products. ARM Ltd themselves are already working towards 14nm but as said it&#039;s not the only resource it that field. They have the rest of the players working for them, it&#039;s not like Intel has all manufacturing capabilities.]]></description>
		<content:encoded><![CDATA[<p>That is still not much of a point, you can pretty much use any IP on SoC with PPC64-core, MIPS-64-core, SuperH core (granted 32-bit) or whatever. If it was necessary say for an app as network processor in high-end gear. For consumer stuff your not doing anything better then ARM Ltd in the field. In a cheapo server, NAS or appliance whatever you can still cram a 32-bit ARM with 40-bit addressing of memory (ARMv7a and A15 at least) for more memory. That of course also means Intel has to compete against gear with high-end old and new 64-bit microprocessors with tools built up around them. Fabs as some of the mentioned businesses are, do have access to low-level stuff like optimizing transistors and design aspects for the fabrication process and so on even for ARM. Intrinsity now Apple did optimize the Hummingbird SoC physically which did things like minimizing leakage. You don&#8217;t need to opt for a static design just because you buy IP.</p>
<p>ARM Companies like Broadcom also has their own MIPS64-implementations.</p>
<p>Won&#8217;t be general purpose stuff but it&#8217;s quite a bit away from that happening on ARM too.</p>
<p>As most ARM-players use TSMC and their physical IP not much is actually 32nm which TSMC doesn&#8217;t produce at all. It&#8217;s mostly TSMC 40G. 45nm at some others. You can still make an awful a lot of design choices. Including configuration of FP/SIMD-units and everything not in the actual processor as always. Of course Intel will have some design and fabrication lead, if they choice to, but that don&#8217;t really mean Atom will be bleeding edge. 32nm on none-released stuff isn&#8217;t that impressive, for that matter Samsung does 32nm on their Exynos-series already that is coming out this year too, so we shouldn&#8217;t draw any big conclusions mobile SoCs hasn&#8217;t been the first applications to be shrunk at TSMC or other fabs. Neither is there much need. GF does 28nm on ARM too using the same equipment as AMD. TI&#8217;s latest designs will of course be 28nm too. It&#8217;s pretty bleeding edge in their fields.Intel won&#8217;t go 22nm until 2013 sometime here, so at most it&#8217;s proven 28nm designs against a new 22nm one. Most don&#8217;t have massive 28nm lines up and running trouble free yet, dosen&#8217;t mean it is not a good design target when products are rolling out in new consumer products. ARM Ltd themselves are already working towards 14nm but as said it&#8217;s not the only resource it that field. They have the rest of the players working for them, it&#8217;s not like Intel has all manufacturing capabilities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191318</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 07 Mar 2012 20:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191318</guid>
		<description><![CDATA[I don&#039;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). ]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191319</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 07 Mar 2012 20:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191319</guid>
		<description><![CDATA[I don&#039;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). ]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191320</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 07 Mar 2012 20:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191320</guid>
		<description><![CDATA[I don&#039;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). ]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191321</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 07 Mar 2012 20:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191321</guid>
		<description><![CDATA[I don&#039;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). ]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t doubt you, myself. But your second sentence made me laugh. The problem with Wikipedia: gimme five minutes and I could make any claim and back it up with a Wikipedia article (that I just modified). </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CyberGusa</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191121</link>
		<dc:creator>CyberGusa</dc:creator>
		<pubDate>Wed, 07 Mar 2012 10:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191121</guid>
		<description><![CDATA[Sorry, but you&#039;re not understanding my point. Doing things like changing the GPU only effects the design of the SoC but doesn&#039;t change the ARM core and other licensed technology.  All of which is pretty much just building blocks that they are working with that the licensees use to make their products.

However, none of that lets them deal directly with things like power leakage, which goes down to the individual components like transistors, and other similar issues as they continue to shrink the manufacturing process and have to overcome the issues of going that small causes. 

Scaling the same architecture down only works so far before you have to make fundamental changes in what is being used in that architecture. 

So the ARM business model doesn&#039;t make it easy to make fundamental changes needed to make it easier to continue shrinking the manufacturing process without also making significant changes to the underlying technology being used.

What ARM is good at is allowing for flexible use of its technology, which allows for easily simplifying of designs, lowering costs, optimizing overall design efficiencies, scaling as needed, adding or removing components as needed, but that&#039;s about it and they&#039;re starting to reach the limits of that benefit.

While collaborating with ARM does help and manufacturers can make some changes on their own and together they&#039;ll eventually deal with such issues as I&#039;m pointing to, but my point was that Intel has a distinct advantage as they don&#039;t have to waste time with any such back and forth when they have full control and can immediately make changes as needed and can even do all R&amp;D in house.  So they can make those changes faster and it&#039;s more in line with Intel&#039;s business model than ARM&#039;s to do so more consistently.

Examples of companies delaying going 28nm and still producing 32nm because of things like power leakage issues, which they specifically said was the issue, shows this is a growing problem for ARM.  Meanwhile Intel is heading towards 22nm and will go down to 14nm in 2014, which is more rapidly than either ARM or even AMD are making their own similar moves to smaller FABs.

Also don&#039;t forget ARM is still 32bit, they may have started employing things like 64bit memory bus but they&#039;re still years away from even sample full 64bit products and that&#039;s another stumbling block they&#039;ll have to deal with as they start to compete more directly with x86 products.]]></description>
		<content:encoded><![CDATA[<p>Sorry, but you&#8217;re not understanding my point. Doing things like changing the GPU only effects the design of the SoC but doesn&#8217;t change the ARM core and other licensed technology.  All of which is pretty much just building blocks that they are working with that the licensees use to make their products.</p>
<p>However, none of that lets them deal directly with things like power leakage, which goes down to the individual components like transistors, and other similar issues as they continue to shrink the manufacturing process and have to overcome the issues of going that small causes. </p>
<p>Scaling the same architecture down only works so far before you have to make fundamental changes in what is being used in that architecture. </p>
<p>So the ARM business model doesn&#8217;t make it easy to make fundamental changes needed to make it easier to continue shrinking the manufacturing process without also making significant changes to the underlying technology being used.</p>
<p>What ARM is good at is allowing for flexible use of its technology, which allows for easily simplifying of designs, lowering costs, optimizing overall design efficiencies, scaling as needed, adding or removing components as needed, but that&#8217;s about it and they&#8217;re starting to reach the limits of that benefit.</p>
<p>While collaborating with ARM does help and manufacturers can make some changes on their own and together they&#8217;ll eventually deal with such issues as I&#8217;m pointing to, but my point was that Intel has a distinct advantage as they don&#8217;t have to waste time with any such back and forth when they have full control and can immediately make changes as needed and can even do all R&amp;D in house.  So they can make those changes faster and it&#8217;s more in line with Intel&#8217;s business model than ARM&#8217;s to do so more consistently.</p>
<p>Examples of companies delaying going 28nm and still producing 32nm because of things like power leakage issues, which they specifically said was the issue, shows this is a growing problem for ARM.  Meanwhile Intel is heading towards 22nm and will go down to 14nm in 2014, which is more rapidly than either ARM or even AMD are making their own similar moves to smaller FABs.</p>
<p>Also don&#8217;t forget ARM is still 32bit, they may have started employing things like 64bit memory bus but they&#8217;re still years away from even sample full 64bit products and that&#8217;s another stumbling block they&#8217;ll have to deal with as they start to compete more directly with x86 products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petter</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-191111</link>
		<dc:creator>Petter</dc:creator>
		<pubDate>Wed, 07 Mar 2012 08:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-191111</guid>
		<description><![CDATA[ Your forgetting that fabs have their own libraries and tools for these ARM-designs though. Hard-macros are foundry tied. Soft-macros can be optimized for different processes and fabs and less common here, but are combined with the actual product of course. Actually collaborating with ARM means actually collaborating with ARM. Something fabless businesses don&#039;t in that regard. Qualcomm and Broadcom has their own GPUs as has Nvidia, others use PowerVR from Img Tec or Mali from ARM for that matter. Also plays into fabrication and so on.]]></description>
		<content:encoded><![CDATA[<p> Your forgetting that fabs have their own libraries and tools for these ARM-designs though. Hard-macros are foundry tied. Soft-macros can be optimized for different processes and fabs and less common here, but are combined with the actual product of course. Actually collaborating with ARM means actually collaborating with ARM. Something fabless businesses don&#8217;t in that regard. Qualcomm and Broadcom has their own GPUs as has Nvidia, others use PowerVR from Img Tec or Mali from ARM for that matter. Also plays into fabrication and so on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CyberGusa</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-190953</link>
		<dc:creator>CyberGusa</dc:creator>
		<pubDate>Tue, 06 Mar 2012 23:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-190953</guid>
		<description><![CDATA[ This is by and large irrelevant since the vast majority are still only licensees and because even those with direct access to manufacturing still don&#039;t have full control.  

ARM Ltd doesn&#039;t work directly with these companies but instead just licenses their technology out to them.  While many of these companies also don&#039;t focus on just the manufacturing of ARM chips but also many other products and all of that means less flexibility on the Fabrication side of things.  Limiting them to what they are set to manufacture and what technology they can license.

This is where Intel can start getting an advantage because they have far more control over their fabrication and can more readily develop their own technology instead of licensing.  Factors like dealing with power leakage as the fabrication gets continuously scaled down is something Intel can deal with better than many of these others working with ARM. 

The normal ARM strengths of being able to be more simply designed to reduce production cost and energy usage are starting to reach their limits and it&#039;s the fabrication process that&#039;s starting to become a more pertinent factor.

Some companies are already delaying the move to 28nm because of concerns over power leakage and production efficiency with ARM and is why we&#039;re still seeing 32nm and larger FABs still being used.

Though on the other hand there are a lot of companies working together on ARM and that&#039;s a significant factor as well but it remains to be seen whether the market fragmentation out weighs its strength in numbers.]]></description>
		<content:encoded><![CDATA[<p> This is by and large irrelevant since the vast majority are still only licensees and because even those with direct access to manufacturing still don&#8217;t have full control.  </p>
<p>ARM Ltd doesn&#8217;t work directly with these companies but instead just licenses their technology out to them.  While many of these companies also don&#8217;t focus on just the manufacturing of ARM chips but also many other products and all of that means less flexibility on the Fabrication side of things.  Limiting them to what they are set to manufacture and what technology they can license.</p>
<p>This is where Intel can start getting an advantage because they have far more control over their fabrication and can more readily develop their own technology instead of licensing.  Factors like dealing with power leakage as the fabrication gets continuously scaled down is something Intel can deal with better than many of these others working with ARM. </p>
<p>The normal ARM strengths of being able to be more simply designed to reduce production cost and energy usage are starting to reach their limits and it&#8217;s the fabrication process that&#8217;s starting to become a more pertinent factor.</p>
<p>Some companies are already delaying the move to 28nm because of concerns over power leakage and production efficiency with ARM and is why we&#8217;re still seeing 32nm and larger FABs still being used.</p>
<p>Though on the other hand there are a lot of companies working together on ARM and that&#8217;s a significant factor as well but it remains to be seen whether the market fragmentation out weighs its strength in numbers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petter</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-190931</link>
		<dc:creator>Petter</dc:creator>
		<pubDate>Tue, 06 Mar 2012 22:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-190931</guid>
		<description><![CDATA[A quite few of the SoC players do have their own factories and silicon fabs, like TI, Fujitsu, ST/ST-E, Freescale, Renesas, Samsung even if not all their products are fabbed at them in house. And that is just ARM application processor SoC&#039;s if you add in MIPS SoCs, ARM MCU SoCs and PPC-SoCs as well as x86 SoCs you also have Toshiba, Sony, NXP Semi, Analog devices, Intel, Infineon and a few other companies. So though they are like Qualcomm, nVidia, Broadcom etc, it&#039;s still not like every other company.]]></description>
		<content:encoded><![CDATA[<p>A quite few of the SoC players do have their own factories and silicon fabs, like TI, Fujitsu, ST/ST-E, Freescale, Renesas, Samsung even if not all their products are fabbed at them in house. And that is just ARM application processor SoC&#8217;s if you add in MIPS SoCs, ARM MCU SoCs and PPC-SoCs as well as x86 SoCs you also have Toshiba, Sony, NXP Semi, Analog devices, Intel, Infineon and a few other companies. So though they are like Qualcomm, nVidia, Broadcom etc, it&#8217;s still not like every other company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: First Name</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188692</link>
		<dc:creator>First Name</dc:creator>
		<pubDate>Tue, 28 Feb 2012 15:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188692</guid>
		<description><![CDATA[For what it&#039;s worth, I&#039;m an electrical engineering and am qualified to write such an article. I only mentioned Wikipedia so that nobody would have to just take my word for it.]]></description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth, I&#8217;m an electrical engineering and am qualified to write such an article. I only mentioned Wikipedia so that nobody would have to just take my word for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188659</link>
		<dc:creator>Guest</dc:creator>
		<pubDate>Tue, 28 Feb 2012 11:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188659</guid>
		<description><![CDATA[Wow, I did not know there were people who proudly reference wikipedia...]]></description>
		<content:encoded><![CDATA[<p>Wow, I did not know there were people who proudly reference wikipedia&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188660</link>
		<dc:creator>Guest</dc:creator>
		<pubDate>Tue, 28 Feb 2012 11:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188660</guid>
		<description><![CDATA[Wow, I did not know there were people who proudly reference wikipedia...]]></description>
		<content:encoded><![CDATA[<p>Wow, I did not know there were people who proudly reference wikipedia&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CyberGusa</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188587</link>
		<dc:creator>CyberGusa</dc:creator>
		<pubDate>Tue, 28 Feb 2012 01:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188587</guid>
		<description><![CDATA[Most mobile chips are SoC now, including the Intel Medfield!  Intel will be even going SoC with their higher end processors.


22nm Silvermont will put all ATOM&#039;s under SoC and Haswell will be the SoC version of the upcoming Ivy Bridge, both coming out 2013.  So hardly exclusive to Apple, never mind ARM has been making SoC&#039;s for longer than Apple has joined them.


Apple just licenses and designs, leaving the actual manufacturing to companies like Samsung.  Just like most other companies that don&#039;t have their own factories.


Regardless, what&#039;s mainly differentiating one generation from the next is still the processor!  While SoC&#039;s also still do not necessarily include everything like Storage drives, WiFi/3G/4G, etc that still varies per system.  So it&#039;s fine to call them processors, when that&#039;s the main part being referred to.]]></description>
		<content:encoded><![CDATA[<p>Most mobile chips are SoC now, including the Intel Medfield!  Intel will be even going SoC with their higher end processors.</p>
<p>22nm Silvermont will put all ATOM&#8217;s under SoC and Haswell will be the SoC version of the upcoming Ivy Bridge, both coming out 2013.  So hardly exclusive to Apple, never mind ARM has been making SoC&#8217;s for longer than Apple has joined them.</p>
<p>Apple just licenses and designs, leaving the actual manufacturing to companies like Samsung.  Just like most other companies that don&#8217;t have their own factories.</p>
<p>Regardless, what&#8217;s mainly differentiating one generation from the next is still the processor!  While SoC&#8217;s also still do not necessarily include everything like Storage drives, WiFi/3G/4G, etc that still varies per system.  So it&#8217;s fine to call them processors, when that&#8217;s the main part being referred to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: First Name</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188490</link>
		<dc:creator>First Name</dc:creator>
		<pubDate>Mon, 27 Feb 2012 19:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188490</guid>
		<description><![CDATA[Intel develops processors. ARM develops processors. Qualcomm develops processors (the Scorpion and Krait CPUs used in Snapdragon are their own design). Apple on the other hand takes stock ARM intellectual property cores developed by ARM Ltd. and puts them on silicon wired up with other peripherals.

Apple develops what are conventionally referred to as &quot;systems-on-a-chip&quot;. The A5 is not a processor, it is a &quot;system-on-a-chip&quot;. Wikipedia!]]></description>
		<content:encoded><![CDATA[<p>Intel develops processors. ARM develops processors. Qualcomm develops processors (the Scorpion and Krait CPUs used in Snapdragon are their own design). Apple on the other hand takes stock ARM intellectual property cores developed by ARM Ltd. and puts them on silicon wired up with other peripherals.</p>
<p>Apple develops what are conventionally referred to as &#8220;systems-on-a-chip&#8221;. The A5 is not a processor, it is a &#8220;system-on-a-chip&#8221;. Wikipedia!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tron Carter</title>
		<link>http://www.slashgear.com/apple-developing-both-a5x-and-a6-processors-hints-ios-5-1-code-27215806/#comment-188485</link>
		<dc:creator>Tron Carter</dc:creator>
		<pubDate>Mon, 27 Feb 2012 19:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=215806#comment-188485</guid>
		<description><![CDATA[Awww hells yeah!  Lets get that going baby.  Can&#039;t wait to find a truck of iPads and then me and my mate Ricky C gonna sell em.]]></description>
		<content:encoded><![CDATA[<p>Awww hells yeah!  Lets get that going baby.  Can&#8217;t wait to find a truck of iPads and then me and my mate Ricky C gonna sell em.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
