Index: trunk/doc/design/07_devmap.html =================================================================== --- trunk/doc/design/07_devmap.html (revision 271) +++ trunk/doc/design/07_devmap.html (revision 272) @@ -6,7 +6,7 @@ Device mapping is a generic mechanism for detaching schematics symbols from footprints and simulation models. It allows:
{des7:0} In the above example v_plus and v_minus are never prefixed with "slot/" because -of their noslot attribute. In case the symnbol is used with the slot attribute +of their noslot attribute. In case the symbol is used with the slot attribute set, this means:
{imp7:0} While both of the above solutions would work with cschem, it is recommended -to use the devmap mechanism instead. For the 2n7002-in-sot23 example, the decmap +to use the devmap mechanism instead. For the 2n7002-in-sot23 example, the devmap would mean:
{imp7:0} However, this again creates bad coupling: for PCB, the devmap file name includes the footprint, because that makes the actual binding between the -generic symbol and generic footprint. This mean there would be a differnet -devmap file for the same mosfet part coming in a to92 package. Yet, the spice +generic symbol and generic footprint. This mean there would be a different +devmap file for the same MOSFET part coming in a to92 package. Yet, the spice model attribute and pin mapping would be copied into both.
{imp7:0} @@ -173,7 +173,7 @@ but can be text, e.g. "power", "gpio", "i2c".
{imp7:0} -Instead of the somewhat cryptic slotdef atribute, the devmap file contains +Instead of the somewhat cryptic slotdef attribute, the devmap file contains a more readable table of pin assignment.