On 04/19/2011 01:33 PM, Scott Wood wrote: > On Tue, 19 Apr 2011 13:26:26 -0500 > Meador Inge <meador_i...@mentor.com> wrote: > >> On 04/19/2011 12:52 PM, Scott Wood wrote: >>> On Tue, 19 Apr 2011 11:59:34 -0500 >>> Meador Inge <meador_i...@mentor.com> wrote: >>> >>>> Aliases are of the form 'msgr-block<n>', >>>> + where <n> is an integer specifying the block's number. Numbers shall >>>> start >>>> + at 0. >>> >>> The hw docs refer to "group A" and "group B", not "block 0" and "block 1". >>> >>> Plus, I'd put "mpic-" in the alias name. >> >> Are you suggesting that the alias should be called: 'mpic-groupA', >> 'mpic-groupB', 'mpic-groupC', etc... ? > > I was thinking something like "mpic-msgr-group-a", "mpic-msgr-group-b" -- > though if you want to use numbers instead to more easily map to potential > APIs, that's OK. >
Hmmm ... In the MPC8572E and P1022DS manuals I don't see the terminology group used for message registers. The MPIC global timers on the other hand do use group A and group B. I will definitely add the 'mpic-' prefix, but unless I am looking in the wrong place in the manuals, then I am not so sure there are MPIC message register groups. As a side note, the term "register block" pops up in a few places not related to message registers. If you feel like group is a more idiomatic term, I can change it. -- Meador Inge | meador_inge AT mentor.com Mentor Embedded | http://www.mentor.com/embedded-software _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev