[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] ISE Project navigator and ISE files

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] ISE Project navigator and ISE files
Date: Thu, 17 Jan 2008 11:10:03 -0800
User-agent: Mutt/1.5.17 (2007-11-01)

On Thu, Jan 17, 2008 at 12:35:59PM -0600, Jeff Brower wrote:
> Eric-
> > > > We're not using coregen, so that part shouldn't be a problem.
> > >
> > > How do you implement FIFOs, SDRAM controller, GbE MAC, etc?  Using a 
> > > 'non-Xilinx'
> > > method?
> > 
> > We write them in verilog.  We like to avoid vendor specific code when
> > possible, and non-free code like the plague.
> > 
> > We've pulled a fair amount of stuff from opencores.org.  We've found
> > that the quality of code there is highly variable.  Matt's fixed the
> > parts we care about, or found people to fix them.  This includes a GbE
> > MAC, wishbone compatible microblaze knock off (currently running at
> > 50 MHz in a Spartan 3), lots of simple periperals such as I2C, SPI,
> > UART, interrupt controller, etc.  That free software / open source
> > idea really does work ;)
> Ok understand.  Matt's expertise is the key then, patching and fixing as 
> needed. 

And contributing the fixes back.

> Otherwise you'd be dependent on the originators, which as I'm sure you've 
> found they
> can sometimes be less than reliable or in the worst case no longer "findable".

Same as with pretty much anything.  That's why the code's there.

> What about the Microblaze clone... would Xilinx have any issue with that?

Shouldn't be any problem regardless of where we're running it.  
It's a clean-room implementation that executes the same instruction set.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]