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=FbjpWH4PeU6ftxQ8of6rjxhuSAC5b18azz9CVq5rfSw=;
	b=rHah8FCz8GlOqBXXCiGq6SQchiIt0NypFDfInjiCPwE0FrU8YLE+1hrIAFW4bCUBfb
	ygMmrAhkb/1f5uLH7xatDEe+G8eiioc7aGdoq9SkHYvv7NPZkZ2L0xXKuUQEk+8Ys49N
	Q1S3sxYnYBEZHYvsYMoYI3u3lHvoQ8iZkOGqkdqaLhvmCycnAt89gdmMuPby2JSB/8YG
	Rx8NZW7D4HebNs/Z3RfuK98CxwSiLDDi1gJycGJ2fsxkOaVznGkzOybSP/vrFq5foQf5
	dps6+xDSIkbYzF8Y32NZQBsca8TeB1V+HcRbcucmpnL/DHvg3CCm+Z8XY4+1ksMc3GzS
	X4zQ==
MIME-Version:	1.0
In-Reply-To:	<20130115172850.GA5543@recycle.lbl.gov>
References:	<87wqvhd4tw DOT fsf AT gmail DOT com>
	<kd21ao$j6j$1 AT ger DOT gmane DOT org>
	<20130115013756 DOT 9917 DOT qmail AT stuge DOT se>
	<CAOP4iL0yLZ-gvovCy5zCmJyjOXUUaoOB5U1+6CqcD20BM15FiQ AT mail DOT gmail DOT com>
	<50F4E4D1 DOT 3010802 AT ecosensory DOT com>
	<CAOP4iL1f=3TV5UKUjyJtpUw_5oBDxpk=5S2F=dEcUC2UYiNhVQ AT mail DOT gmail DOT com>
	<878v7uv4gl DOT fsf AT gmail DOT com>
	<50F58A89 DOT 1040004 AT ecosensory DOT com>
	<20130115172850 DOT GA5543 AT recycle DOT lbl DOT gov>
Date:	Tue, 15 Jan 2013 10:17:55 -0800
Message-ID:	<CAOP4iL3dF5sjr6WX4AWT79yNuaQ9oa9FR+vVO9Y6RA=txm7x+g@mail.gmail.com>
Subject:	Re: [geda-user] Data Sheets (was: Lowering the cost of a starting a
	gEDA project)
From:	Ouabache Designworks <z3qmtr45 AT gmail DOT com>
To:	geda-user AT delorie DOT com
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

--f46d0408d49de2ae9004d357c7db
Content-Type: text/plain; charset=ISO-8859-1

> On Tue, Jan 15, 2013 at 10:57:45AM -0600, John Griessen wrote:
> > What is a good place to keep datasheets handy for redesign/reuse, and is
> there any optimum
> > compression method for them?  Are there tools that will disassemble
> pdfs, apply
> > best compression, and reassemble them so they are equivalent?  Some are
> compressed more than others.
> > Should we just leave them as their creators published them to be a legal
> document specification?
> > They're almost always public.
>
>

If you create a human readable data sheet then you are requiring that a
human being must take the time to read
it before they can use your part. The IC world to going to machine readable
data sheets with xml files. Instead of
humans writing data sheets for other humans we now have tool flows creating
data sheets for other tool flows.

Right now I can clone a IP repository  for a verilog module into my design
environment and then fire up a ip-xact
editor like kactus2. This gives me a blank sheet where I can enter a
schematic for my design. The module that
I just downloaded will be shown as one of the libraries and I didn't have
to do anything to make that happen. The
tool scans for all xml files and loads the ones that are valid ip-xact
files.

I can select it and it shows the symbol graphic with all pins and types
along with parameters and their default values.
If I click on any of these then I will see a text description. It gives you
about 95% of what you need to plop something
down and hook it up without ever having to look for or read a pdf file.

When I build a netlist it can grab files from the module as well as
handling hierarchy. As you grow and share designs then
you have to start doing things like this.

You of course can have all the stuff that we currently find in data sheets
but these files have pointers in the xml file for
when you need to access that data.


John Eaton





John Eaton

--f46d0408d49de2ae9004d357c7db
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, Jan 1=
5, 2013 at 10:57:45AM -0600, John Griessen wrote:<br>
&gt; What is a good place to keep datasheets handy for redesign/reuse, and =
is there any optimum<br>
&gt; compression method for them? =A0Are there tools that will disassemble =
pdfs, apply<br>
&gt; best compression, and reassemble them so they are equivalent? =A0Some =
are compressed more than others.<br>
&gt; Should we just leave them as their creators published them to be a leg=
al document specification?<br>
&gt; They&#39;re almost always public.<br>
<br>
</blockquote><div><br><br>If you create a human readable data sheet then yo=
u are requiring that a human being must take the time to read<br>it before =
they can use your part. The IC world to going to machine readable data shee=
ts with xml files. Instead of<br>
humans writing data sheets for other humans we now have tool flows creating=
 data sheets for other tool flows.<br><br>Right now I can clone a IP reposi=
tory=A0 for a verilog module into my design environment and then fire up a =
ip-xact<br>
editor like kactus2. This gives me a blank sheet where I can enter a schema=
tic for my design. The module that<br>I just downloaded will be shown as on=
e of the libraries and I didn&#39;t have to do anything to make that happen=
. The<br>
tool scans for all xml files and loads the ones that are valid ip-xact file=
s.<br><br>I can select it and it shows the symbol graphic with all pins and=
 types along with parameters and their default values.<br>If I click on any=
 of these then I will see a text description. It gives you about 95% of wha=
t you need to plop something<br>
down and hook it up without ever having to look for or read a pdf file. <br=
><br>When I build a netlist it can grab files from the module as well as ha=
ndling hierarchy. As you grow and share designs then<br>you have to start d=
oing things like this.<br>
<br>You of course can have all the stuff that we currently find in data she=
ets but these files have pointers in the xml file for <br>when you need to =
access that data.<br><br><br>John Eaton<br><br><br><br><br><br>John Eaton<b=
r>
<br>=A0<br></div></div><br>

--f46d0408d49de2ae9004d357c7db--

- Raw text -