aboutsummaryrefslogtreecommitdiff
path: root/thunk.c
diff options
context:
space:
mode:
authorScott Wood <scottwood@freescale.com>2012-12-21 16:15:42 +0000
committerAlexander Graf <agraf@suse.de>2013-01-07 17:37:10 +0100
commitbe7c236fa2e59090d7cd0193ca3f225c331d5f81 (patch)
tree059d83bc9de13248c1ee027f613cd754b8905400 /thunk.c
parenta1bb73849fbd7d992b6ac2cf30c034244fb2299d (diff)
downloadqemu-be7c236fa2e59090d7cd0193ca3f225c331d5f81.zip
qemu-be7c236fa2e59090d7cd0193ca3f225c331d5f81.tar.gz
qemu-be7c236fa2e59090d7cd0193ca3f225c331d5f81.tar.bz2
openpic: make register names correspond better with hw docs
The base openpic specification doesn't provide abbreviated register names, so it's somewhat understandable that the QEMU code made up its own, except that most of the names that QEMU used didn't correspond to the terminology used by any implementation I could find. In some cases, like PCTP, the phrase "processor current task priority" could be found in the openpic spec when describing the concept, but the register itself was labelled "current task priority register" and every implementation seems to use either CTPR or the full phrase. In other cases, individual implementations disagree on what to call the register. The implementations I have documentation for are Freescale, Raven (MCP750), and IBM. The Raven docs tend to not use abbreviations at all. The IBM MPIC isn't implemented in QEMU. Thus, where there's disagreement I chose to use the Freescale abbreviations. Signed-off-by: Scott Wood <scottwood@freescale.com> [agraf: rebase on current state of the code] Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'thunk.c')
0 files changed, 0 insertions, 0 deletions