Konban ha,

On Sun, 17 Dec 2006 18:23:32 -0500
"Timothy Miller" <[EMAIL PROTECTED]> wrote:

> I have, I think, possibly, a working PCI target to test.

Cool!

> (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?

First fix the directory hierarchy so that every subdir
makes sense. Either by fixing the PCI dir or changing the
current hierarchy.

For the old stuff, i'd just create a new directory "old_stuff"
at the top level, then clone the current hierarchy we have and
"svn move" directories in there, best with a date attached. ie
cd <ogptree>/trunk
mkdir old_stuff
svn add old_stuff
svn mv pci old_stuff/pci-`date -I`
svn ci


> (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.

Definitly. I once had a few hours free time and tried
to make sense of the current file structure and what
we have. I gave up after two hours of code reading.
Some READMEs that describe the contents of each directory
would really help

 
> 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.

As i never thought about how to implement a PCI interface,
i don't have a clear idea what the difficulties are from
a target to a master. But couldn't we first stay with the
target, simulate it, synthesize it, test it fully and then
step by step add master functionalities?

                        Attila Kinali


-- 
Lotus Notes ist eine verteilte Datenbankapplikation,
als Sample ist eine miese Groupware dabei ;)
                       -- Lukas Beeler
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to