From: Scott Wood <scottwood@freescale.com>
To: Ryan Wang <openspace.wang@gmail.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Re: What does rmo/tce stand for in powerpc?
Date: Wed, 2 Nov 2011 14:19:20 -0500 [thread overview]
Message-ID: <4EB197B8.8020504@freescale.com> (raw)
In-Reply-To: <CAPxxNQ=TkMFhzBeLi9bt5Fo7gygoM2V61EHYRzKqcMetaG2qnQ@mail.gmail.com>
On 11/02/2011 06:17 AM, Ryan Wang wrote:
>=20
>=20
> 2011/11/2 Nishanth Aravamudan <nacc@us.ibm.com <mailto:nacc@us.ibm.com>=
>
>=20
> Hi Ryan,
>=20
> On 01.11.2011 [14:25:43 +0800], Ryan Wang wrote:
> > Hi,
> >
> > In kernel source comments, I saw the words:
> > ''
> >
> > alloc_top is set to the top of RMO, eventually shrink down if the
> > <http://lxr.linux.no/linux+*/arch/powerpc/kernel/prom_init.c#L972
> <http://lxr.linux.no/linux+*/arch/powerpc/kernel/prom_init.c#L972>>=
TCEs
> > overlap
> >
> > ''
> >
> > I wonder what does RMO mean, and TCE?
>=20
> RMO =3D Real Mode Offset -- deprecated in terms of Real Mode Area i=
n PAPR.
>=20
> TCE =3D Translation Control Entry
>=20
> You should be able to find descriptions of both in PAPR.
>=20
>=20
> Thanks Nish!
>=20
> But I searched <Power.orgTM Standard for Embedded Power ArchitectureTM
> Platform Requirements> and failed to found the concept RMO or Real Mode
> Offset.
>=20
> Will you please give me some hints to the docs=EF=BC=9FThanks,
ePAPR and PAPR are not the same thing.
It looks like PAPR is only available to power.org members.
-Scott
next prev parent reply other threads:[~2011-11-02 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 6:25 What does rmo/tce stand for in powerpc? Ryan Wang
2011-11-01 17:25 ` Nishanth Aravamudan
2011-11-02 11:17 ` Ryan Wang
2011-11-02 18:30 ` Nishanth Aravamudan
2011-11-02 19:19 ` Scott Wood [this message]
2011-11-03 1:05 ` Ryan Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB197B8.8020504@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nacc@us.ibm.com \
--cc=openspace.wang@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.