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

Regions should have separate sizes for DTCM and SDRAM #34

Open
neworderofjamie opened this issue Jun 18, 2015 · 1 comment
Open

Regions should have separate sizes for DTCM and SDRAM #34

neworderofjamie opened this issue Jun 18, 2015 · 1 comment

Comments

@neworderofjamie
Copy link
Contributor

Large recording regions are the extreme case of this as they can take several megabytes of SDRAM, but essentially no DTCM. I've made the following hack to the LIF constraints, but it's not the best solution:

constraints = {
            sdram_constraint: lambda s: regions.utils.sizeof_regions(
                self.regions, s),
            dtcm_constraint: lambda s: regions.utils.sizeof_regions(
                self.regions[:-2], s),  # **HACK**
            cpu_constraint: cpu_usage,
        }
@mundya
Copy link
Member

mundya commented Jun 18, 2015

Definitely agree.

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