• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 3502 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

does the BUFFERABLE bit of HPROT/AxCACHE ever mean anything by itself?

jameskim jameskim
Note: This was originally posted on 31st July 2009 at http://forums.arm.com

hi all,

there seems to be a clear definition of "bufferable" in both the AHB and AXI specs, pertaining to where write responses must be issued from.  but, then there are tables like the following from an ARM10 manual, which makes it seems like bufferable doesn't mean anything by itself:

C  B  Notes
0  0  Uncached, unbuffered
0  1  Uncached, buffered
1  0  Write-through cached, buffered
1  1  Write-back cached, buffered[/font]

for both AHB and AXI, does the bufferable bit always have to be interpreted along with the cacheable bit?

another thread seems to imply this:
[url="http://forums.arm.com/index.php?showtopic=12871"]http://forums.arm.com/index.php?showtopic=12871[/url]

any other official statements to this effect?

thanks!
james
Parents Reply Children
No data