<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0">
    <title>Integration Insights</title>
    
    
    <link rel="alternate" type="text/html" href="http://integrationinsights.typepad.com/blog/" />
    <id>tag:typepad.com,2003:weblog-81250500062254859</id>
    <updated>2010-12-15T17:18:00+00:00</updated>
    
    <generator uri="http://www.typepad.com/">TypePad</generator>
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/IntegrationInsights" /><feedburner:info uri="integrationinsights" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://hubbub.api.typepad.com/" /><entry>
        <title>IP Integration :  What is the difference between stitching and weaving?</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/IntegrationInsights/~3/KrE-qmHULEg/ip-integration-what-is-the-difference-between-stitching-and-weaving.html" />
        <link rel="replies" type="text/html" href="http://integrationinsights.typepad.com/blog/2010/12/ip-integration-what-is-the-difference-between-stitching-and-weaving.html" thr:count="2" thr:updated="2011-02-06T21:57:33+00:00" />
        <id>tag:typepad.com,2003:post-6a01310f476968970c01348033e343970c</id>
        <published>2010-12-15T17:18:00+00:00</published>
        <updated>2011-01-27T17:06:15+00:00</updated>
        <summary type="html">As a hardware design engineer, I was never comfortable when someone talked about IP integration as ‘stitching a chip together’. First of all, it sounded like a painful process involving sharp needles, usually preceded by a painful accident. I happened to be the recipient of said stitches when, at 8...&lt;img src="http://feeds.feedburner.com/~r/IntegrationInsights/~4/KrE-qmHULEg" height="1" width="1"/&gt;</summary>
        <author>
            <name>David Murray</name>
        </author>
        
        



    <feedburner:origLink>http://integrationinsights.typepad.com/blog/2010/12/ip-integration-what-is-the-difference-between-stitching-and-weaving.html</feedburner:origLink></entry>
    <entry>
        <title>Automation without abstraction is like a bicycle without pedals</title>
        <link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/IntegrationInsights/~3/sN5HyWX-1qE/aut.html" />
        <link rel="replies" type="text/html" href="http://integrationinsights.typepad.com/blog/2010/11/aut.html" thr:count="0" />
        <id>tag:typepad.com,2003:post-6a01310f476968970c0133f616e9cc970b</id>
        <published>2010-11-19T16:44:03+00:00</published>
        <updated>2010-11-19T16:44:03+00:00</updated>
        <summary type="html">I’ve noticed recently that the word ‘automation’ can be used very loosely in the EDA industry as a presumption of productivity and quality. Here is a quirky take on 'Automation without abstraction'&lt;img src="http://feeds.feedburner.com/~r/IntegrationInsights/~4/sN5HyWX-1qE" height="1" width="1"/&gt;</summary>
        <author>
            <name>David Murray</name>
        </author>
        
        



    <feedburner:origLink>http://integrationinsights.typepad.com/blog/2010/11/aut.html</feedburner:origLink></entry>
 
</feed><!-- ph=1 -->

