I have, I think, possibly, a working PCI target to test.
This one is highly simplified from what I was trying to do before. It's a complete rewrite that strives for logical correctness, not performance. Once we know it's functionally correct, optimizing for performance will be a straightforward process. It's also got a lot of stubs in it that'll be hooked up right later. There are a few things that need to be done: (1) Since this is a replacement for the old design, I'd like to set the old one aside. I don't want to delete it or take it offline, because there's more copy/paste to be done as the new design evolves. What would be the most sensible way to handle this in SVN? I was thinking that perhaps a new directory would be good, but pci already sadly violates the rtl/ hierarchy we have for other things. Suggestions? (2) Once it's in SVN, I'd like to get some help testing it. I have a working simulation environment that should therefore be easy to hack. I was hoping I could get those of you who have a PCI spec or Shanley's book could help me beef up the tests and expand their scope. (3) Going with the spirit of being an educational project, not to mention good engineering practices, I think we should document this in fine detail. It should be documented to the point that people with no experience in hardware design can follow along and make sense of it, and those with hardware design experience could code a new one in a week. We can start with more comments, but diagrams, ODF documents (and PDFs of those), and sort-of tutorials would be good to have. The PCI block of this design is a critical component. Everything goes in and out of the PCI block, so it it's wrong, nothing else works. Next, we should discuss strategy. I'm thinking that we urgently need a PCI target (the one we're testing with does not belong to us), so I think the next step is to make this synthesizable. However, we should take a baby-step towards adding the master logic so that we don't have to do a lot of back-tracking when we do get around to that. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
