[Open-graphics] SVN organization of new code ??

[Timothy Normand Miller]

On 12/12/07, Petter Urkedal <urkedal at nbi.dk> wrote:
> On 2007-12-11, Timothy Normand Miller wrote:
> > I need some feedback on how I should organize these files in SVN.
>
> I'd suggest
>
>   * Bigger things like PCI controller, memory controller, video
>     controller, and HQ in their own directories under rtl.

Those are.

>   * Smaller OGA1 specific things in a shared directory, say rtl/oga1.

Ok, how about this?

rtl/oga1/xp10/xp10_top_level.v
rtl/oga1/xp10/xp10_bridge2.v
rtl/oga1/xp10/fpga_config.v
rtl/oga1/xp10/pci_address_decode.v

rtl/oga1/s3/arbiter.v
rtl/oga1/s3/s3_bridge.v
rtl/oga1/s3/s3_top_level.v
rtl/oga1/s3/top_video_out.v
rtl/oga1/s3/bot_video_out.v



>   * Smaller generic things could be categorised like rtl/fifos or, if we
>     can't think of a suitable category, a common directory like rtl/lib.

The only thing I can think of that has more general use is
fpga_config.v.  It's logic in the XP10 that programs the Spartan in
slave-serial mode.




-- 
Timothy Normand Miller
http://www.cse.ohio-state.edu/~millerti
Open Graphics Project