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:sender:in-reply-to:references:from:date:message-id :subject:to; bh=5Mu7EtBe6Xni+wsrj9cr8AivdSakg9V0uGTUcsJIbxg=; b=SQQF9NqHubS46eTN4FV1Oom9rnPXdf/R+n9Boh5tAiIZG1gma5ek/p2O6Z96h/thcM lSHjLY/Stub+tgr1sD8druZ9fF7BTNolN8+IBut1X15Xm2oXt+uZ1pzjjOQytCwjDPBG xheynaX6wZQL2FqVebZ1zBtAIRJjxcT8ci2dGhWCePzplx3JqUnW8C9BdatzmTTqnPzd rh4Us7Jo/2Q3GpCRlNc47E3FQMk/auaopdvAVgJA75GATIGCq5TEcqleJYxLb5BLj3eD rvs57zyKOew+MfEdMiF19ixdH2dOXeOef2hV1wgvJ33+E4QVVMiTmgOSpDMHNEHWw39o QR7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=5Mu7EtBe6Xni+wsrj9cr8AivdSakg9V0uGTUcsJIbxg=; b=YQxPw4yBs3JqY30tvsWXyxPl4b6JRxSOicYkMH43nbHpQfQgmaCd4qeaau92iP9qVr M4x8YXJL4ak5Av+VGmQ2wa+CTtZ1KknJFa+aJSFKzn+chH2ExJEIbYm55anBhg48AqRA q3g/zRRxjI2jzFWPqB/67obNbJZ/YDWaFSDh3YI+18wTwTU43WsTWVKJaVjMjm8ES6Nz ljZFWVNFBOQnWFT79YR+eao0+oPspTAlFMUXASByBzQCJ7pS90cy/vfNNpXK9bEudK4H +swmOGCbfxbnACRuotPDEl+OSUQUGy9a8t1G4l6dluMKHiuBW3Hs36nWKAHyTugfEvhC 2VDw== X-Gm-Message-State: AE9vXwOHea4DBssWs191oK/f+1OsH6PGWZR1SuXIcSFXIfm0HTxmwtQW6UXQcDKsfz6AWgM7Y59snN4J1irGwg== X-Received: by 10.36.68.135 with SMTP id o129mr23902866ita.0.1472764963785; Thu, 01 Sep 2016 14:22:43 -0700 (PDT) MIME-Version: 1.0 Sender: svenn DOT bjerkem AT gmail DOT com In-Reply-To: <20160831221409.GA2585@localhost.localdomain> References: <20160823053301 DOT 865f671a1b40b5a422e59ce7 AT gmail DOT com> <20160824185818 DOT GD14293 AT localhost DOT localdomain> <20160831221409 DOT GA2585 AT localhost DOT localdomain> From: "Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com]" Date: Thu, 1 Sep 2016 23:22:43 +0200 X-Google-Sender-Auth: q6Zlm2zRYbTnF77TiM2YdlkurgA Message-ID: Subject: Re: [geda-user] Can an attribute be attached to text for later inclusion in gnetlist backend? To: geda-user 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 On 1 September 2016 at 00:14, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > Svenn, > > On Thu, Aug 25, 2016 at 08:11:26AM +0200, Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: > >> I have so many thoughts about how gschem/gnetlist can help me organize >> "throwaway" testbenches for my vhdl design, but it is all a side >> project to my daily work. >> I am working on my own version of a vhdl back-end, but I am not very >> far at the moment. Learning. > > OK, probably we could work together to make something useful > then. I am going to publish my changes made so far somewhere, so > if you're interested, we could discuss the topic. I can discuss, but I am not good in scheme yet. >> >> I am also looking into choosing top-level attribute names which will >> work the same accross vhdl, verilog and vams backends so that the >> schematic can be used with little modification on different types of >> simulators. > > There are too many different simulators. I believe we could > concentrate on a limited subset, say, spice, verilog and/or vhdl. I noted that the verilog back-end expects the attribute which define the name of the module to build a netlist for to be module-name and the vhdl back-end expects the attribute to be module_name. I don't know what the spice back-end expects. > >> >> My main target is to just create top-level block-type schematics. I am >> not sure gnetlist could handle a "real" hierarchical design. I know >> too little about its capabilities. >> > > If I would know what is "real" hierarchical design... ;-) Yes, > gnetlist has many limitations, though it has some means for > working with hierarchical schematics. I find it hard to describe what makes a design a real hierarchical design other than that a symbol can represent a new schematic filled with symbols which again represent schematics. Kind of the way scheme works recursively into its problem solution. geda users make hierarchical spice netlists all the time, so I am not sure what really is the snag with gnetlist here, but for my most frequent use-case, a schematic will be one level only where each symbol represent a file with vhdl code (or verilog). -- Svenn