X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=t59P9KklEqAOLoK4VujxA7+EVxiXYQk3/Ewe3RtPUOU=;
        b=OxIOHBfywv4S0r3kgatv8p4eoIe2BZDB09XtStqkHCM9w/bcv75Ji6knmxRhsKBP1C
         QmhTDzKxcX+PLBS/0eCAVi97tdbqaACgsGfC257Y/5wqaQvFhd12R4MmxM9qHVGmQcNO
         sj7Yp0QKGhPBLRe5AdrEVH5abDxYkJR4H86X+lHCcWIus/uugOz8M197SGyuvi6GbbXM
         VzbnqfESTyROPr3VU3W0fsSudQtNlrN1h3FdVYkppnWYPsVs1UDAOC53mUueqLCMcw3y
         hEQVD6uzNj4iaKHufODXZllYFVk6N9oteCAHRNplNIThdz0nXuEVhwnw4owZM3sRc7fq
         AiEg==
MIME-Version: 1.0
X-Received: by 10.50.17.104 with SMTP id n8mr35287812igd.21.1434035971623;
 Thu, 11 Jun 2015 08:19:31 -0700 (PDT)
In-Reply-To: <CAPDh1TpHFo20SxAGi2bHRDbSWP21r_ec+Yaw07dKmrnjKBYnGA@mail.gmail.com>
References: <CAOP4iL2RenFM9yxVhc_fkmPmzBa9iXRFH2uUvfEuGC_qMY17Jw AT mail DOT gmail DOT com>
	<CAPDh1To9cjhR-zJpsJCL68cWiSTMQDJ-jvnrGLwR_-qp6+r+Tg AT mail DOT gmail DOT com>
	<20150608222056 DOT 10601 DOT qmail AT stuge DOT se>
	<CAPDh1TqwQOtyh0jQjEMzF-pg6wzXVJ2rSCZEHh7-xvUqNWRdLQ AT mail DOT gmail DOT com>
	<218C63C4-B2B5-4DFB-A995-B170E7591B6F AT noqsi DOT com>
	<CAOP4iL19A9+7589oo0ctfeznW=TC-8MVsaw_6sjwLXRU1xjEDg AT mail DOT gmail DOT com>
	<CAPDh1TpHFo20SxAGi2bHRDbSWP21r_ec+Yaw07dKmrnjKBYnGA AT mail DOT gmail DOT com>
Date: Thu, 11 Jun 2015 08:19:31 -0700
Message-ID: <CAOP4iL1Gmxbr=axpvYwTZxxoKGMvhQaGoK-W2JMAnFVu9eREBg@mail.gmail.com>
Subject: Re: [geda-user] Any news about FOSS EDA coordination? Import/export,
 common file format
From: "Ouabache Designworks (z3qmtr45 AT gmail DOT com)" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e0118398aaf10ad05183f8485
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

--089e0118398aaf10ad05183f8485
Content-Type: text/plain; charset=UTF-8

On Wed, Jun 10, 2015 at 11:29 PM, timofonic timofonic (timofonic AT gmail DOT com)
<geda-user AT delorie DOT com> wrote:

> What's wrong with IP-XACT?
>

It was created by the spirit consortium that was made up from engineers
from eda tool vendors, IP houses and Si vendors. Correct me if I am wrong
but I don't think that they had anyone on the committe who's day job
actually involved designing IC's.  The biggest complaint is that to use it
you have to use vendorExtensions to do anything useful and once you add
that you have the same old problem that EDIF had with each vendor having
their own "flavor" of IP-Xact.

My biggest grip was that they don't support design variants that are
critical in IC design. They support parameters but parameters cannot change
a port list or a file list. If your
design variant needs to change either of those then you are out of luck.

IP-Xact has seen some adoption as a way to describe register bits with
tools that read an IP-Xact component file to generate the RTL,documentation
and head files for those registers. But it is capable of doing a lot more
than that.

I see IP-Xact as a case of pulling defeat from the jaws of victory.  It has
some really great features that are usefull. For example if you add one
IP-Xact file into your IP repository then that will provide  a unique
identifier for your IP. No other repo in the world will have that same id,
no more naming collisions.

IP-Xact is a packaging standard that does not tell you how to package
anything at all. They knew that nobody was going to adopt it if they had
change anything in their legacy IP so that all you have to do is to add an
IP-Xact file anywhere in your legacy repos and they will be IP-Xact
compliant.


John Eaton

--089e0118398aaf10ad05183f8485
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jun 10, 2015 at 11:29 PM, timofonic timofonic (<a href=3D"mailt=
o:timofonic AT gmail DOT com">timofonic AT gmail DOT com</a>) <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">Wha=
t&#39;s wrong with IP-XACT?</p></blockquote><div><br></div><div>It was crea=
ted by the spirit consortium that was made up from engineers from eda tool =
vendors, IP houses and Si vendors. Correct me if I am wrong but I don&#39;t=
 think that they had anyone on the committe who&#39;s day job=C2=A0 actuall=
y involved designing IC&#39;s.=C2=A0 The biggest complaint is that to use i=
t you have to use vendorExtensions to do anything useful and once you add t=
hat you have the same old problem that EDIF had with each vendor having the=
ir own &quot;flavor&quot; of IP-Xact. <br><br></div><div>My biggest grip wa=
s that they don&#39;t support design variants that are critical in IC desig=
n. They support parameters but parameters cannot change a port list or a fi=
le list. If your<br></div><div>design variant needs to change either of tho=
se then you are out of luck.<br><br></div><div>IP-Xact has seen some adopti=
on as a way to describe register bits with tools that read an IP-Xact compo=
nent file to generate the RTL,documentation and head files for those regist=
ers. But it is capable of doing a lot more than that.<br><br></div><div>I s=
ee IP-Xact as a case of pulling defeat from the jaws of victory.=C2=A0 It h=
as some really great features that are usefull. For example if you add one =
IP-Xact file into your IP repository then that will provide=C2=A0 a unique =
identifier for your IP. No other repo in the world will have that same id, =
no more naming collisions.<br><br></div><div>IP-Xact is a packaging standar=
d that does not tell you how to package anything at all. They knew that nob=
ody was going to adopt it if they had change anything in their legacy IP so=
 that all you have to do is to add an IP-Xact file anywhere in your legacy =
repos and they will be IP-Xact compliant.<br><br><br></div><div>John Eaton<=
br><br></div><div><br><br></div><div><br></div><div><br></div><div><br><br>=
<br></div></div></div></div>

--089e0118398aaf10ad05183f8485--