When I try to generate nv_small, it goes wrong.

[CrazyBingo]

When I try to generate nv_small, it goes wrong. It exiting while the project.h does nor exists., and stoped itself.

So can the NVDLA now support nv_small now? TKs.

[JunningWu]

No, just now.

[jwise]

@JunningWu is correct. nv_small is expected in a future release.

[teabun]

Is there an estimated timeline when nv_small will be available? Some clarity on this is helpful, thanks!

[CrazyBingo]

@teabun So the same to you, the reason why we want nv_small is the area of nv_large is big

[CrazyBingo]

@teabun
sorry I do not know, I'm not the member of NVDIA, but a follower of nvdla as you.
I just find out that we can not generate nv_small code now.

Which step have you reached?

[teabun]

My team just started explorating nv_large as we are aware nv_small isn't ready,  but from the milestone it seems to suggest end Q4 '17. Just wish to get some visibility for planning purpose. Thanks! Sent from Yahoo Mail on Android On Thu, 8 Feb 2018 at 22:51, CrazyBingo<notifications@github.com> wrote: @teabun sorry I do not know, I'm not the member of NVDIA, but a follower of nvdla as you. I just find out that we can not generate nv_small code now. Which step have you reached? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[CrazyBingo]

Me too，and we aware thar nv_full can not put in MPSOC， or the performance of nv_small is not enough

[megalomanaa]

I am also looking forward to the release, but then, is this true that any different MAC size other than nv_full is not available yet?

[CrazyBingo]

May be，wait together ……

[jwise]

nv_small is now released in the master branch.