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

readme: Update docs on CACHE WIDTH option #58

Merged
merged 1 commit into from
Jan 4, 2018

Conversation

stffrdhrn
Copy link
Member

@stffrdhrn stffrdhrn commented Jan 4, 2018

As discussed in IRC:

  12:39 < stekern> oetwi_: or1k can only dynamically control addresses to
        be cacheable/noncacheable when the mmu is enabled.
  12:40 < stekern> mor1kx have an option to work around this, you can
        hardwire the upper address space to be noncacheable by adjusting
        OPTION_DCACHE_LIMIT_WIDTH
  12:42 < stekern> (we should fix the linux kernel to setup some mmu
        mapping that marks the uart as non-cacheable before the first early
        prints)

We have traditionally set cache address width to 31 and mapped devices
into high order address space to avoid caching of device reads and
writes. Add this as a recommendation in the mor1kx options
documentation.

As discussed in IRC:

  12:39 < stekern> oetwi_: or1k can only dynamically control addresses to
        be cacheable/noncacheable when the mmu is enabled.
  12:40 < stekern> mor1kx have an option to work around this, you can
        hardwire the upper address space to be noncacheable by adjusting
        OPTION_DCACHE_LIMIT_WIDTH
  12:42 < stekern> (we should fix the linux kernel to setup some mmu
        mapping that marks the uart as non-cacheable before the first early
        prints)

We have traditionally set cache address width to 31 and mapped devices
into high order address space to avoid caching of device reads and
writes.  Add this as a recommendation in the mor1kx options
documentation.
@skristiansson skristiansson merged commit 70b92df into openrisc:master Jan 4, 2018
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