[Open-graphics] Mad dash to finish VGA -PCI info
Josephblack
josephhenryblack at gmail.com
Fri Dec 7 02:31:34 EST 2007
On 07/12/2007, Timothy Normand Miller <theosib at gmail.com> wrote:
snip
> Optimizing too early just makes it an incomprehensible mess. Now, PCI
> is an extreme case, because I had to force restructuring of the logic
> in ways that ISE would not have done voluntarily. Xilinx even told
> me, when I opened a web case, that my manual MUX approach was about
> the best I was going to do. But it's nasty. Instead of burying
> selections in the logic in a way that makes semantic sense.... well,
> let me be clearer....
>
> There are, I believe, 3 or 4 different inputs from PCI that we cannot
> register because we need to use the signals directly on a given cycle.
> These include #STOP and #IRDY. Let's say we have an internal state
> or output or whatever that depends on those two. What I had to do was
> design logic to generate what the state would be for each of the four
> possible combinations of those signals, force ISE to generate logic
> for those, and then MUX those based on the inputs. It's vital to use
> those inputs at the absolute last stage of the logic. Since they're
> coming in from the PCI bus, there's already a huge delay on them.
> (Out from the driver, delay on the bus, ad input buffers in our FPGA.)
> There were cases where I had to MUX 8 different possibilities. IIRC,
> it wasn't any worse than that, although it will be when we do the
> Master.
>
>
> --
> Timothy Normand Miller
> http://www.cse.ohio-state.edu/~millerti
> Open Graphics Project
do we want to document this yet?
jb
More information about the Open-graphics
mailing list