diff options
author | Dan Crowell <dcrowell@us.ibm.com> | 2016-04-08 21:03:51 -0500 |
---|---|---|
committer | Stephen Cprek <smcprek@us.ibm.com> | 2016-04-21 13:51:32 -0500 |
commit | 76f1c48130a060fbe83c851fce2474c17b2df9b2 (patch) | |
tree | e258515dcbdab5817603c9d290befe2324df7d59 /src/usr/hwpf/hwp/dimm_errors.xml | |
parent | 3967f43b9478d7e6b58180dd0b331e61412997cd (diff) | |
download | talos-hostboot-76f1c48130a060fbe83c851fce2474c17b2df9b2.tar.gz talos-hostboot-76f1c48130a060fbe83c851fce2474c17b2df9b2.zip |
Removing some more old fapi1 and hwp code
Deleted all of the old fapi1 code
Moved potentially reuseable occ code to a new dir
Deleted a variety of p8 hwp files
Change-Id: I8b6ab72fef3f1413d919bdd21bc88f2c4f59c5c3
RTC: 146345
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/23075
Tested-by: Jenkins Server
Tested-by: FSP CI Jenkins
Reviewed-by: Matt Derksen <v2cibmd@us.ibm.com>
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Reviewed-by: William G. Hoffa <wghoffa@us.ibm.com>
Diffstat (limited to 'src/usr/hwpf/hwp/dimm_errors.xml')
-rw-r--r-- | src/usr/hwpf/hwp/dimm_errors.xml | 104 |
1 files changed, 0 insertions, 104 deletions
diff --git a/src/usr/hwpf/hwp/dimm_errors.xml b/src/usr/hwpf/hwp/dimm_errors.xml deleted file mode 100644 index 6b19331f0..000000000 --- a/src/usr/hwpf/hwp/dimm_errors.xml +++ /dev/null @@ -1,104 +0,0 @@ -<!-- IBM_PROLOG_BEGIN_TAG --> -<!-- This is an automatically generated prolog. --> -<!-- --> -<!-- $Source: src/usr/hwpf/hwp/dimm_errors.xml $ --> -<!-- --> -<!-- OpenPOWER HostBoot Project --> -<!-- --> -<!-- COPYRIGHT International Business Machines Corp. 2012,2014 --> -<!-- --> -<!-- Licensed under the Apache License, Version 2.0 (the "License"); --> -<!-- you may not use this file except in compliance with the License. --> -<!-- You may obtain a copy of the License at --> -<!-- --> -<!-- http://www.apache.org/licenses/LICENSE-2.0 --> -<!-- --> -<!-- Unless required by applicable law or agreed to in writing, software --> -<!-- distributed under the License is distributed on an "AS IS" BASIS, --> -<!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or --> -<!-- implied. See the License for the specific language governing --> -<!-- permissions and limitations under the License. --> -<!-- --> -<!-- IBM_PROLOG_END_TAG --> -<!-- $Id: dimm_errors.xml,v 1.7 2014/02/27 21:40:32 mjjones Exp $ --> - -<hwpErrors> - <!-- *********************************************************************** --> - <hwpError> - <rc>RC_BAD_DQ_DIMM_BAD_PARAM</rc> - <description> - A HWP called a utility function to access the bad DQ data but specified - an invalid PORT/DIMM/RANK - </description> - <ffdc>FFDC_PORT</ffdc> - <ffdc>FFDC_DIMM</ffdc> - <ffdc>FFDC_RANK</ffdc> - </hwpError> - <!-- *********************************************************************** --> - <hwpError> - <rc>RC_BAD_DQ_DIMM_NOT_FOUND</rc> - <description> - A HWP called a utility function to accessing the bad DQ data. The - utility function could not find a functional DIMM associated with the - specified MBA/PORT/DIMM - </description> - <ffdc>FFDC_MBA_TARGET</ffdc> - <ffdc>FFDC_PORT</ffdc> - <ffdc>FFDC_DIMM</ffdc> - </hwpError> - <!-- ********************************************************************* --> - <hwpError> - <rc>RC_BAD_DQ_MFG_MODE_BITS_FOUND_DURING_GET</rc> - <description> - A HWP noted additional bad bits in the bad dq bitmap of the - specified DIMM while in the manufacturing DISABLE_DRAM_REPAIRS - mode during a read operation. - CLEAN_BAD_DQ_BITMAP represents a bad dq bitmap with the appropriate - spare and ECC DQs (if any) set to 1 and all other DQs set to 0. - CURRENT_BAD_DQ_BITMAP represents the current bad dq bitmap. Any - discrepancies with CLEAN_BAD_DQ_BITMAP are the result of a manufacturing - mode process. - </description> - <ffdc>DIMM</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK0</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK1</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK2</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK3</ffdc> - <ffdc>CURRENT_BAD_DQ_BITMAP_RANK0</ffdc> - <ffdc>CURRENT_BAD_DQ_BITMAP_RANK1</ffdc> - <ffdc>CURRENT_BAD_DQ_BITMAP_RANK2</ffdc> - <ffdc>CURRENT_BAD_DQ_BITMAP_RANK3</ffdc> - <callout> - <target>DIMM</target> - <priority>HIGH</priority> - </callout> - </hwpError> - <!-- ********************************************************************* --> - <hwpError> - <rc>RC_BAD_DQ_MFG_MODE_BITS_FOUND_DURING_SET</rc> - <description> - A HWP noted an attempt to set additional bad bits in the bad dq bitmap - of the specified DIMM while in the manufacturing DISABLE_DRAM_REPAIRS - mode during a write operation. - CLEAN_BAD_DQ_BITMAP represents a bad dq bitmap with the appropriate - spare and ECC DQs (if any) set to 1 and all other DQs set to 0. - UPDATE_BAD_DQ_BITMAP represents the proposed updates to set. Any - discrepancies with CLEAN_BAD_DQ_BITMAP are the result of a manufacturing - mode process and should not be made. - </description> - <ffdc>DIMM</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK0</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK1</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK2</ffdc> - <ffdc>CLEAN_BAD_DQ_BITMAP_RANK3</ffdc> - <ffdc>UPDATE_BAD_DQ_BITMAP_RANK0</ffdc> - <ffdc>UPDATE_BAD_DQ_BITMAP_RANK1</ffdc> - <ffdc>UPDATE_BAD_DQ_BITMAP_RANK2</ffdc> - <ffdc>UPDATE_BAD_DQ_BITMAP_RANK3</ffdc> - <callout> - <target>DIMM</target> - <priority>HIGH</priority> - </callout> - </hwpError> - <!-- ********************************************************************* --> -</hwpErrors> |