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

Don't initialize nvdla-workload with init-submodules #1063

Merged
merged 3 commits into from
Dec 17, 2021
Merged

Conversation

jerryz123
Copy link
Contributor

nvdla-workload is very large, results in long init times. Make users initialize this explicitly (like we do with gemmini-software)

Type of change: other enhancement

Impact: software change

Release Notes

NVDLA-workload submodule is not longer initialized with init-submodules script

nvdla-workload is very large, results in long init times
Copy link
Contributor

@abejgonzalez abejgonzalez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add some documentation to https://chipyard.readthedocs.io/en/dev/Software/index.html to indicate that there is a software/ dir and that you need to initialize it to use it?

set -o pipefail

# Enable submodule update for software submodules
git config --unset submodule.software/nvdla-workload.update || :
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be git config --local --unset like what the init-submodules.sh script does?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

_unskip() { git config --local --unset-all "submodule.${1}.update" || : ; }

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the --local flag is default.

These values are specific to that single repository, and represent passing the --local option to git config. If you don’t specify which level you want to work with, this is the default.

Copy link
Contributor

@abejgonzalez abejgonzalez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Successfully merging this pull request may close these issues.

2 participants