X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <521BB96B.5090807@gmx.com> Date: Mon, 26 Aug 2013 13:24:11 -0700 From: Jan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Tutorial: VHDL with gEDA References: <521B22D8 DOT 3030707 AT iae DOT nl> <1377531768 DOT 2150 DOT 11 DOT camel AT AMD64X2 DOT fritz DOT box> <521B8AD4 DOT 4020000 AT iae DOT nl> In-Reply-To: <521B8AD4.4020000@iae.nl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FJsVeMgWpdGe8tRGVElxzaYApVJuvkpOgoPG2hIjRrG46iEiuJD ZlatM1WCHJbQhiRVlOUAwCHcAAPt50rouaA0d9kZRBNLWj1STWR4lKD9Yqj08EOHEXNfvR3 jd0fGUJzSKt8I0WSJQkKk1EjHQ3C2nwr62dmSeYvyR6cTnV1uGRzfSicGX8kv7zmHreX5CY 5AapDDGH1SxerHzFwiHLA== Reply-To: geda-user AT delorie DOT com Myken, thanks for the effort, I will use this when I have time to do so. It looks great so far. Just a reminder, spell check doesn't catch grammar errors which can become quite important for translations. Let us know when you think your tutorial is ready for prime time! I've also found on several separate gEDA installs gafrc doesn't work for homemade symbols, I've always had to add my own stuff directly to the main symbol libraries in order for my existing schematics to display properly. Which leads me to think gafrc doesn't work at all. Perhaps you could explore this in your tutorial, maybe it's a bug that's been around for a long time? On 08/26/2013 10:05 AM, myken wrote: >> Fine -- indeed I was wondering in the last weeks what you was doing with >> gEDA and VHDL -- my initial guess was that you tried to generate >> schematics from VHDL code. > You are absolutely right. That was/is my primary trigger. But first I > had to figure out how the gschem to VHDL path works. So why not let > everybody profit from my work ;-) > Unfortunately I got stonewalled by the way gschem/gnetlist (VHDL > backend) handles buses. I haven't solved that one. >> Maybe you should start your tutorial indeed with a short remark what you >> intend -- starting with statements about bugs is very negative in > Good point. I'll add an introduction. >> general. And from my knowledge the way schematic -> VHDL is not very >> common, VHDL was invented to allow textual input, maybe generate >> schematic output for verifying the result. Of course the direction >> schematic VHDL may be justified, i.e. for very special digital >> circuits. > Oh really? I usually use the schematics to define the architecture or > communicate about the architecture and fill in the working block > later. But I guess that makes me special :-) >> I had only a short look at your page -- is my impression wrong that your >> general used font is smaller than the users default? > It should not be. I'll test it on an other machine later tonight. > >