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
         :cc:content-type;
        bh=0/sGn7R1zF3JMdT6ZqeMTZxF6Y9Q9K723Iohmms43Sg=;
        b=cgEn8/lD2yhM7V7sgLJC5FEv7nSMK5ny4yqs8vH0HKyuZyS3PftE4+SzOsf14xYolV
         LcLoDmhJ4H8daAZ0Sdi9ie4ZtXauF1X+hxAC8LbtjGFTmcPGUWql4omR0vPVvIL4N+WE
         mm2SVb48Yzt90GAkkXq96UzEl9nVcWgb5gj/dLUuufH0NvpNZF4Ah3m615o0U9+EYJbh
         UorN82BwLdzT3U2NUgKpwtkE2HWqM7KHCrB6ytDGvi9A2Jb6uIEULSSSNIxaJBYRQqDG
         /JEcuyI+1lHempKpOyBSHS0zRWdQTdN4aNUKKtHPapAEhSCkxVCJKBZiUL0o45KcZ5mO
         GLYQ==
MIME-Version: 1.0
X-Received: by 10.42.175.74 with SMTP id az10mr8340299icb.55.1434289221828;
 Sun, 14 Jun 2015 06:40:21 -0700 (PDT)
In-Reply-To: <CAOP4iL1Gmxbr=axpvYwTZxxoKGMvhQaGoK-W2JMAnFVu9eREBg@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>
	<CAOP4iL1Gmxbr=axpvYwTZxxoKGMvhQaGoK-W2JMAnFVu9eREBg AT mail DOT gmail DOT com>
Date: Sun, 14 Jun 2015 15:40:21 +0200
Message-ID: <CAPDh1TrZoMxNhUF7qdVa9wqrA0iB4dda=42Giq_ZJBpdaW5wQg@mail.gmail.com>
Subject: Re: [geda-user] Any news about FOSS EDA coordination? Import/export,
 common file format
From: "timofonic timofonic (timofonic AT gmail DOT com)" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Cc: foss-pcb AT ohwr DOT org,
        The Open Source Hardware Association Discussion List <discuss AT lists DOT oshwa DOT org>,
        kicad-users AT yahoogroups DOT com
Content-Type: multipart/alternative; boundary=485b397b947d9287a805187a7bad
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

--485b397b947d9287a805187a7bad
Content-Type: text/plain; charset=UTF-8

Oh, the idea looked promising...

So what about kicad and geda supporting both formats at least? What about
sharing the same library? :)
On Jun 11, 2015 5:27 PM, "Ouabache Designworks (z3qmtr45 AT gmail DOT com)" <
geda-user AT delorie DOT com> wrote:

>
>
> 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
>
>
>
>
>
>
>
>
>

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

<p dir=3D"ltr">Oh, the idea looked promising...</p>
<p dir=3D"ltr">So what about kicad and geda supporting both formats at leas=
t? What about sharing the same library? :)</p>
<div class=3D"gmail_quote">On Jun 11, 2015 5:27 PM, &quot;Ouabache Designwo=
rks (<a href=3D"mailto:z3qmtr45 AT gmail DOT com">z3qmtr45 AT gmail DOT com</a>)&quot; &l=
t;<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>&gt; wr=
ote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jun=
 10, 2015 at 11:29 PM, timofonic timofonic (<a href=3D"mailto:timofonic AT gma=
il.com" target=3D"_blank">timofonic AT gmail DOT com</a>) <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">=
What&#39;s wrong with IP-XACT?</p></blockquote><div><br></div><div>It was c=
reated by the spirit consortium that was made up from engineers from eda to=
ol vendors, IP houses and Si vendors. Correct me if I am wrong but I don&#3=
9;t think that they had anyone on the committe who&#39;s day job=C2=A0 actu=
ally involved designing IC&#39;s.=C2=A0 The biggest complaint is that to us=
e it you have to use vendorExtensions to do anything useful and once you ad=
d that you have the same old problem that EDIF had with each vendor having =
their own &quot;flavor&quot; of IP-Xact. <br><br></div><div>My biggest grip=
 was that they don&#39;t support design variants that are critical in IC de=
sign. They support parameters but parameters cannot change a port list or a=
 file list. If your<br></div><div>design variant needs to change either of =
those then you are out of luck.<br><br></div><div>IP-Xact has seen some ado=
ption as a way to describe register bits with tools that read an IP-Xact co=
mponent file to generate the RTL,documentation and head files for those reg=
isters. But it is capable of doing a lot more than that.<br><br></div><div>=
I see IP-Xact as a case of pulling defeat from the jaws of victory.=C2=A0 I=
t has some really great features that are usefull. For example if you add o=
ne IP-Xact file into your IP repository then that will provide=C2=A0 a uniq=
ue identifier for your IP. No other repo in the world will have that same i=
d, no more naming collisions.<br><br></div><div>IP-Xact is a packaging stan=
dard 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 lega=
cy repos and they will be IP-Xact compliant.<br><br><br></div><div>John Eat=
on<br><br></div><div><br><br></div><div><br></div><div><br></div><div><br><=
br><br></div></div></div></div>
</blockquote></div>

--485b397b947d9287a805187a7bad--