[Coco] 6809 VHDL cores

[jdaggett at gate.net]

James

By portable I mean from various different FPGA vendors and/or to 
ASIC itself. You can make the code specific to a particular FPGA 
and improve gate efficiency. There is nothing wrong in doing that. 
You just have to realize that if you wish to port ot another vendors 
FPGA device. 

If and  when I get onto the chat I will know that I can't use JamesD. 
:)

james

On 20 Aug 2004 at 11:35, James Dessart wrote:

Date sent:      	Fri, 20 Aug 2004 11:35:08 -0400 (EDT)
From:           	James Dessart <james at skwirl.ca>
To:             	CoCoList for Color Computer Enthusiasts 
<coco at maltedmedia.com>
Subject:        	Re: [Coco] 6809 VHDL cores
Send reply to:  	CoCoList for Color Computer Enthusiasts 
<coco at maltedmedia.com>
	<mailto:coco-
request at maltedmedia.com?subject=unsubscribe>
	<mailto:coco-
request at maltedmedia.com?subject=subscribe>

> 
> 
> On Fri, 20 Aug 2004 jdaggett at gate.net wrote:
> 
> > One other note on Jeff Kent's work. The VHDL  has  now become 
> > specific to Xilinx chips. His VHDL code now includes unisim
> > libraries that are specific to Xilinx FPGAs. If you wanted to use
> > Altera or others then the references to  unisim libraries will  have
> > to be rewritten. 
> > 
> > While this is not bad, it does make the VHDL code less portable. 
> 
> Right. Well, there isn't too much difference between the two, as I see
> it. Or is there a difference? I guess it's just the tools available,
> but you can always go with the open source vhdl compilers and the
> like.
> 
> I just noticed, we have the same first name, and the same first letter
> of our last names. I was using JamesD in the coco chat, and I just
> realized that that doesn't differentiate that well between the two of
> us. :)
> 
> James
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco