Temporarily Remove freq_attributes.xml to fix mirror issue

Change-Id: Ie36650e7fd8c7eb1fbdfe6977dfec98be60ea8d1
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/42143
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
Tested-by: Daniel M. Crowell <dcrowell@us.ibm.com>

1 files changed, 0 insertions, 109 deletions

diff --git a/src/import/chips/p9/procedures/xml/attribute_info/freq_attributes.xml b/src/import/chips/p9/procedures/xml/attribute_info/freq_attributes.xml
deleted file mode 100644
index 7ca6d5cbd..000000000
--- a/src/import/chips/p9/procedures/xml/attribute_info/freq_attributes.xml
+++ /dev/null
@@ -1,109 +0,0 @@
-<!-- IBM_PROLOG_BEGIN_TAG                                                   -->
-<!-- This is an automatically generated prolog.                             -->
-<!--                                                                        -->
-<!-- $Source: src/import/chips/p9/procedures/xml/attribute_info/freq_attributes.xml $ -->
-<!--                                                                        -->
-<!-- OpenPOWER HostBoot Project                                             -->
-<!--                                                                        -->
-<!-- Contributors Listed Below - COPYRIGHT 2015,2016                        -->
-<!-- [+] International Business Machines Corp.                              -->
-<!--                                                                        -->
-<!--                                                                        -->
-<!-- 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                                                     -->
-<!-- freq_attributes.xml -->
-<attributes>
-  <!-- ********************************************************************* -->
-  <attribute>
-    <id>ATTR_FREQ_PROC_REFCLOCK_KHZ</id>
-    <targetType>TARGET_TYPE_SYSTEM</targetType>
-    <description>
-      The frequency of the processor refclock in kHz.
-      Provided by the Machine Readable Workbook.
-      This can be overridden to adjust the refclock frequency.
-    </description>
-    <valueType>uint32</valueType>
-    <platInit/>
-  </attribute>
-  <!-- ********************************************************************* -->
-  <attribute>
-    <id>ATTR_FREQ_MEM_REFCLOCK</id>
-    <targetType>TARGET_TYPE_SYSTEM</targetType>
-    <description>
-      The frequency of the memory refclock in MHz.
-      Provided by the Machine Readable Workbook.
-      This is read by the set_ref_clock HWP to find out the desired frequency.
-      This can be overridden to adjust the refclock frequency.
-    </description>
-    <valueType>uint32</valueType>
-    <platInit/>
-  </attribute>
-  <!-- ********************************************************************* -->
-  <attribute>
-    <id>ATTR_MAX_ALLOWED_DIMM_FREQ</id>
-    <targetType>TARGET_TYPE_SYSTEM</targetType>
-    <description>
-      Maximum frequency (in MHz) that this system can run the DIMMs at.
-      There are 5 possible values determined by the dimm configuration.
-      For configurations which have mixed rank configurations, the lowest
-      frequency based on ranks of either DIMM is chosen. For example if
-      there was a 1R and a 2R DIMM installed, and 1R dual drop was a lower
-      max freq than 2R dual drop, then the 1R max freq would be the max allowed.
-        [0]=One rank, single drop
-        [1]=Two rank, single drop
-        [2]=Four rank, single drop
-        [3]=One rank, dual drop
-        [4]=Two rank, dual drop
-      A value of zero would indicate an unsupported configuration. Note: Do not
-      use this attribute to limit configurations, it is not checked during plug rules.
-      If you have an unsupported configuration, use the value 0 as the maximum freq.
-    </description>
-    <valueType>uint32</valueType>
-    <array>5</array>
-    <platInit/>
-  </attribute>
-  <!-- ********************************************************************* -->
-  <attribute>
-    <id>ATTR_REQUIRED_SYNCH_MODE</id>
-    <targetType>TARGET_TYPE_SYSTEM</targetType>
-    <description>
-      Specify the system policy to enforce synchronous mode between memory and
-      nest. This drives the value of ATTR_MEM_IN_SYNCH_MODE.
-         UNDETERMINED : Run synchronously if the dimm and nest freq matches
-         ALWAYS : Require matching frequencies and deconfigure memory that
-                  does not match the nest
-         NEVER : Do not run synchronously, even if the frequencies match
-    </description>
-    <valueType>uint8</valueType>
-    <enum>UNDETERMINED=0, ALWAYS=1, NEVER=2</enum>
-    <platInit/>
-  </attribute>
-  <!-- ********************************************************************* -->
-  <attribute>
-    <id>ATTR_MEMVPD_POS</id>
-    <targetType>TARGET_TYPE_MCS</targetType>
-    <description>
-      The position of the MCS target's VPD selector data, relative to the EEPROM
-      that contains its data.  The VPD defition supports up to 16 values per
-      EEPROM.
-      For systems with an EEPROM per chip, this value should be equivalent to
-      ATTR_CHIP_UNIT_POS.
-      For systems with a single EEPROM for all chips, the value should follow
-      the physical position in such a way to fit within the 16 available slots.
-    </description>
-    <valueType>uint8</valueType>
-    <platInit/>
-  </attribute>
-  <!-- ********************************************************************* -->
-</attributes>