On 23 May 2013 13:34, Albert ARIBAUD <albert.u.boot@xxxxxxxxxxx> wrote: > Well -- if you form the acronym, you do end with 'A R M' indeed, but > this is quite unfortunate, as 'ARM ARM' is redundant (as the acronym's > A already has ARM in it), confusion (as 'ARM' already bears a quite > established meaning) and ambiguous (as there are actually several > documents with the title of 'ARM<vXXX> Reference Manual' and which > would end up with the same acronym). "ARM ARM" is the standard abbreviated way of referring to the ARM Architecture Reference Manual (and as you can see it's not a redundant acronym, since the A doesn't stand for ARM). A TRM (Technical Reference Manual) is a completely different document type, describing a specific processor. Andre is correct that the restriction in question is architectural (and thus described in the ARM ARM), not implementation specific (which would be what you'd find in a TRM). > So if you don't want to use 'TRM' (which I can understand), then > at least please replace 'ARM ARM' with 'ARMv7-AR Reference Manual'. > Stating the DDI* reference is not a must, unless you want to specify > a given revision (but then I suggest adding it after 'Manual' too). "ARMv7-AR Reference Manual" is confusing, because you've dropped the "Architecture" bit. Since this is only a git comment, I'd suggest "ARM architecture reference manual" as both clear for non-ARM people and sufficiently unambiguous, or "ARMv7-AR Architecture Reference Manual" if you want to be a bit more formal about it. thanks -- PMM _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
