X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
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=WxYNXYdgZytSycWf+pFBZw1O8Yj5aSTbA66mcwVOdlU=;
        b=bVuYNMjDYbXJ2NbotY3YjOscUf+M3yT1GadardtbdLVwereOVyFM0XWT/POR31oaPL
         3Jd4Eef8qpjxR0OOl2IVIhiWhLxIK2V9zL+aPkd/+5Zhe761X3xgPJs2ywVLtOEY69ic
         5Tv6wXjIEmZHvxWsNDopQmovCTz1DjWhU4bUe33mG0/hG2nERTs/9g0NJBxAAC4r5ob3
         u/m5OmVHCrPg6tcunV6TlKRIqgxaoctsvHZyLGR464IcuOKP+2UCFnZVunBLQRGEX9QZ
         oueIbNCMggKJp7luO/Xnlxm2XaqHOy+DIp4428LUxRMzwV3FfwRTsV99tMfrCUDs2eaV
         q7tw==
MIME-Version: 1.0
X-Received: by 10.220.43.19 with SMTP id u19mr1183842vce.3.1377751421755; Wed,
 28 Aug 2013 21:43:41 -0700 (PDT)
In-Reply-To: <521DF924.5020406@iae.nl>
References: <521B22D8 DOT 3030707 AT iae DOT nl>
	<CAMvDHVCZm+dYkFrbWoBMbnGvEv_nxr_OG+J3HM5EShhtd6kDBQ AT mail DOT gmail DOT com>
	<521C6317 DOT 7070605 AT iae DOT nl>
	<CAMvDHVCSRjqYw_wm7vO+qbX+bz373S=cvpN2zJ6_ZUC+WdL1bw AT mail DOT gmail DOT com>
	<521C7A68 DOT 1090900 AT iae DOT nl>
	<CAMvDHVD-CK77EbE7-LQUqQS-u0LJquX2U+3xAyr-J7ur8ikF4Q AT mail DOT gmail DOT com>
	<521CA130 DOT 70309 AT iae DOT nl>
	<20130827182849 DOT GA25569 AT localhost DOT localdomain>
	<521DF924 DOT 5020406 AT iae DOT nl>
Date: Thu, 29 Aug 2013 08:43:41 +0400
Message-ID: <CAMvDHVAKYt8KZBHUbwhMpSGktcjgwCkpSaTzdzTKND_rC8pWRg@mail.gmail.com>
Subject: Re: [geda-user] Tutorial: VHDL with gEDA
From: Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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

2013/8/28, myken <myken AT iae DOT nl>:
> On 27/08/13 20:28, Vladimir Zhbanov wrote:
>> Yes, this would be better.
>
> OK I'll do that. BUT I still disagree about your definition of the
> attribute pintype when used in a port symbol.
>
> If pintype=out means it is the output pin of a port symbol, then why are
> oc, oe, pas, tp, tri, clk and pwr defined as valid values according to
> the Master Attribute Documentation in the section "Symbol only
> Attributes"
> (http://wiki.geda-project.org/geda:master_attributes_list#pintype) ?
> What does a Tristate pintype mean if it is attached to a port symbol?

As John already said, the pintype attribute is used not only by vhdl backend.
The drc2 backend uses it to check schematic to prevent user from
connecting inappropriate pins. You can use it in your vhdl
sub-schematic as well. Say, if you connect the output pin of your
ipad symbol to the output of your nand or xor, the drc2 backend
will notify you by outputting an error. This check prevents you
from doing silly or unnoticed errors.

The tristate pintype is hardly provided for the vhdl backend :) I
think this type is unnecessary in this case but can be used to
check other schematics.