Re: [Fx2lib-devel] Change sync delay macro

[-t <tg...@ya...>]

Date: Thu, 03 Mar 2011 09:27:36 -0700
From: Dennis Muhlestein <djm...@gm...>
Subject: Re: [Fx2lib-devel] Change sync delay macro (Daniel O'Connor)
To: fx2lib developer mailing list <fx2...@li...>
Message-ID: <4D6...@gm...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


>
> To be honest, after using the GPIF designer a few times I was sorely tempted to 
>write a bunch of macros to generate the GPIF data words :-/
>

After using the gpif a bit, my impression was that everyone switched to 
slave fifo :).  

...

So, to make along story short: Slave fifo solved the issue.


>
>GPIF is used when the peripheral interface bus needs to be mastered.  I have not 
>come across a better programmable parallel bus interface implementation than 
>GPIF for bus mastering.  It is true that GPIF adds an additional layer on top of 
>the Slave FIFO interface, and in doing so has more limitations.  These 
>limiations are rarely a show-stopper.  When these limitations are hit, 
>they're usually because the peripheral is already a bus master.  Flowstate is an 
>additional layer on top of GPIF, and in my opinion is only useful for UDMA 
>intefacing.  Flowstate sounds cool, attracts EVERYONE - just pulls them right 
>in, and 99% of the time is not a good fit to solve other interfacing needs, 
>again this is my opinion.  Tip:  Only use Flowstate for UDMA interfacing.  I've 
>designed peripheral interfaces with GPIF and Slave FIFO on and off for more than 
>a decade now, and have never failed to provide a fully functional interface.  
>Please feel free to ping me if you ever need help with GPIF and / or Slave 
>FIFO.  
>
>
>P.S. I use the older GPIFTool utility :)