Jon Elson wrote:
> Does anyone know what Paul is talking about here?  Is there any 
> intellectual property that belongs to someone outside the immediate
 > project included in the distributions or CVS?

No.  Copyright for the existing Mesa stuff belongs to either Peter
Wallace or PeteV, and it is all released under the GPL.  Copyright
for the Pluto stuff belongs to Jeff Epler and is released under the
GPL.

 > (I know that .bit files
 > for the Mesa boards are associated with the driver for them.)
> I seriously doubt that these .bit files could be of use with any other 
> maker's chips,

The binary files are chip specific.  The tool licenses prohibit the
binary files from being used with other chips, but place no restriction
on the source (which can be used to create new binaries for other chips).

 > or that any IP could be extracted from them and re-synthesized
 > for other chips.

All the IP in those bitfiles belongs to Pete and/or Pete.

> A VHDL file that
> is synthesized to program the Mesa board's FPGA isn't likely to contain 
> Xilinx's IP, but may
> require something like a PCI macro.

There are no proprietary macros.  The Mesa board uses a separate PLX9030
PCI bus bridge chip to interface to the PCI bus.  It provides a "local" 
bus that connects to the FPGA.  The FPGA contains simple bus interface
logic that is written in plain old VHDL.

As of now, at least 6 to 10 man hours have been spent on this
particular tempest in a teapot.  That is time that would be better
spent improving EMC, in my humble opinion.

Regards,

John Kasunich

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to