systemsoftware
/
Linux-Architecture-Reference
35
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

minor formatting updates

Browse Source
pull/2/head
Jeff Scheel 6 years ago
parent 331f07b778
commit 92f14bfc73
2 changed files with 60 additions and 50 deletions
Show Stats Download Patch File Download Diff File

42
DeviceTree/ch_devtree_pa.xml
Unescape Escape View File

@ -161,8 +161,10 @@
<para>OF shall use the memory resources within the space indicated by the
<emphasis>real-base, real-size, virt-base</emphasis> and
<emphasis>virt-size</emphasis> Configuration Variables defined for the PA.
<emphasis role="bold"><literal>real-base</literal></emphasis>,
<emphasis role="bold"><literal>real-size</literal></emphasis>,
<emphasis role="bold"><literal>virt-base</literal></emphasis>, and
<emphasis role="bold"><literal>virt-size</literal></emphasis> Configuration Variables defined for the PA.
As described in the applicable platform binding, a mechanism is defined
to enable OF to determine if its current configuration is consistent with
the requirements of the client.</para>
@ -172,20 +174,20 @@
OF loads the client program, it inspects the program header, and if its
current usage of physical memory or virtual address space conflicts with
that specified in the program header, OF shall set the
<emphasis>real-base</emphasis>,
<emphasis>real-size</emphasis>,
<emphasis>virt-base</emphasis>, and
<emphasis>virt-size</emphasis> to the configuration variables as specified
<emphasis role="bold"><literal>real-base</literal></emphasis>,
<emphasis role="bold"><literal>real-size</literal></emphasis>,
<emphasis role="bold"><literal>virt-base</literal></emphasis>, and
<emphasis role="bold"><literal>virt-size</literal></emphasis> to the configuration variables as specified
in the header and restart itself.
<emphasis>Real-base</emphasis>,
<emphasis>real-size</emphasis>,
<emphasis>virt-base</emphasis>, and
<emphasis>virt-size</emphasis> may be specified as -1, in which case the
<emphasis role="bold"><literal>Real-base</literal></emphasis>,
<emphasis role="bold"><literal>real-size</literal></emphasis>,
<emphasis role="bold"><literal>virt-base</literal></emphasis>, and
<emphasis role="bold"><literal>virt-size</literal></emphasis> may be specified as -1, in which case the
firmware is permitted to choose appropriate values for the variables
specified as -1.</para>
<para>If the values of the
<emphasis>real-size</emphasis> and/or
<emphasis>virt-size</emphasis> configuration variables do not provide
<emphasis role="bold"><literal>real-size</literal></emphasis> and/or
<emphasis role="bold"><literal>virt-size</literal></emphasis> configuration variables do not provide
sufficient memory and/or virtual address space for the firmware's own
use, then the firmware shall not attempt to load a client program and the
condition should be reported to the user. The possibility of not being
@ -242,12 +244,12 @@
interface handler, that is passed to the client, has to be a real
address.</para>
<para>The Configuration Variables
<emphasis>real-base</emphasis> and
<emphasis>real-size</emphasis> should indicate the physical memory base
<emphasis role="bold"><literal>real-base</literal></emphasis> and
<emphasis role="bold"><literal>real-size</literal></emphasis> should indicate the physical memory base
and size in which OF must locate itself. In Real-Mode, the Configuration
Variables
<emphasis>virt-base</emphasis> and
<emphasis>virt-size</emphasis> do not have meaning and should be set to
<emphasis role="bold"><literal>virt-base</literal></emphasis> and
<emphasis role="bold"><literal>virt-size</literal></emphasis> do not have meaning and should be set to
-1.</para>
</section>
@ -263,11 +265,11 @@
interfaces to allow OF and its client to ensure that this single virtual
address model can be maintained.</para>
<para>The Configuration Variables
<emphasis>virt-base</emphasis> and
<emphasis>virt-size</emphasis> should indicate the virtual address space
<emphasis role="bold"><literal>virt-base</literal></emphasis> and
<emphasis role="bold"><literal>virt-size</literal></emphasis> should indicate the virtual address space
base address and size that OF should use. The Configuration Variables
<emphasis>real-base</emphasis> and
<emphasis>real-size</emphasis> should indicate the physical memory base
<emphasis role="bold"><literal>real-base</literal></emphasis> and
<emphasis role="bold"><literal>real-size</literal></emphasis> should indicate the physical memory base
and size in which OF must locate itself.</para>
</section>

68
DeviceTree/ch_devtree_system.xml
Unescape Escape View File

@ -540,7 +540,7 @@
<icon size=64,64 color-space=3,3,2><bitmap>hh ... hh1</bitmap></icon>
</chrp-boot>]]></programlisting></para>

<para>AIX Diagnostics Bootinfo Object Example:
<para><emphasis role="bold">AIX Diagnostics Bootinfo Object Example:</emphasis>
<programlisting><![CDATA[<chrp-boot>
<description>AIX 4.2.D.0 Diagnostics</description>
<os-name>AIX 4.2.D.0 Diagnostics</os-name>
@ -4694,7 +4694,7 @@
<entry>
<para>0</para>
</entry>
<entry morerows="1">
<entry morerows="1" valign="middle">
<para>0b11 for H_CONFER &amp; H_PROD</para>
</entry>
</row>
@ -4707,7 +4707,7 @@
<entry>
<para>2</para>
</entry>
<entry>
<entry valign="middle">
<para>Set to 1 if H_PURR is implemented with a reduced volatile
kill set of r3 &amp; r4; else set to 0.</para>
</entry>
@ -4716,7 +4716,7 @@
<entry>
<para>3</para>
</entry>
<entry morerows="4">
<entry morerows="4" valign="middle">
<para>Reserved for future expansion (0b0)</para>
</entry>
</row>
@ -7544,16 +7544,21 @@
<para>The presence of the node indicates that all or some of the function
has been implemented and will be reported using an interrupt.</para>
<para>
<emphasis role="bold"><literal>&#8220;name&#8221;</literal></emphasis></para>
<para>Standard
<emphasis>property name</emphasis> that denotes the I/O sub-system
events.</para>
<para>
<emphasis>prop-encoded-array</emphasis>: A string, encoded as with
<emphasis role="bold"><literal>encode-string</literal></emphasis>.</para>
<para>The value of this string shall be
<literal>&#8220;ibm,io-events&#8221;</literal>.</para>
<variablelist>
<varlistentry>
<term><emphasis role="bold"><literal>&#8220;name&#8221;</literal></emphasis> [S]</term>
<listitem>
<para>Standard
<emphasis>property name</emphasis> that denotes the I/O sub-system
events.</para>
<para>
<emphasis>prop-encoded-array</emphasis>: A string, encoded as with
<emphasis role="bold"><literal>encode-string</literal></emphasis>.</para>
<para>The value of this string shall be
<literal>&#8220;ibm,io-events&#8221;</literal>.</para>
</listitem>
</varlistentry>
</variablelist>
</section>

@ -8419,7 +8424,7 @@
<para><emphasis role="bold"><literal>&#8220;status&#8221;</literal></emphasis></para>
</listitem>
</itemizedlist>
<para><emphasis>Optionally</emphasis> the children of the
<para><emphasis role="bold">Optionally</emphasis> the children of the
<emphasis role="bold"><literal>/ibm,platform-facilities</literal></emphasis> node may contain as
appropriate the following standard properties with their standard
definitions:</para>
@ -8430,7 +8435,7 @@
</listitem>
</itemizedlist>
<para><emphasis>Additionally</emphasis> the children of the
<para><emphasis role="bold">Additionally</emphasis> the children of the
<emphasis role="bold"><literal>/ibm,platform-facilities</literal></emphasis> node may contain as
appropriate the following unique properties:</para>
@ -9974,11 +9979,12 @@
the endian-ness specified by the EI-DATA field of the file.</para>
<para>The format of a Note Section header can be described by an OF
struct as:</para>
<para>struct \ Note Section header for OF</para>
<para>/L field ns.namesz \ length of ns.name, including NULL</para>
<para>/L field ns.descrsz</para>
<para>/L field ns.type</para>
<para>0 field ns.name \ NULL-terminated, /L padded</para>
<programlisting><![CDATA[struct \ Note Section header for OF
/L field ns.namesz \ length of ns.name, including NULL
/L field ns.descrsz
/L field ns.type
0 field ns.name \ NULL-terminated, /L padded]]></programlisting>

<section>
<title>1275 PowerPC Note Definition</title>
@ -9992,13 +9998,14 @@
depends upon the kind of Note Section in which it is contained. For the
PowerPC OF note, the format of the Note Section&#8217;s descriptor can be
described by an OF struct, as follows:</para>
<para>struct \ Note Section descriptor for CHRP OF</para>
<para>/L field ns.real-mode</para>
<para>/L field ns.real-base</para>
<para>/L field ns.real-size</para>
<para>/L field ns.virt-base</para>
<para>/L field ns.virt-size</para>
<para>/L field ns.load-base</para>
<programlisting><![CDATA[struct \ Note Section descriptor for CHRP OF</para>
/L field ns.real-mode
/L field ns.real-base
/L field ns.real-size
/L field ns.virt-base
/L field ns.virt-size
/L field ns.load-base]]></programlisting>
<para>If the
<emphasis role="bold"><literal>ns.load-base</literal></emphasis> value is not -1, then that value is
compared against the current value of the
@ -10073,7 +10080,7 @@
the Note Section&#8217;s descriptor can be described by an OF struct, as
follows:</para>

<programlisting linenumbering="numbered"><![CDATA[struct \ Note Section descriptor for OF
<programlisting><![CDATA[struct \ Note Section descriptor for OF
/L field ns.lparaffinity \= “0/1” (default assumption to be “N”)
/L field ns.min-rmo-size \Minimum size of the Real Mode Accessible Storage
\ Area in MB
@ -10092,7 +10099,8 @@
\ variables based upon the values in this
\ header.
\ (default value 0)
/L field ns.large-page-ready \Flag to indicate the partition OS is prepared for large pages.
/L field ns.large-page-ready \Flag to indicate the partition OS is prepared for
\ large pages.
/L field ns.force_alpha_mode]]></programlisting>

<para><emphasis role="bold">Note:</emphasis> The size of the /L field is based off of

Write Preview
Loading…
Cancel
Save