search

nvdla / hw

RTL, Cmodel, and testbench for NVDLA
Other
1.71k stars 565 forks source link

differences between master and nv_small #229

Closed shgangchen closed 5 years ago

shgangchen commented 5 years ago

in the branch, there are master copy and nv_small copy, and master copy can be configed as nv_small.spec.

So, what's the differences between the master master branch and nv_small branch？

And you said in the document that only nv_small is tested, whether you mean the nv_small branch or the nv_small configuration?

I'm a little confused. So @jwise @zdraw @sernc11 @prasshantg @nodushiv , anyone can help to explain that?

ghost commented 5 years ago

So, i was a witness to the last pushes, since I regularly follow the NVDLA development. I am not active NVDLA contributor by the way, except for some little, rather insignificant merge requests.

A long, long time ago there were two branches:

A this point developers worked heavily on better configurability. And what they finally did:

The last two points usually is an opportunity to burn someone on the stake by Gitflow fans :)

So to answer your question: in typical git flow, nv_small would be a tag - a stable release of NVDLA supporting nv_small only. And master would just go forth in the tree with newer changes.

Hope it helps :)

shgangchen commented 5 years ago

So, i was a witness to the last pushes, since I regularly follow the NVDLA development. I am not active NVDLA contributor by the way, except for some little, rather insignificant merge requests.

A long, long time ago there were two branches:

  • nvdlav1 - the oldest branch with so called _nvfull with floating point support
  • master - development branch of _nvsmall - although it supports other .spec files it most likely won't synthesise.

A this point developers worked heavily on better configurability. And what they finally did:

  • nvdlav1 - was left as is (maybe with some minor bugfixes, I didn't follow that)
  • master was renamed to _nvsmall
  • new master was pushed from their local repositories

The last two points usually is an opportunity to burn someone on the stake by Gitflow fans :)

So to answer your question: in typical git flow, nv_small would be a tag - a stable release of NVDLA supporting nv_small only. And master would just go forth in the tree with newer changes.

Hope it helps :)

Thanks a lot. I really helps.