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=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=OO0d7jCw2Gks9JCgtVuU/irFi0fRQjTWA92+UdT3PuE=;
	b=wUO/EI9bkLDmyxBW2HXFlm7zmgcT2a/iTSGgfS+hpnjEU5LYIX3m2mzxPALt2cPVPB
	UqFf1gffXelT5jBsCR+YZZZ7TwITG8lBlDtLD6xXY6PK35lNLG1drztsAHUy+7L6lzZm
	ehYltJNXGLTG+RcL2hBAzXuiPmOZZs9ll2Tv2/SuYc1n8OLJA+r0p1ABa8CEDyGffwPv
	eU6fyedcrRqb1mPqqLsD7IEsPNdVGWKV+VX6SL2eCVU0wRd8MGHV78wMNtEPmlIAt8T+
	5wQpG1jWQ1oFn71cV50Tq9ebRvg3DiNRkuBpqyi+yYwgs7Eqw0pgsom/4K00b8FXdXIG
	mbZQ==
X-Received:	by 10.180.93.2 with SMTP id cq2mr2284464wib.33.1445324404766;
	Tue, 20 Oct 2015 00:00:04 -0700 (PDT)
Date:	Tue, 20 Oct 2015 09:00:03 +0200
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Pin mapping (separate symbols from mappings)
Message-Id:	<20151020090003.0e5c20774c7809ff84d3021a@gmail.com>
In-Reply-To:	<n04bl6$i90$1@ger.gmane.org>
References:	<20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com>
	<201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com>
	<20151018233004 DOT 78db1f9df1b1e68325c8639e AT gmail DOT com>
	<n03l6g$91u$1 AT ger DOT gmane DOT org>
	<AA4348BC-542E-469B-8FF1-A45009327ED3 AT noqsi DOT com>
	<n04bl6$i90$1 AT ger DOT gmane DOT org>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> >> IMHO, the missing part in the puzzle is the notion of a "package"
> >> which delivers all information specific to a physical component. I
> >> deliberately did not write "contain" but "deliver". The package may
> >> include footprints viable for this component. Alternatively the
> >> package may refer to a footprint library by giving filenames of a
> >> footprints known to work. Which of the two is the most appropriate
> >> depends on circumstances. Therefore, the choice between inclusion
> >> or reference is up to the designer of the library of packages.
> > 
> > But now you’re tangling upstream and downstream. How the footprint
> > library works depends on the layout tool.
> > 
> A package provides a way to store all information related to a 
> specific hardware component. It can be queried/read by any EDA tool. 
> This includes  applications for schematic capture, netlisters, layout  
> tools, BOM creators, simulation tools, documentation assemblers, 3D 
> modelers, and whatnot. So the terms "upstream" and "downstream" are 
> meaningless with regard to the library of packages.

A package provides a way to store all information related to a specific hardware component and since this information is not known at the start of drawing this linking information should be added later in the process.

Then the symbol is added in gschem package and value is usually not decided although it may be implicitly given for some integrated circuits and in such case default attribute values are useful.

Nicklas Karlsson

- Raw text -