From 92f14bfc737f97b59a542f62c745c55d2b881a89 Mon Sep 17 00:00:00 2001 From: Jeff Scheel Date: Tue, 13 Nov 2018 15:03:08 -0600 Subject: [PATCH] minor formatting updates --- DeviceTree/ch_devtree_pa.xml | 42 ++++++++++---------- DeviceTree/ch_devtree_system.xml | 68 ++++++++++++++++++-------------- 2 files changed, 60 insertions(+), 50 deletions(-) diff --git a/DeviceTree/ch_devtree_pa.xml b/DeviceTree/ch_devtree_pa.xml index 51c5a5c..b76b4b4 100644 --- a/DeviceTree/ch_devtree_pa.xml +++ b/DeviceTree/ch_devtree_pa.xml @@ -161,8 +161,10 @@ OF shall use the memory resources within the space indicated by the - real-base, real-size, virt-base and - virt-size Configuration Variables defined for the PA. + real-base, + real-size, + virt-base, and + virt-size 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. @@ -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 - real-base, - real-size, - virt-base, and - virt-size to the configuration variables as specified + real-base, + real-size, + virt-base, and + virt-size to the configuration variables as specified in the header and restart itself. - Real-base, - real-size, - virt-base, and - virt-size may be specified as -1, in which case the + Real-base, + real-size, + virt-base, and + virt-size may be specified as -1, in which case the firmware is permitted to choose appropriate values for the variables specified as -1. If the values of the - real-size and/or - virt-size configuration variables do not provide + real-size and/or + virt-size 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. The Configuration Variables - real-base and - real-size should indicate the physical memory base + real-base and + real-size should indicate the physical memory base and size in which OF must locate itself. In Real-Mode, the Configuration Variables - virt-base and - virt-size do not have meaning and should be set to + virt-base and + virt-size do not have meaning and should be set to -1. @@ -263,11 +265,11 @@ interfaces to allow OF and its client to ensure that this single virtual address model can be maintained. The Configuration Variables - virt-base and - virt-size should indicate the virtual address space + virt-base and + virt-size should indicate the virtual address space base address and size that OF should use. The Configuration Variables - real-base and - real-size should indicate the physical memory base + real-base and + real-size should indicate the physical memory base and size in which OF must locate itself. diff --git a/DeviceTree/ch_devtree_system.xml b/DeviceTree/ch_devtree_system.xml index 15783d5..c8b6ff4 100644 --- a/DeviceTree/ch_devtree_system.xml +++ b/DeviceTree/ch_devtree_system.xml @@ -540,7 +540,7 @@ hh ... hh1 ]]> - AIX Diagnostics Bootinfo Object Example: + AIX Diagnostics Bootinfo Object Example: AIX 4.2.D.0 Diagnostics AIX 4.2.D.0 Diagnostics @@ -4694,7 +4694,7 @@ 0 - + 0b11 for H_CONFER & H_PROD @@ -4707,7 +4707,7 @@ 2 - + Set to 1 if H_PURR is implemented with a reduced volatile kill set of r3 & r4; else set to 0. @@ -4716,7 +4716,7 @@ 3 - + Reserved for future expansion (0b0) @@ -7544,16 +7544,21 @@ The presence of the node indicates that all or some of the function has been implemented and will be reported using an interrupt. - - “name” - Standard - property name that denotes the I/O sub-system - events. - - prop-encoded-array: A string, encoded as with - encode-string. - The value of this string shall be - “ibm,io-events”. + + + “name” [S] + + Standard + property name that denotes the I/O sub-system + events. + + prop-encoded-array: A string, encoded as with + encode-string. + The value of this string shall be + “ibm,io-events”. + + + @@ -8419,7 +8424,7 @@ “status” - Optionally the children of the + Optionally the children of the /ibm,platform-facilities node may contain as appropriate the following standard properties with their standard definitions: @@ -8430,7 +8435,7 @@ - Additionally the children of the + Additionally the children of the /ibm,platform-facilities node may contain as appropriate the following unique properties: @@ -9974,11 +9979,12 @@ the endian-ness specified by the EI-DATA field of the file. The format of a Note Section header can be described by an OF struct as: - 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 + +
1275 PowerPC Note Definition @@ -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’s descriptor can be described by an OF struct, as follows: - struct \ Note Section descriptor for CHRP OF - /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 + + +/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]]> If the ns.load-base value is not -1, then that value is compared against the current value of the @@ -10073,7 +10080,7 @@ the Note Section’s descriptor can be described by an OF struct, as follows: - Note: The size of the /L field is based off of