<?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: Is hardware customization obsolete?</title>
	<atom:link href="http://www.embeddedinsights.com/channels/2011/09/21/is-hardware-customization-obsolete/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embeddedinsights.com/channels/2011/09/21/is-hardware-customization-obsolete/</link>
	<description>Shedding Light on the Hidden World of Embedded Systems</description>
	<lastBuildDate>Mon, 28 Jul 2014 16:18:37 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: OAZ @ TI</title>
		<link>http://www.embeddedinsights.com/channels/2011/09/21/is-hardware-customization-obsolete/#comment-8379</link>
		<dc:creator>OAZ @ TI</dc:creator>
		<pubDate>Thu, 29 Sep 2011 00:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=634#comment-8379</guid>
		<description>The PC succeeded because it was an open architecture. And I believe in the mobile world this will continue to be true. Not in terms of adding new HW to a device rather than inter-connecting devices using wireless technologies e.g. like M2M or utilizing the cloud. Customization will happen via SW - and the SW needs to be open  .....</description>
		<content:encoded><![CDATA[<p>The PC succeeded because it was an open architecture. And I believe in the mobile world this will continue to be true. Not in terms of adding new HW to a device rather than inter-connecting devices using wireless technologies e.g. like M2M or utilizing the cloud. Customization will happen via SW &#8211; and the SW needs to be open  &#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L.R. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/09/21/is-hardware-customization-obsolete/#comment-8318</link>
		<dc:creator>L.R. @ LI</dc:creator>
		<pubDate>Fri, 23 Sep 2011 05:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=634#comment-8318</guid>
		<description>Robert, you pose a question relating to several trends in the industry, and it is not clear if you need each trend to be individually addressed, or perhaps you are trying to hint that these trends are inter-related?
With regards to the fist observation, with respect to the addition of application-specific peripherals, I completely agree with S. - the trend is still here except that the additions are happening outside of the box, instead of inside. Looking to the future, I think that while USB should satisfy most consumer requirements,external PCIe (including the Thunderbolt variant) is fully capable of accommodating high-end professional peripherals of any conceivable function, including custom-built (e.g. on an FPGA) hardware blocks.
Explaining the reasons for this trend may actually touch on the other trend you mention - the underlying trend is to improve the user experience and reduce the total cost of ownership.
With respect to the extension of system capabilities - in-box customization is prone to mistakes like overloading of the power supply or the overwhelming of the ventilation system, which are very difficult to diagnose in a telephone support call, and thus moving towards outside of the box addition greatly reduces the chance of system failure as a result of such additions (e.g. USB tight power consumption rules and over-current protections), and reduces the difficulty of troubleshooting (and hence reducing TCO).
The trend of consumers moving away from the traditional desktop form factor IMO can be traced to the same motivation - why buy a cow for just a glass of milk ?
Digging even deeper it seems all these trends are rooted in the mass-market adoption of computing devices and is feeding from it. Due to the vastness of the mass-market volume it has become practicable to build devices in a variety of form factors and configurations to fit that particular market segment, instead of selling a base system plus a repertoire of add-on components, essentially as a kit.
Going back a century, to when the radio receiver was gaining acceptance, during the first wave DIY kits were sold to hobbyists, as they were few, but when market adoption has ramped up and demand increased, the manufacturer had to address a much less competent consumer with a more cost-effective product, at a vastly bigger volume.
So this may be all the result of the scaling economies.</description>
		<content:encoded><![CDATA[<p>Robert, you pose a question relating to several trends in the industry, and it is not clear if you need each trend to be individually addressed, or perhaps you are trying to hint that these trends are inter-related?<br />
With regards to the fist observation, with respect to the addition of application-specific peripherals, I completely agree with S. &#8211; the trend is still here except that the additions are happening outside of the box, instead of inside. Looking to the future, I think that while USB should satisfy most consumer requirements,external PCIe (including the Thunderbolt variant) is fully capable of accommodating high-end professional peripherals of any conceivable function, including custom-built (e.g. on an FPGA) hardware blocks.<br />
Explaining the reasons for this trend may actually touch on the other trend you mention &#8211; the underlying trend is to improve the user experience and reduce the total cost of ownership.<br />
With respect to the extension of system capabilities &#8211; in-box customization is prone to mistakes like overloading of the power supply or the overwhelming of the ventilation system, which are very difficult to diagnose in a telephone support call, and thus moving towards outside of the box addition greatly reduces the chance of system failure as a result of such additions (e.g. USB tight power consumption rules and over-current protections), and reduces the difficulty of troubleshooting (and hence reducing TCO).<br />
The trend of consumers moving away from the traditional desktop form factor IMO can be traced to the same motivation &#8211; why buy a cow for just a glass of milk ?<br />
Digging even deeper it seems all these trends are rooted in the mass-market adoption of computing devices and is feeding from it. Due to the vastness of the mass-market volume it has become practicable to build devices in a variety of form factors and configurations to fit that particular market segment, instead of selling a base system plus a repertoire of add-on components, essentially as a kit.<br />
Going back a century, to when the radio receiver was gaining acceptance, during the first wave DIY kits were sold to hobbyists, as they were few, but when market adoption has ramped up and demand increased, the manufacturer had to address a much less competent consumer with a more cost-effective product, at a vastly bigger volume.<br />
So this may be all the result of the scaling economies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S.A. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2011/09/21/is-hardware-customization-obsolete/#comment-8312</link>
		<dc:creator>S.A. @ LI</dc:creator>
		<pubDate>Thu, 22 Sep 2011 16:08:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=634#comment-8312</guid>
		<description>The availability of robust external interfaces, particularly USB but also including Firewire, eSATA and so on, has been one factor in this move away from internally-bussed hardware devices. Also, there are now higher levels of integration of devices on the motherboard - for example, a one-chip solution that integrates 802.11 a/b/g/n and Bluetooth is easily integrated. Depending on the application, the wireless capabilities of the device may be all you need to connect to peripherals. 

In those examples, the driver architecture is often greatly simplified. For example, if you have a low-speed I/O device, it may be possible to simply use the USB HID interface and avoid needing a device-specific driver altogether.

But for high bandwidth or low-latency I/O, plugging into a board-level bus (like one of the PCI flavors) seems like it won&#039;t be going away any time soon?</description>
		<content:encoded><![CDATA[<p>The availability of robust external interfaces, particularly USB but also including Firewire, eSATA and so on, has been one factor in this move away from internally-bussed hardware devices. Also, there are now higher levels of integration of devices on the motherboard &#8211; for example, a one-chip solution that integrates 802.11 a/b/g/n and Bluetooth is easily integrated. Depending on the application, the wireless capabilities of the device may be all you need to connect to peripherals. </p>
<p>In those examples, the driver architecture is often greatly simplified. For example, if you have a low-speed I/O device, it may be possible to simply use the USB HID interface and avoid needing a device-specific driver altogether.</p>
<p>But for high bandwidth or low-latency I/O, plugging into a board-level bus (like one of the PCI flavors) seems like it won&#8217;t be going away any time soon?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
