There are a few footprints at gedasymbols.org like
Element[90551 110236 0 0 0 100 ]
(
Pin[0 0 5300 2000 5900 2400 1 edge2]
Pin[19213 0 5300 2000 5900 2400 2 edge2]
ElementLine [-12992 -5512 -12992 5512 1000]
ElementLine [-9055 9449 27953 9449 1000]
Stephen Williams wrote:
Question:
Does *anybody* use or even see value in the 32bit runtime support
that Icarus Verilog includes in 64bit builds? In particular, there
is support in the Icarus Verilog source for building simultaneously
a vvp (64bit) and a vvp32 (32bit) to support 32bit VPI's
Günter Dannoritzer wrote:
Stephen Williams wrote:
Question:
Does *anybody* use or even see value in the 32bit runtime support
that Icarus Verilog includes in 64bit builds? In particular, there
is support in the Icarus Verilog source for building simultaneously
a vvp (64bit) and a vvp32
Stephen Williams wrote:
Günter Dannoritzer wrote:
Hi,
I am looking into using Icarus Verilog with Teal/Truss, a C++ based
verification framework.
With Icarus 0.8.6 all tests but the last, with release of a_wire, are
working.
It's probably a matter of it not being implemented yet. Looks
On Jan 25, 2008 7:38 AM, Günter Dannoritzer [EMAIL PROTECTED] wrote:
Well, I will be honest with you. Trying to figure out truss/teal I am
still finding some other problems of the software itself that makes me
not succeed using it. So for now I can live with using it with the
stable version of
I have newer seen these Attribute() entries before -- is this new
and is there documentation about it?
I put support in for that a while back... August 2006.
It's documented in the usual pcb documentation.
You can put attributes at board-level too.
6 matches
Mail list logo