Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nv_small and nv_full difference #12

Open
ferin08 opened this issue Jul 10, 2018 · 2 comments
Open

nv_small and nv_full difference #12

ferin08 opened this issue Jul 10, 2018 · 2 comments

Comments

@ferin08
Copy link

ferin08 commented Jul 10, 2018

This link on scalability configuration shows the differences in parameters for the two

http://nvdla.org/hw/v2/scalability.html

However, I would like to know what impact these parameters difference would mean from an application difference standpoint.

@JunningWu
Copy link
Owner

as to application, I guess you means the nvdla_runtime. so, when porting from nv_full to nv_small, you have to change the low-level driver APIs related to configuration REGs. and nv_small may lack of some computation unit which you shall not using in your application code.

@ferin08
Copy link
Author

ferin08 commented Jul 11, 2018

This link on scalability configuration shows the differences in parameters for the two

http://nvdla.org/hw/v2/scalability.html

According to this, are sub units like RUBIK engine and BDMA not present in nv_small config?

Also is nv_small just a scaled down version of nv_full or are there important units removed from an application point of view?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants