Patent Grant
8775112
The present invention relates to the field of semiconductor manufacturing. In particular, the present invention relates to a system and method for dynamically configuring operational characteristics of functional components within an integrated circuit.
Electronic systems and circuits have made a significant contribution towards the advancement of modern society and are utilized in a number of applications to achieve advantageous results. Numerous electronic technologies such as digital computers, calculators, audio devices, video equipment, and telephone systems have facilitated increased productivity and reduced costs in analyzing and communicating data in most areas of business, science, education and entertainment. Electronic systems providing these advantageous results often include integrated circuits. It is desirable to utilize integrated circuits with very high reliability characteristics to prevent erroneous results. However, designing and building integrated circuits with diverse functionality and performance characteristics is challenging. Additionally, the manufacturing process to build the integrated circuits is highly complex and resource intensive.
Manufacturing integrated circuits is an expensive, resource intensive activity, in which numerous computational components are included in a single integrated circuit unit. The computational components are usually required to be capable of performing a variety of tasks with very high reliability. Various applications often require different performance levels and functionality. Traditionally, each die is fabricated with a predetermined quantity of properly performing components providing set functionality. However, providing appropriate and efficient functionality at acceptable reliability is often difficult. For example, many traditional approaches require that there be few or no defective components included in the integrated circuit.
Conventionally, integrated circuits are manufactured in wafers comprising a number of die, with each die comprising an integrated circuit having numerous functional components. The number of die that are functionally acceptable from a given wafer is referred to as the yield from the wafer. It is desirable to maintain relatively high yields in order to eliminate waste, save cost and speed-up the effective manufacturing time for a given number of die. Yields for wafers with high performance die with a large number of components can be very low.
One method used by memory chip makers for mitigating the impact of the occurrence of defective components within an integrated circuit die is to produce the die with more components, e.g. memory cells, than required. If there is a defective component the defective component is disconnected and one of the “surplus” components is utilized. This approach usually results in considerable waste of precious die area and resources on fabricating components that remain “surplus” even after replacing defective components. Such surplus components do not contribute to functionality and/or operational productivity. A significant number of die end up having numerous “surplus” components with perfectly good operational capabilities that are not utilized.
Another traditional attempt at addressing defective components is to remove functional capability if one functional component associated with a particular function is defective. For example, if a floating point acceleration component of a processor is defective, the floating point acceleration functionality is removed or disabled using conventional repair techniques, and the processor becomes a non-floating point acceleration processor. In addition, the end result is a usable integrated circuit with limited capability and that does not provide a full range of functionality (e.g., not able to perform floating point operations).
The present invention systems and methods enable configuration of functional components in integrated circuits. A present invention system and method can flexibly change the operational characteristics of functional components in an integrated circuit die based upon a variety of factors including manufacturing defects, compatibility characteristics, performance requirements, and system health (e.g., the number of components operating properly). In one embodiment, a present invention configuration system includes functional components, a distribution component, a functional component configuration controller and optionally a collection component. The functional components perform processing operations (e.g., graphics processing operations, floating point operations, etc.). The distribution component distributes workflow information (e.g., graphics processing information, floating point processing information, etc.) to the functional components. The functional component configuration controller configures operational characteristics of the functional components. The collection component “collects” the output or results from the functional components and aggregates the results of the operations for use in achieving a common objective.
In one exemplary implementation, the changes to operational characteristics of a functional component are coordinated with changes to other functional components. Workflow scheduling and distribution is also adjusted based upon the changes to the operational characteristics of the functional components. For example, the functional component configuration controller changes the operational characteristics settings and provides an indication of the changes to a workflow distribution component. The workflow distribution component changes the workflow schedule based upon the operational characteristics settings. For example, the work flow is diverted to or away from particular functional components.
The present invention system and method enable integrated circuit chips with defective functional components to be salvaged and facilitate increased wafer yield in integrated circuit manufacturing in one embodiment. Traditionally, the integrated circuits with the defective functional components would otherwise be discarded resulting in the costs of producing a wafer being assigned to fewer acceptable die. In one embodiment, a present invention system and method disables defective functional components in the die in a manner that maintains the basic functionality of the chip.
In one embodiment of the present invention, integrated circuit salvaging is performed in conjunction with chip testing. A chip is tested (e.g., in accordance with a built in self test) and defective functional components of the chip are identified. A determination is made if a defective functional component is one which does not have another functional component included in the die that is similar. In one embodiment, a distinction is made if the die does not have another functional component that can handle the work flow if the defective functional component is disabled. If such a defective functional component is identified, the die may be discarded since the die could not provide full functionality. If other functional components exist that can be used to perform the functionality of the defective component, a functional component configuration process (e.g., functional component configuration process 400) is performed on the chip based upon results of the testing.
In one embodiment of the present invention, the functional component configuration process disables defective functional components included in a chip. An indication of the defective functional component identification is received. A determination is made if the defective functional component is one of a plurality of similar functional components. In one embodiment of the present invention, the identified defective component (e.g., a pixel shader, vertex processor, floating point component, etc.) is compared against a list of other similar components that can provide the same functionality. In one exemplary implementation, the other similar components are examined to determine if they are parallel components to the defective functional component. The defective functional component is disabled if it is one of the plurality of similar functional components and another component can handle the workflow that would otherwise be assigned to the defective component. In one embodiment of the present invention, functional components associated with the defective component can also be disabled (e.g., to maintain product differentiation). Workflow is diverted from the disabled component.
In one embodiment, diverting the workflow is accomplished by providing notification of the disablement to a component that otherwise communicates information to the defective functional component. For example, a disabling component provides an indication (e.g., a bit map) to the distributor component and the distributor component does not provide information to the defective functional component. Instead, the work flow is diverted to other similar functional components.
In one embodiment of a present invention salvage method, definitions of characteristics of a die for a particular performance level are included and a die is marked accordingly. In one exemplary implementation, the test includes an indication of what defects are permissible in each performance level. For example, the test can include a first performance level in which a first plurality of parallel functional components can be disabled and a second performance level in which a second plurality of parallel functional components can be disabled. The present invention can also facilitate automatic binning of the die based upon performance levels as part of the testing procedure.
In one embodiment, centralized resources are utilized in the configuration of remote integrated circuits. A remote functional component configuration architecture facilitates configuration of functional components included in a remotely located integrated circuit die. In one exemplary implementation a die functional component reconfiguration request process is engaged in wherein a system requests a reconfiguration code from a remote resource. The code request includes a reconfiguration code permission indicator that indicates the requester is authorized to receive a reconfiguration code (e.g., the requester has made a requisite payment, has an authorized system, etc.). A reconfiguration code production process is executed in which a request for a reconfiguration code and a permission indicator are received, validity of the permission indicator is analyzed, and a reconfiguration code is provided. A die functional component reconfiguration process is performed on the die when an appropriate reconfiguration code is received by the die.
The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the invention by way of example and not by way of limitation. The drawings referred to in this specification should be understood as not being drawn to scale except if specifically noted.
Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with the preferred embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be obvious to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present invention.
Some portions of the detailed descriptions which follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means generally used by those skilled in data processing arts to effectively convey the substance of their work to others skilled in the art. A procedure, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps include physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, optical, or quantum signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present application, discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, “displaying” or the like, refer to the action and processes of a computer system, or similar processing device (e.g., an electrical, optical, or quantum, computing device), that manipulates and transforms data represented as physical (e.g., electronic) quantities. The terms refer to actions and processes of the processing devices that manipulate or transform physical quantities within a computer system's component (e.g., registers, memories, other such information storage, transmission or display devices, etc.) into other data similarly represented as physical quantities within other components.
Distribution component 110 selectively distributes information to functional components 131-134 (e.g., enabled functional components). It is appreciated that distribution component 110 can distribute a variety of information. For example, distribution component 110 can distribute workflow information. The workflow information can be information or data for processing in association with a common objective. For example, the workflow information can be graphics related information (e.g., a single stream of information in which various parts of the information stream include pixel information for sequentially configured pixels of an image). In one exemplary implementation, distribution component 110 receives a single stream of workflow information or data (e.g., graphics data) and distributes the workflow information to functional components 131-134. For example, the single stream of information can include information related to a first pixel, a second pixel, and a third pixel. Distribution component 110 receives the single stream of pixel information (e.g., a sequence of packets) and distributes the information (e.g., as individual packets) related to the first pixel to functional component 131, the information related to the second pixel to functional component 132 and the information related to the third pixel to functional component 133. In another exemplary implementation, the distribution component 110 receives a single stream of information related to floating point calculations and distributes information associated with a first floating point calculation to functional component 131, information associated with a second floating point calculation to functional component 132, and information associated with a third floating point calculation to functional component 133. In one embodiment, distribution component 110 can also receive multiple information streams and distribute the information to the functional components 131-134. It is appreciated that distribution component 110 can be implemented in a variety of embodiments, including embodiments in which distribution component 110 provides functions or performs tasks in addition to distributing the workflow information.
Functional components 131-134 can include a variety of implementations in which the functional components 131-134 perform different functional operations or tasks. In one embodiment functional components 131-134 provide similar functionality (e.g., perform parallel operations). For example, in one embodiment functional components 131-134 can perform graphics processing related tasks (e.g., shading, texturing, occlusion culling, etc). In another embodiment, functional components 131-134 can perform floating point related processing.
Collection component 140 “collects” the output or results from functional components 131-134. In one embodiment, collection component 140 concatenates or aggregates the results of the operations for use in achieving the common objective. For example, the collection component 140 can aggregate the results for communication to a graphics buffer. In another embodiment, the collection component 140 is a graphics buffer. In yet another embodiment, collection component 140 can aggregate the results of floating point calculations.
The components of integrated circuit 100 also cooperatively operate to flexibly configure functional component operational characteristics (e.g., enable/disable a functional component, change clock speed, change operating voltage, etc.). Functional component configuration controller 120 controls adjustments in operational characteristics (e.g., disable/enable, etc.) of one or more of the functional components 131-134 and can provide information to distribution component 110 and collection component 140 regarding the adjustment. For example, functional component configuration controller 120 can disable or enable a functional component (e.g., disable or enable functional component 132). Functional component configuration controller 120 can notify distribution component 110 of the change to functional component 132 operating characteristics (e.g., which of the functional components is enabled, disabled, etc.).
Distribution component 110 can use information about the operational characteristics of functional component 132 in distributing workflow information. In one embodiment, the distribution component 110 can factor the configuration of the functional components into distribution of information (e.g., workflow including data for processing) to the functional components. If one of the processor functional components is disabled (e.g., because it is defective), distribution component 110 distributes the information to the other remaining processor functional components to handle the “work flow”. For example, if functional component 132 is disabled by functional component configuration controller 120, distribution component 110 is notified that functional component 132 is disabled and distribution component 110 can route workflow to other functional components (e.g., 131, 133, and/or 134). If functional component 132 is enabled by functional component configuration controller 120, distribution component 110 is notified that functional component 132 is enabled and distribution component 110 can route workflow to functional component 132. Distribution component 110 can also distribute the information to remaining enabled functional components based upon the performance configuration (e.g., clock speed) of the functional components. In one exemplary implementation, tasks with greater performance demands (e.g., critical tasks) are routed to functional components with greater performance characteristics or capabilities (e.g., faster). For example, three dimensional (3D) graphics information can be routed to a high performance (e.g., high speed) graphics pipeline and two dimensional (2D) graphics information can be routed to a lower performance (e.g., slower speed) graphics pipeline. In one embodiment the information is distributed in accordance with scoreboarding algorithms.
In one embodiment of the present invention, functional component configuration controller 120 directs changes to operational characteristics of functional components 131-134. The operational characteristics can impact the performance of functional components 131-134. For example, functional component configuration controller 120 can change an operational characteristic state of functional components 131-134 (e.g., enable or disable the functional component). In one exemplary implementation, functional component configuration controller 120 can alter the speed at which a functional component operates (e.g., by changing a clock frequency) and/or the power consumed by a functional component (e.g., by changing the voltage supplied to the functional component). For example, functional component configuration controller 120 can direct clock source 137 to change a frequency of a clock signal supplied to functional components 131-134 and/or power supply 138 to change the voltage of a power signal supplied to functional components 131-134.
It is appreciated that the present invention is readily adaptable for utilization with a variety of functional components. Functional components 131-134 can be functional units that provide a variety of different functions (e.g., floating point, pixel shading, vertex shading, storage, buffering, etc.). In one exemplary implementation, the functional components can perform similar operations at substantially the same time (e.g., concurrently in parallel). In one embodiment of the present invention, the functional components are active functional components.
In one embodiment, the functional components are processor components (e.g., floating point components, pixel shader components, vertex processor components, etc.) included in a processing unit. It is appreciated that the present invention can be readily implemented in a variety of processing units, including a central processing unit (CPU), a graphics processing unit (GPU), and/or an embedded processing unit. In one exemplary implementation, the processing unit includes a scoreboarding algorithm for allocating tasks to the processor functional components (e.g., floating point components). As results are processed by the processor functional components the scoreboard tracks which operand is required by a processor functional component and schedules it. The results from the individual processor functional components can be combined to provide an overall result. The scoreboard can factor a functional component configuration into the scheduling of tasks. For example, if one of the processor functional components is disabled (e.g., because it is defective), the scoreboard reschedules the other remaining processor functional components to handle the processing work flow.
The present invention can be implemented in a pipeline type (e.g., a vector type, thread type, etc.) processing environment.
The components of pipeline integrated circuit 150 operate similar to the components of integrated circuit 100. For example, workflow information is diverted or routed in a similar manner. Functional component configuration controller 152 provides information to distribution component 151 regarding the operational characteristics of the functional components 171-174 (e.g., disabled, enabled, speed, voltage, etc). Distribution component 151 distributes information to the pipelines 171-174 based in part upon the operation characteristic information (e.g., distributes workflow information to enabled functional components and not disabled functional components). Collection component 140 “collects” (e.g., concatenates or aggregates) the output of pipelines 171-174 (e.g., concatenates or aggregates the results for storage in a graphics buffer). In one embodiment, functional component configuration controller 152 can direct clock source 175 to change a frequency of a clock signal supplied to functional components 171-174 and/or power supply 177 to change the voltage of a power signal supplied to functional components 171-174.
A present invention integrated circuit can be implemented at a variety of integration levels (e.g., a variety of die hierarchies and architectures).
The components of multiprocessor integrated circuit 190 operate similar to the components of integrated circuit 100. For example, workflow information is diverted or routed in a similar manner. Functional component configuration controller 192 provides information to distribution component 191 regarding operational characteristics of the functional components (e.g., disabled, enabled, speed, voltage, etc). Distribution component 191 distributes information (e.g., workflow data) to the processors 195-199. The distribution is based in part upon the operation characteristic information (e.g., distributes workflow information to enabled functional components and not disabled functional components). In one exemplary implementation, collection component 194 is a memory (e.g., a common cache) which “collects” or stores the output of processors 195-199. In one embodiment, functional component configuration controller 192 can direct clock source 181 to change a frequency of a clock signal supplied to functional components 195-199 and/or power supply 182 to change the voltage of a power signal supplied to functional components 195-199.
A distinction is made between performance and functionality in one embodiment of the present invention. In some instances, the present invention does not limit functionality when changing operational characteristics in the sense that a particular type of function or task is still capable of being performed even though the function or task may be accomplished at a different performance level. In one embodiment, a functional component configuration controller does not disable all the functional components capable of performing tasks in parallel. For example, if a die has two parallel floating point functional components in a processor and functional component configuration alters the enablement characteristic or state (e.g., disables) one of the floating point functional components, the work flow is “rerouted” to the remaining enabled floating point functional components. The performance level of floating point activities may change (e.g., slow down) since the work flow is being handled by one floating point functional component instead of two. However, the die still has the ability to provide the same functionality or task (e.g., perform the floating point functions).
In one embodiment of the present invention, integrated circuits (e.g., integrated circuit 100, integrated circuit 150, integrated circuit 190, etc.) are marked with a performance indicator that corresponds to the performance capabilities (e.g., the number of functional components that are enabled and/or disabled). The marking can be an electronically readable marking and/or an ink marking (e.g., on a die). The marking can be an indicator of the quality rating of the integrated circuit. The marking can also correspond to a performance metric associated with the integrated circuit (e.g., a processing speed, bandwidth, etc.).
It is appreciated that the functional component configuration controllers 120, 152, and/or 192 can direct functional component changes in accordance with a variety of objectives. For example, a functional component configuration controller can alter operational characteristics of functional components based upon yield issues, compatibility issues, performance issues, system “health” issues, etc. It is also appreciated that functional component configuration controllers 120, 152, and/or 192 can include a variety of implementations to achieve the objectives, including a software programmable register or mask, hardcoded mask, etc.
In one embodiment, a functional component configuration controller (e.g., 120, 152 and/or 192) directs changes in the operational characteristics of functional components to address yield issues. The present invention has the benefit of facilitating increased wafer yield in integrated circuit manufacturing. A present invention system and method enables integrated circuits with some defective functional components to be salvaged. Traditionally, die with defective functional components are discarded resulting in the costs of producing a wafer being assigned to fewer acceptable die. The present invention permits some die with defective functional units to be used to perform the same types of functions and thereby maintain functionality even though the disablement of the defective components may impact performance. Increasing the number of useful die on a wafer permits the cost of wafer production to be assigned to a greater number of acceptable die. By permitting the fixed cost of wafer production to be assigned to a greater number of die, the cost per die can decrease, even though the lower performing die may be sold at a lower price.
The present invention facilitates “salvaging” of die even though some of the die may operate at different performance levels. In one exemplary implementation, the die that would otherwise be discarded are able to provide the same functionality in the sense that the die execute the same type of tasks. For example, a processor with parallel floating point functional components capable of performing floating point operations is still able to perform floating point operations since in one embodiment the present invention does not disable all the parallel floating point components and “reroutes” workflow from the disabled parallel floating point components to the remaining floating point components. Die with more disabled components may perform the tasks at a different level (e.g., slower) because some parallel components are disabled. However, the die still has the ability to provide the same functionality (e.g., perform the same tasks).
In one embodiment, a functional component configuration controller (e.g., 120, 152 and/or 192) directs operational characteristic changes (e.g., enable, disable, etc.) to functional components during manufacturing testing. For example, a functional component configuration controller (e.g., 120, 152 or 192) disables a functional component (e.g., 132, 173, or 198 respectively) if testing indicates the functional component is defective and enables a functional component (e.g., 131, 174, 197 respectively) if testing indicates the functional component is not defective.
In one embodiment of the present invention, a functional component configuration controller (e.g., 120, 152 and/or 192) directs changes in the operational characteristics of functional components to address “self health” issues. In one exemplary implementation, the functional component controller addresses self health issues in the “field” or after initial shipment from the manufacturer. In one exemplary implementation, an integrated circuit is capable of running in the field “self-health” tests. For example, if a “self-health” test results in an indication of a defective functional component, a functional component configuration controller (e.g., 120, 152 and/or 192) disables the defective functional component and provides an indication that the functional component is disabled to a distribution component (e.g., 110, 150, or 191). In one embodiment of the present invention, the self health test is compliant with International Electrical and Electronic Engineering (IEEE) Standard 1149.1 (also referred to as Joint Task Action Group (JTAG) testing). In an alternate embodiment, the self health test is a proprietary test for checking the operational integrity of the system. In yet another embodiment, a functional component is enabled if a “self health” test in the field indicates the functional component is not defective.
In yet another embodiment, if a non-enabled non-defective functional component that performs similar types of tasks or functions as a defective functional component is available, the non-enabled non defective functional component is enabled if the defective component is disabled. For example, integrated circuit 100 of
In one embodiment of the present invention, a functional component configuration controller (e.g., 120, 152 and/or 192) directs changes in the operational characteristics of functional components to address compatibility issues. In one embodiment, a functional component controller included in a graphics accelerator is capable of recognizing chipsets that are compatible with features of the graphics accelerator and changes operational characteristics of the graphics accelerator accordingly. For example, if the functional component configuration controller is controlling operational characteristics of graphics pipelines, the functional component configuration controller can enable a higher number of graphics pipelines if the chip set supports it and is compatible with the utilization of a higher number of graphics pipelines. For example, a graphics accelerator and a chip set are manufactured by the same manufacturer and the functional component controller included in the graphics accelerator can receive a signal identifying a chip set included in the same system as the graphics accelerator. In one embodiment of the present invention, compatibility is established by a driver and a functional component controller directs changes to the operational characteristics of the functional components accordingly.
In one embodiment of the present invention, a functional component configuration controller (e.g., 120, 152 and/or 192) directs changes in the operational characteristics of functional components to address performance issues. In one embodiment, performance mask 40 provides an indication of operational characteristics for functional components based upon performance issues. For example, a particular application is being run and desirable supported functional component operational characteristics are enabled. If the application is a graphics application additional graphics pipelines can be enabled and/or the clock speed of existing graphics application pipelines can be increased. In one embodiment of the present invention, the type of the system can be factored into performance operational changes, for example in mobile devices the performance can be adjusted to conserve power.
It is appreciated that there are a variety of functional component configuration controller embodiments for implementing functional component changes in accordance with different objectives.
Priorities can be assigned to the different objectives or masks. For example, yield mask 20 can be assigned a higher priority than performance mask 40. In this example, the operational characteristic setting value in cell 98 controls over the operational characteristic setting value in cell 97. If the setting value in cell 98 indicates that the functional component associated with column 12 is disabled, the functional component is disabled regardless of the setting value in cell 97. The values in mask array 10 can also be utilized in a variety of algorithms that account for a variety of considerations in determining an operational characteristic setting that is implemented by a functional component configuration controller.
Yield mask 20 provides an indication of functional components that are disabled due to yield issues (e.g., defects). For example, yield mask 20 includes operational characteristic setting values that cause functional components to be disabled if the functional components have a manufacturing defect. In one exemplary implementation, a functional component is permitted to be disabled if there is another operational functional component that can handle the work flow.
Compatibility mask 30 provides an indication of operational characteristics for functional components based upon compatibility issues. For example, a particular processor and chip set can exchange identification with one another and based upon the exchange of identification, compatible supported functional component operational characteristics can be enabled. In one embodiment of the present invention, compatibility is established by a driver and a corresponding operational characteristic setting value is entered in compatibility mask 30.
Performance mask 40 provides an indication of operational characteristics for functional components based upon performance issues. For example, a particular application is being run and a value is entered into performance mask 40 enabling corresponding desirable supported functional component operational characteristics. If the application is a graphics application additional graphics pipelines can be enabled and/or the clock speed of existing graphics application pipelines can increase. In one embodiment of the present invention, the type of the system can be factored into performance operational changes, for example in mobile devices a value entered in performance mask 40 can direct a performance adjustment to conserve power. For example, direct changes to operational characteristics of functional components, including disabling/enabling functional components, adjusting speed, voltage, etc.).
Self healing mask 50 provides an indication of operational characteristics for functional components based upon field testing issues. For example, results from testing operations are utilized to determine changes in operational characteristics for functional components. In one exemplary implementation, a field test indicates that an enabled first functional component is defective. The operational characteristic setting value in the self healing mask cell associated with the first functional component is changed to indicate the first functional component is disabled and the operational characteristic setting value in the self healing mask cell associated with a second functional component that is disabled is changed to indicate the second functional component is enabled. By changing the respective operational characteristic setting values of the first and second functional components the defective first component is disabled and prevented from producing more problems and enabling a disabled second functional component allows the second functional component to perform the workflow that would otherwise be routed to the first functional component and thus the system in effect heals itself in that the same work flow is still able to be performed without defects.
The components of computer system 200 cooperatively operate to provide versatile functionality and performance. The operating characteristics of functional components included in computer system 200 can change dynamically. In one exemplary implementation, the components of computer system 200 cooperatively operate to provide predetermined types of functionality, even though some of the functional components included in computer system 200 may be defective. Communications buses 291, 292, 293, 294, 295 and 297 communicate information. Central processor 201 processes information. Main memory 202 stores information and instructions for the central processor 201. Removable data storage device 204 also stores information and instructions (e.g., functioning as a large information reservoir). Input device 206 provides a mechanism for inputting information and/or for pointing to or highlighting information on display 220. Signal communication port 208 provides a communication interface to exterior devices (e.g., an interface with a network). Display device 220 displays information in accordance with data stored in frame buffer 215. Graphics processor 211 processes graphics commands from central processor 201 and provides the resulting data to graphics buffers 215 for storage and retrieval by display monitor 220.
The operational configurations of the functional components included in computer system 200 are flexibly adaptable to meet a variety of objectives. For example, operational configurations of the functional components included in computer system 200 are configurable to maintain execution of a type of function even if some of the functional components are disabled. In one exemplary implementation, central processor 201 and graphics processor 211 are still capable of executing the same type of processing functions and main memory 202 stores information even through some of the functional components (e.g., floating point component, pixel shader component, memory cell component, etc) are disabled. In one embodiment, the processors include a plurality of functional components for performing processing operations. The operational characteristics of the functional components can be altered. In one embodiment, the processors include a plurality of functional components for performing processing operations, wherein defective functional components included in the plurality of functional components are disabled. The processors also include a workflow control component for dispensing workflow to enabled processing components and preventing distribution of workflow to the disabled defective components. In one exemplary implementation, computer system 200 can continue to provide full functionality even through the functionality may be provided at a reduced performance level (e.g., slower).
It is appreciated that the present invention can be implemented in a variety of embodiments. In one exemplary implementation the present invention can be utilized in processing systems utilized to provide a variety of graphics applications including video games. For example, the present invention can be utilized to disable defective components in a game console, personal computer, personal digital assistant, cell phone or any number of platforms for implementing a video game. It is also appreciated that references to video game application implementations are exemplary and the present invention is not limited to these implementations.
The components of graphics pipeline 300 cooperatively operate to perform graphics pipeline operations even if some of the operational characteristics of functional components in the pipeline are changed (e.g., disabled/enabled). Functional component configuration controller 350 can change the operational characteristics of vertex processors 311 through 314, pixel shaders 321 through 324, and/or raster operation components 331 through 334. Functional component configuration controller 350 can make a variety of changes to the operational characteristics, including enabling/disabling a functional component, changing the clock speed of the functional component and/or increase the voltage supply to the functional component. The functional component configuration controller 350 can make the changes for a variety of reasons, including yield issues (e.g., the function component is defective and/or associated with a defective component), compatibility issues, performance issues and/or system “health” issues. Functional component configuration controller 350 also provides information on operational characteristic changes to pipeline input 310, rasterizer 320, pre-raster operation (ROP) component 330, and pipeline output 340. Pipeline input component 310 receives graphics pipeline information and distributes corresponding packetized graphics pipeline information to vertex processors 311 through 314 remaining enabled. Vertex processors 311 through 314 perform vector shading on the respectively received graphics pipeline information and forward the resulting information to rasterizer 320. Rasterizer 320 determines which pixels to shade and distributes packetized vector shaded graphics pipeline information to pixel shaders 321 through 324. Pixel shaders 321 through 323 perform pixel shading calculations on the packetized vector shaded graphics pipeline information and forward the results to pre-raster operation (ROP) component 330.
In one embodiment, the pixel shaders 321 through 324 can also perform texture operations. The texture operations can be performed by texture shader components (e.g., corresponding to the pixel shaders). Pre-raster operation (ROP) component 330 gathers the vector shading information and distributes packetized pixel shaded information to raster operation components 331 through 334. Raster operation components 331 through 334 perform additional rasterizing processing on the packetized pixel shaded information (e.g., performing color binding and Z buffer processing) and forwards the results to pipeline output 340. Pipeline output 340 aggregates the graphics pipeline information into a single output stream. Alternatively, the Functional Component Configuration Controller 350 may be implemented as a cross bar or multiplexer structure positioned between the respective levels of the functional components in the pipeline.
The present invention can also be applied to portions of a frame buffer interface that are split into multiple partitions. In one exemplary implementation, the frame buffer interface includes multiple similar modules that operate as functional components that communicate with a memory (e.g., a portion of a DRAM that makes up the frame buffer). If one of the modules are defective it can be disabled and the workload of the defective module is reassigned to another module (e.g., based upon the portion of the memory addresses associated with the module). For example, the mapping of frame buffer interface modules to memory addresses are remapped so that the entire memory is still available to the chip.
In step 410, an indication of a functional component configuration (e.g., operational characteristic) alteration trigger event is received. In one embodiment of the present invention, the indication of the alteration trigger event is received by a functional component controller (e.g., 120, etc.). The indication can include an indication of the configuration change to be made (e.g., disable, enable, increase/decrease speed and/or voltage, etc.). In one embodiment, the functional component configuration alteration trigger event is received from an internal component of the integrated circuit (e.g., an internal testing system, a driver, an application, etc.). The indication of a functional component configuration alteration trigger event can also be received from a component external to the integrated circuit (e.g., an external testing system, the internet, a centralized configuration system, etc.).
It is appreciated that the indication and configuration alteration trigger event can be associated with a variety of operational objectives (e.g., application, pay per use, market segmentation, etc.). An alteration trigger event can be associated with a yield issue. For example, the event can be associated with testing operations detecting a defective functional component and an indication identifying the defective functional component is received (e.g., by a functional component controller). In one embodiment of the present invention, the indication of a defective functional component is received from a testing system. For example, an International Electrical and Electronic Engineering (IEEE) Standard 1149.1 (also referred to as Joint Task Action Group (JTAG) testing) compliant testing system and/or a proprietary operational integrity test (e.g., a proprietary scan test mechanism). An alteration trigger event can be associated with a compatibility issue. For example, a signal indicating a component has a predetermined compatibility is received. An alteration trigger event can be associated with a performance issue. For example, a signal is received indicating a new and/or different application is being loaded, a pay per use authorization is granted, and/or the integrated circuit is included in a mobile device in which power conservation is desirable. An alteration trigger event can also be associated with a self test and healing issue.
In step 420, a determination is made if an indicated functional component configuration alteration (e.g., operational characteristic alteration) is valid. For example, a determination of an authorized operational characteristic for the functional component is made. In one embodiment, the indication received in step 410 is an encoded bit stream. The bit stream is decoded and the resulting value is examined for valid authorization to trigger a functional component configuration alteration. In one embodiment of the present invention, an encoded indicator is analyzed. The analysis includes decoding the indicator and comparing it to a predetermined list of different possible operational characteristic settings for the functional component. For example, the value of the decoded indicator is compared to values in a predetermined list of authorized trigger indications or values, wherein the values in the list are associated with a particular operational characteristic setting.
It one embodiment of the present invention, the functional component configuration alteration action is also checked for validity. For example, when performing a functional component disablement in association with yield and self healing issues, in one embodiment a determination is made if there is a second functional component (e.g., in parallel) that can perform similar functions on the workflow information that would have otherwise went to a defective functional component. For example, a determination is made if a defective functional component is one of a plurality of similar functional components. In one embodiment of the present invention, the type of defective component is compared to a list of multiple components that provide similar functions. For example, the defective component is identified (e.g., a pixel shader, vertex processor, floating point component, etc.) and the identified functional component is compared against a list of other similar components that can provide the same functionality. In one exemplary implementation, the other similar components are examined to determine if they are parallel components to the defective functional component. If there is a second functional component that can perform the workflow the first functional component can be disabled (e.g., if the first functional component is defective).
In step 430, a functional component configuration alteration is directed. In one embodiment of the present invention, the functional component configuration alteration (e.g., operational characteristic alteration) is directed by a functional component controller (e.g., 120, 152, 192, etc.). In one embodiment of the present invention, the functional component configuration change (e.g., disabling, enabling, etc.) is accomplished by programming a value (e.g., in a register) that controls the configuration (e.g., operational characteristics) of the functional component. Based upon the value in the register a signal is sent to the functional component which changes the configuration (e.g., disables, enables, etc.) the component. In one exemplary implementation, the values are configured in a mask (e.g., mask10). It is appreciated that there are a variety of present invention methods for altering the configuration (e.g., altering operational characteristics) of a functional component. For example, the disabling of a defective functional component can accomplished by fusing communication lines to the defective functional component. The defective functional component can also be disabled in manner that ensures the defective functional component does not generate spurious traffic. A receiving component can also be notified of a defective component and programmed to ignore information coming from the defective functional component. Functional component configurations can also be altered by soft coded methods.
In one embodiment, on going operations of the functional components are monitored and factored into the configuration operations of step 430. For example, the system “health” is checked or tested and the results are utilized in determining changes to operational characteristics. For example, if a first functional component fails a self diagnostic test the functional component can be disabled. If a second functional component is available it can be activated to “replace” the first functional component. For example, if the second functional component works perfectly fine but was previously disabled for some other reason, it can be enabled to replace the functional component that failed the test. In one exemplary implementation, application activation is monitored and operational characteristics of functional components altered accordingly. For example, if a high performance graphics application is activated, the operational characteristics of functional components can be increased (e.g., faster clock setting) and/or additional functional components (e.g., additional graphics pipelines) can be enabled or disabled.
Changes of components in a system (e.g., adding new components) can also be monitored and operational characteristics changed to accommodate the component changes. For example, if a particular type of graphics processor is coupled to a particular type of chip set, an identification indication can be communicated and the operational characteristics of functional components can be altered accordingly. The identification permits predetermination of compatibility and support for enhanced features. In one embodiment, the identification is encoded. The encoding prevents malicious tampering with operational characteristic settings. For example, encoding provides protection from attempts at inappropriately reducing operational characteristics of functional components and/or increasing operational characteristics without compatibility assurance which could otherwise potentially introduce complex faults that are difficult to identify.
In one embodiment of the present invention, the operational characteristic changes are coordinated amongst functional components. For example, a properly operating functional component that is closely associated with a changed functional component (e.g., in the same pipeline, thread, etc) can also be changed. In one exemplary implementation, operational changes are coordinated amongst functional components to maintain product differentiation. For example, if a lower performance chip is specified as having one less pixel shading component and one less vertex shading component, both a pixel shading component and a vertex shading component can be disabled to maintain product differentiation.
In step 440, workflow is diverted in accordance with the alteration to a functional component. For example, the work flow can be diverted to other similar functional components. In one embodiment, diverting the workflow is accomplished by providing notification of the configuration alteration (e.g., enablement, disablement, etc.) to a component that otherwise communicates information to the altered functional component. For example, a functional component controller (e.g., 120, etc.) provides an indication of a functional component configuration alteration (e.g., change in operational characteristic) to a distribution component (e.g., 110, etc.) and the distribution component routes work flow information accordingly. For example, if a first functional component is enabled workflow is routed or scheduled and forwarded to the first functional component. If a first functional component is disabled the workflow is routed or scheduled to another enabled functional component.
In one exemplary implementation, the workflow is diverted or routed to faster or slower functional components. For example, workflow contents are analyzed and parts of the workflow associated with higher performance activities are routed to a faster functional component (e.g., a functional component operating at a higher clock rate) and parts of the workflow associated with lower performance activities are routed to a slower functional component. Pixels in an area of graphics image that are changing rapidly (e.g., pixels towards the center of the display) can be routed to a faster functional component (e.g., high clocked shader) and pixels in an area of graphics image that are changing slowly (e.g., pixels towards the edge of the display) are routed to a slower functional component (e.g., low clocked shader).
The functional component operational characteristic changes (e.g., disabling, etc.) can be coordinated in a manner that reduces impacts to other components. In one embodiment, properly operating functional components can be programmed or reconfigured to be tolerant of possible garbage (e.g., illegal signal combinations) on the outputs of the disabled components. For example, a properly operating functional component can be directed to ignore information from a disabled component. A receiving component (e.g., collection component 140) can also be notified of an operational characteristic change in a functional component and programmed to react accordingly. For example, if the speed of the functional component is lowered the receiving component can be programmed not to idle while waiting for information coming from the functional component but to check back later or if the functional component is disabled to ignore information from the functional component. If the functional component is disabled the receiving component can be programmed to ignore signals from the functional component.
In step 510, a chip is prepared for testing. A chip is placed in a testing system and the testing system is initialized. In one embodiment of the present invention, initial states for a scan test are entered in scan test cells. For example, the chip can be prepared for testing in accordance with International Electrical and Electronic Engineering (IEEE) Standard 1149.1 (also referred to as Joint Task Action Group (JTAG) testing). In one embodiment of the present invention, a custom type of testing that is compatible with testing capabilities of the chip (e.g., a proprietary and/or non-JTAG-compliant testing) is utilized.
In step 520 the chip is tested. In one embodiment of the present invention the testing comprises identifying defective functional components of the chip. In one exemplary implementation of the present invention, a built in self test (BIST) is performed. For example, a scan test is included in the BIST in which test vectors are applied to stimulate certain aspects of a circuit (e.g., a functional logic component) and the resulting output from the circuit is captured. The scan test chain is designed to scan or shift scan test information (e.g., test vectors) to functional components in a circuit via a scan test chain, cause a functional component to perform an operation on the scan test information, capture the resulting information and then shift the resulting information out via scan test cells of the scan test chain. The resulting information is then analyzed for errors (e.g., compared to predetermined correct results). The test vector patterns can be provided by an automated test pattern generation (ATPG) tool.
In one embodiment of the present invention, particular functional components that are defective are identified. In one exemplary implementation, the output results of a scan test provide an indication of which functional components are defective. For example, the test pattern results are analyzed and the defective functional components identified. The present invention can determine if a defective functional component is one which does not have another functional component included in the die that is similar. In one embodiment, a distinction is made if the defective functional component is critical and/or the die does not have another functional component that can handle the work flow if the defective functional component is disabled. If such a functional component is identified, the die is discarded in one embodiment of the present invention since the die could not provide full functionality.
In one embodiment of the present invention, disabling components are utilized to facilitate identification of a defective component. In one exemplary implementation, test vector operations are performed by a plurality of similar functional components (e.g., pixel shaders 321 through 324). If there is an erroneous result further testing is performed. A first one of a plurality of functional components (e.g., pixel shader 321) is disabled by a disabling component and test vector operations are performed by the remaining functional components. Alternatively, in the testing process software simulation can be utilized to simulate the disablement of a functional component. For example, pixel shader 321 is disabled and test vector operations are performed by pixel shader 322 through 324 and the results analyzed. If there are no erroneous results the first functional component is identified as a defective component. If there are continued erroneous results a second one of a plurality of functional components (e.g., pixel shader 321) is disabled by a disabling component and test vector operations are performed by the remaining functional components. If there are no erroneous results the second functional component is identified as a defective component. The process of elimination continues until the defective component is identified.
In step 530, a functional component configuration process (e.g., functional component configuration process 400) is performed on the chip based upon results of the testing. In one embodiment of the present invention, the functional component configuration process disables one or more of a plurality of homogenous functional components (e.g., execution components) of the chip if the functional components are defective. For example, a disable signal is issued to the defective functional component.
In one embodiment, reduced performance circuit salvage method 500 includes programmably reconfiguring the chip to permit other functional components to perform the functions of the disabled functional component. For example, a mask is programmed into a distributing component that identifies disabled functional components and the work flow can be distributed between the remaining functional components. It can be programmed as either a software loadable register or a hardcoded mask type program that is performed at test time. There are a variety of techniques that can be utilized including programmable non-volatile memory, fuses, wire bond straps, etc.
In one embodiment of reduced performance circuit salvage method 500, a program in the tester includes definitions of characteristics of a die for a particular performance level. In one exemplary implementation, the tester includes an indication of what defects are permissible in each performance level. For example, the tester can include a first performance level in which a first plurality of parallel functional components can be disabled and a second performance level in which a second plurality of parallel functional components can be disabled. The performance level can also correspond to the number of functional components that are enabled. The present invention can also facilitate automatic binning of the die based upon performance levels as part of the testing procedure.
Die salvage testing system 650 tests die 610. Testing module 680 provides test vectors to testing interface 633 which passes the test vectors on to scan test cells 621 through 625. The information in scan test cells 621 through 625 are fed into functional components 611 through 614 and distributor 631, which perform an operation on the scan test information. The results are also captured by scan test cells 621 through 625 and communicated to testing interface 633 which passes them to testing system 650 for analysis. Testing module 680 analyzes the results and provides an indication of defective functional components to defective resolution module 670. Defective resolution module 670 determines if a die can be salvaged by disabling functional components.
Functionality maintenance module 671 determines if the identified functional component is included in a group that is permitted to be disabled. In one embodiment, functionality maintenance module 671 determines if there are other functional components that can handle the workflow of the identified (e.g., defective) functional component. For example, the workflow can be transferred or rerouted to another functional component. In one exemplary implementation, functionality maintenance module 671 checks the identified functional component against a predetermined list of components that are allowed to be disabled (e.g., other components can handle the workflow).
Corresponding component detection module 672 determines if there are related functional components that should be disabled. The related functional components can be properly functioning components. In one embodiment of the present invention, a functional component that is closely associated with a defective functional component (e.g., in the same pipeline, thread, etc.) is identified. For example, if the functional component is downstream from a defective component, the properly functioning component can be disabled (e.g., powered down) to prevent switching activities and corresponding power consumption. In one exemplary implementation, functional components can be disabled to maintain product differentiation. If other functional components that should be disabled are identified, the identity of these components is fed back into functionality maintenance module 671 to determine if disabling them would impact functionality.
Disabling module 673 directs functional component disablement (e.g., disablement of functional components 611, 612, 613 or 614). In one embodiment of the present invention, disabling module 673 sends a disablement signal directly to a functional component via the test interface 633. In an alternate embodiment, disabling module 673 sends a signal to a disabling component (not shown) in die 610. Disabling module 673 disables a functional component if functionality maintenance module 671 provides an indication that it is permissible to disable the component (e.g., it will not eliminate functionality). In one exemplary implementation, functionality maintenance module 671 allows disabling module 673 to disable a functional component even if it reduces performance, as long as it does not reduce functionality.
Die marking module 674 marks a die. In one embodiment of the present invention, die marking module 674 marks a die based upon a performance criteria. Die marking module 674 also provides a marking or indication if a die is rejected. The die can be rejected because functionality maintenance module 671 provides an indication that a defective functional component should not be disabled and/or the performance of the die drops below a predetermined level. In one exemplary implementation, a die is marked based upon the functional components that are disabled. For example, if a predetermined number and/or type of functional component is disabled the die is marked accordingly.
In one embodiment of the present invention, die marking module 674 also marks a wafer upon which the die is located. In one embodiment of the present invention, die marking module 674 marks a wafer based upon a yield criteria. The yield criteria can be segmented for difference performance levels. For example, the yield marking can indicate that a certain number or percentage of the die in a wafer have no disabled functional components, a certain number or percentage of die have a set number of disabled functional components, and a certain number or die are rejected or unsalvageable.
In step 710, a plurality of die with similar configurations are fabricated. In one embodiment of the present invention, the plurality of die are fabricated on a single wafer. In one embodiment of the present invention, the similar configurations enable each of the plurality of die to perform a predetermined type of functionality. In one exemplary implementation, the same lithographic process steps are utilized to fabricate the plurality of die. In one embodiment, similar configuration can be determined by reviewing data sheet information on the die. For example, the data sheet information can include the die size (e.g., number of transistors), functionality indicators, and/or performance indicators, and/or information on product lines the die is associated with (e.g., by determining what the die is sold for). Similar configuration can also be indicated if the dies have substantially the same fabrication costs.
In step 720, a component is prevented from participating in productive contribution within one of the plurality of die without eliminating the ability of the die to perform a function associated with the component. In one embodiment of the present invention, the removal of component productivity may impact performance but does not eliminate the type of functionality. In one exemplary implementation, the component is prevented from participating in productive contribution by disabling the component. The work flow of the disabled component can be redirected to other components. In one embodiment, preventing a component from participating in productive contribution can be detected by analyzing data sheet information. For example, if a die has a product sheet applicable to a product line that provides the same types of functionality at different performance levels. Alternatively, another indication of whether a component is prevented from participating in productive contribution is if a determination of which data sheet information applies to a die is not made until after testing is performed (e.g., selection of a data sheet information corresponds to alterations in the die components based upon the results of testing).
Each of the plurality of die are classified in step 730 based on differentiated performance levels for the functionality. In one exemplary implementation, the die are included in products that are distributed or sold at different prices in correlation to the performance level at which the functionality is provided. Dies with the same design are distributed with different performance levels (e.g., different speeds, bandwidth, etc.) in one embodiment of the present invention.
Performance management component 820 receives information indicating a change to operation components. For example, a test result indicates that an operation component is defective. Performance management component 820 identifies a subset of operation components 831 through 834 that the information applies to. For example, a subset of operation components that are defective and that subset is not enabled for use. In one exemplary implementation, a subset that is not defective is enabled. For example, if testing results indicate that operation component 831 and 834 are defective then operation component 820 enables operation component 832 and 833 but does not enable operation component 831 and 834. If operation component 831 and 834 are enabled performance management component 820 disables them. Performance management component 820 also provides an operational characteristic status indication to allocation component 810. For example, the operational characteristic status indication indicates which of the functional components is enabled and which is disabled. Each of the operation components that are enabled are capable of executing similar functions that would otherwise be executed by the operation components that are not enabled.
In step 910, a wafer is fabricated. The wafer includes a plurality of die and each one of the plurality of die have a functional component capable of performing a plurality of sub-tasks in parallel using a plurality of functional sub-components. For example, each die can include a pipeline that performs a variety of graphics sub-tasks (e.g., shading, texturing, aliasing, rasterizing, etc.) by functional sub-components (e.g., a shader, a rasterizer, etc). In one embodiment of the present invention the wafer is fabricated using lithographic processes.
In step 920, for each die each one of the plurality of functional sub-components that are operable and each one of the plurality of functional sub-components that are not operable are identified. In one embodiment, the operable and non operable functional sub-components are identified as part of a conventional circuit testing process. For example, predetermined input are fed into a functional sub-component and the resulting output is examined. The output information is examined for errors (e.g., the output is compared to predetermined correct results). If the output information includes an error (e.g., if the output does not match predetermined correct results) the functional sub-component is identified as not operable.
In step 930, operation of each one of said plurality of functional sub-components that are identified as not operable is disabled. In one embodiment, each one of said plurality of functional sub-components that are identified as operable can be enabled. In one embodiment, the non operable functional sub-components are disabled and operable functional sub-components are enabled by a hard “coded” mechanism. For example, foundry laser trim bits are utilized to configure or disable functional sub-components. In another embodiment, software programmable information is utilized to configure (e.g., disable or enable) functional sub-components.
In step 940, each one of the plurality of die are sorted into a performance class based on the operable status (e.g., components identified as operable or not operable in step 930). For example, the die can be sorted into a high performance class in which all or a significant percentage of the functional sub components are operable and enabled. The die can be sorted into a medium performance range class in which less of the functional sub-components remain enabled. These performance ranges can be designated as salvageable. There can also be a performance class in which the die do not meet a minimum and are discarded (or subjected to some other corrective action to possibly fix the problem).
In step 950, the die sorted in a performance class designed as salvageable are salvaged. For example, a die with some disabled functional sub components is used to perform processing tasks, even though the speed at which the tasks are performed is reduced.
Remote configuration environment 1100 includes integrated circuit die 1110 and remote configuration control module 1150. Integrated circuit die 1110 comprises, configuration module 1133, distribution component 1131 and functional components 1111 through 1114, with each functional component and distribution component 1131 including operational characteristic registers 1121 through 1125 respectively. Remote configuration controller module 1150 comprises encoding module 1180 and configuration resolution module 1170.
Remote configuration controller module 1150 controls configuration of functional components in integrated circuit die 1110. In one embodiment, remote configuration controller module 1150 is off chip (e.g., in a driver). Configuration resolution module 1170 determines the operational characteristic settings for functional components of integrated circuit die 1110. In one exemplary implementation, configuration resolution module 1170 participates in an automated functionality negotiation process (e.g., capacity on demand) in which agreement is reached on upgraded operational characteristics and a functionality indicator is dynamically changed as part of the functionality negotiation process. The operational characteristics are set to maintain product differentiation in one exemplary implementation. Configuration resolution module 1170 forwards an operational characteristic indicator value to encoding module 1180. Encoding module 1180 encodes the operational characteristic indicator value (e.g., with a key, hash value, etc.) and forwards the encoded operational characteristic indicator value to configuration module 1133.
Configuration module 1133 directs functional component configuration. For example, configuration module 1133 directs changes to functional component operational characteristic settings (e.g., for functional components 1111, 1112, 1113 or 1114) based upon the encoded operational characteristic setting value received from encoding module 1180. Configuration module 1133 can decode the functional component operation characteristic indicator value. Configuration module 1133 forwards the decoded value to functionality tracking module 1137 for comparison to a corresponding operational characteristic setting.
Functionality tracking module 1137 directs maintenance of functional component operational characteristics. In one exemplary implementation, functionality tracking module 1137 provides a correlation between a decoded functionality indicator value and a particular operational characteristic setting. For example, functionality tracking module 1137 checks a functionality indicator against a predetermined correlation list of operational characteristic settings. Functionality tracking module 1137 can also determine if there are other functional components that can handle workflow of an identified functional component.
In step 1210, a die functional component reconfiguration request process is engaged in wherein a system requests a reconfiguration code from a remote resource. In one embodiment, a reconfiguration request process includes requesting and receiving a die functional component reconfiguration code. In one exemplary implementation, the die reconfiguration code is utilized by a functional component controller (e.g., 120, etc.) to reconfigure functional components. It is appreciated the request and receipt of a die functional component reconfiguration code can be communicated via a variety of communication systems. For example, the request and the die functional component reconfiguration code can be communicated via the Internet. In one embodiment, the request includes a reconfiguration code permission indicator that indicates the requester is authorized to receive a reconfiguration code (e.g., the requester has made a requisite payment, has an authorized system, etc.).
In one embodiment, the die functional component reconfiguration request process includes a reconfiguration code permission indicator request process to obtain a reconfiguration code permission indicator. In one exemplary implementation, the reconfiguration code permission indicator request process comprises forwarding a payment and request for a permission indicator and receiving a response to the request and payment for the permission indicator. For example, a customer or user makes an electronic payment via the internet to a remote central resource and receives a permission indicator (e.g., bit stream code) in return.
In step 1220, a reconfiguration code production process is executed. In one exemplary implementation, a remote resource processes the request for the reconfiguration code. In one embodiment, the reconfiguration code production process comprises receiving a request for a reconfiguration code and a permission indicator, analyzing validity of the permission indicator, and providing a reconfiguration code if the permission indicator is valid. For example, a remote resource receives a request to increase the number of graphics pipelines activated in a system. The remote resource analyzes if the requester has made a requisite payment. If the requisite payment has been made the remote resource forwards the reconfiguration code for increasing the number of graphics pipelines activated in a system.
In one embodiment, a reconfiguration code production process includes engaging in a reconfiguration code permission indicator response process to respond to a request process to obtain a reconfiguration code permission indicator. In one exemplary implementation the reconfiguration code permission indicator response process includes receiving payment for a permission indicator and forwarding the permission indicator in response to receiving the payment.
In step 1230, a die functional component reconfiguration process is performed if the reconfiguration code is received by a system (e.g., received from a remote resource). The die functional component reconfiguration process includes reconfiguring a die functional component (e.g., functional component 131, 132, 133, 134, etc.) in accordance with the reconfiguration code. In one embodiment the die functional component reconfiguration process is similar to functional component configuration process 400.
Thus, the present invention enables flexible operational configuration of integrated circuit dies and enhances product differentiation. The dies can be utilized in a product line with multiple performance levels. The present invention also facilitates the manufacture of single die capable of being dynamically configured for high performance tasks or low performance tasks permitting power savings and economic differentiation. The present invention also facilitates conservation of manufacturing resources and salvaging of dies with defective components.
The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto and their equivalents.
This application claims the benefit of commonly-owned U.S. Patent Provisional Application Ser. No. 60/503,710, filed Sep. 15, 2003, entitled “A SYSTEM AND METHOD FOR CONFIGURING SEMICONDUCTOR FUNCTIONAL COMPONENTS” which is hereby incorporated by this reference. This application is also related to the following Applications: U.S. patent application Ser. No. 10/740,721, entitled “AN INTEGRATED CIRCUIT CONFIGURATION SYSTEM AND METHOD”, filed on Dec. 12, 2003; U.S. patent application Ser. No. 10/740,722, entitled “A SYSTEM AND METHOD FOR CONFIGURING SEMICONDUCTOR FUNCTIONAL CIRCUITS”, filed on Dec. 18, 2003; U.S. patent application Ser. No. 10/740,779, entitled “A SYSTEM AND METHOD FOR REMOTELY CONFIGURING SEMICONDUCTOR FUNCTIONAL CIRCUITS”, filed on Dec. 18, 2003; U.S. patent application Ser. No. 10/876,340, entitled “SYSTEM AND METHOD FOR TESTING AND CONFIGURING SEMICONDUCTOR FUNCTIONAL CIRCUITS”, filed on Jun. 23, 2004; U.S. patent application Ser. No. 10/942,169, entitled “MICRO ELECTRO MECHAMCAL SWITCH SYSTEM AND METHOD FOR TESTING AND CONFIGURING SEMICONDUCTOR FUNCTIONAL CIRCUITS”, filed on Dec. 15, 2004; U.S. patent application Ser. No. 11/454,313, entitled “FUNCTIONAL COMPONENT COORDINATED RECONFIGURATION SYSTEM AND METHOD”, filed on Jun. 16, 2006; U.S. patent application Ser. No. 11/472,865, entitled “FUNCTIONAL COMPONENT COMPENSATION RECONFIGURATION SYSTEM AND METHOD”, filed on Jun. 21, 2006; and U.S. patent application Ser. No. 10/942,209, entitled “SEMICONDUCTOR DIE MICRO ELECTRO-MECHANICAL SWITCH MANAGEMENT SYSTEM AND METHOD”, filed on Sep. 15, 2004;
| Number | Name | Date | Kind |
|---|---|---|---|
| 3940740 | Coontz | Feb 1976 | A |
| 4208810 | Rohner et al. | Jun 1980 | A |
| 4412281 | Works | Oct 1983 | A |
| 4449730 | Oberleitner et al. | May 1984 | A |
| 4541075 | Dill et al. | Sep 1985 | A |
| 4773044 | Sfarti et al. | Sep 1988 | A |
| 4885703 | Deering | Dec 1989 | A |
| 4918626 | Watkins et al. | Apr 1990 | A |
| 4949280 | Littlefield | Aug 1990 | A |
| 4951220 | Ramacher et al. | Aug 1990 | A |
| 4985988 | Littlebury | Jan 1991 | A |
| 5036473 | Butts et al. | Jul 1991 | A |
| 5077660 | Haines et al. | Dec 1991 | A |
| 5081594 | Horsley | Jan 1992 | A |
| 5107455 | Haines et al. | Apr 1992 | A |
| 5125011 | Fung | Jun 1992 | A |
| 5276893 | Savaria | Jan 1994 | A |
| 5287438 | Kelleher | Feb 1994 | A |
| 5313287 | Barton | May 1994 | A |
| 5379405 | Ostrowski | Jan 1995 | A |
| 5392437 | Matter et al. | Feb 1995 | A |
| 5400777 | Olsson et al. | Mar 1995 | A |
| 5408606 | Eckart | Apr 1995 | A |
| 5432898 | Curb et al. | Jul 1995 | A |
| 5446836 | Lentz et al. | Aug 1995 | A |
| 5448496 | Butts et al. | Sep 1995 | A |
| 5452104 | Lee | Sep 1995 | A |
| 5452412 | Johnson, Jr. et al. | Sep 1995 | A |
| 5455536 | Kono et al. | Oct 1995 | A |
| 5483258 | Cornett et al. | Jan 1996 | A |
| 5498975 | Cliff et al. | Mar 1996 | A |
| 5513144 | O'Toole | Apr 1996 | A |
| 5513354 | Dwork et al. | Apr 1996 | A |
| 5517666 | Ohtani et al. | May 1996 | A |
| 5530457 | Helgeson | Jun 1996 | A |
| 5543935 | Harrington | Aug 1996 | A |
| 5570463 | Dao | Oct 1996 | A |
| 5574847 | Eckart et al. | Nov 1996 | A |
| 5578976 | Yao | Nov 1996 | A |
| 5594854 | Baldwin et al. | Jan 1997 | A |
| 5623692 | Priem et al. | Apr 1997 | A |
| 5630171 | Chejlava, Jr. et al. | May 1997 | A |
| 5633297 | Valko et al. | May 1997 | A |
| 5634107 | Yumoto et al. | May 1997 | A |
| 5638946 | Zavracky | Jun 1997 | A |
| 5664162 | Dye | Sep 1997 | A |
| 5671376 | Bucher et al. | Sep 1997 | A |
| 5694143 | Fielder et al. | Dec 1997 | A |
| 5705938 | Kean | Jan 1998 | A |
| 5766979 | Budnaitis | Jun 1998 | A |
| 5768178 | McLaury | Jun 1998 | A |
| 5778348 | Manduley et al. | Jul 1998 | A |
| 5805833 | Verdun | Sep 1998 | A |
| 5809230 | Pereira | Sep 1998 | A |
| 5815162 | Levine | Sep 1998 | A |
| 5821949 | Deering | Oct 1998 | A |
| 5854631 | Akeley et al. | Dec 1998 | A |
| 5854637 | Sturges | Dec 1998 | A |
| 5872902 | Kuchkuda et al. | Feb 1999 | A |
| 5884053 | Clouser et al. | Mar 1999 | A |
| 5896391 | Solheim et al. | Apr 1999 | A |
| 5909595 | Rosenthal et al. | Jun 1999 | A |
| 5913218 | Carney et al. | Jun 1999 | A |
| 5937173 | Olarig et al. | Aug 1999 | A |
| 5956252 | Lau et al. | Sep 1999 | A |
| 5956505 | Manduley | Sep 1999 | A |
| 5968175 | Morishita et al. | Oct 1999 | A |
| 5977987 | Duluk, Jr. | Nov 1999 | A |
| 5996996 | Brunelle | Dec 1999 | A |
| 5999990 | Sharrit et al. | Dec 1999 | A |
| 6003100 | Lee | Dec 1999 | A |
| 6028608 | Jenkins | Feb 2000 | A |
| 6034699 | Wong et al. | Mar 2000 | A |
| 6038348 | Carley | Mar 2000 | A |
| 6049870 | Greaves | Apr 2000 | A |
| 6065131 | Andrews et al. | May 2000 | A |
| 6067262 | Irrinki | May 2000 | A |
| 6067633 | Robbins et al. | May 2000 | A |
| 6069540 | Berenz et al. | May 2000 | A |
| 6072500 | Foran et al. | Jun 2000 | A |
| 6072686 | Yarbrough | Jun 2000 | A |
| 6085269 | Chan et al. | Jul 2000 | A |
| 6094116 | Tai et al. | Jul 2000 | A |
| 6098118 | Ellenby et al. | Aug 2000 | A |
| 6104407 | Aleksic et al. | Aug 2000 | A |
| 6104417 | Nielsen et al. | Aug 2000 | A |
| 6115049 | Winner et al. | Sep 2000 | A |
| 6118394 | Onaya | Sep 2000 | A |
| 6128000 | Jouppi et al. | Oct 2000 | A |
| 6129070 | Jingu et al. | Oct 2000 | A |
| 6137918 | Harrington et al. | Oct 2000 | A |
| 6160557 | Narayanaswami | Dec 2000 | A |
| 6160559 | Omtzigt | Dec 2000 | A |
| 6188394 | Morein et al. | Feb 2001 | B1 |
| 6201545 | Wong et al. | Mar 2001 | B1 |
| 6204859 | Jouppi et al. | Mar 2001 | B1 |
| 6219070 | Baker et al. | Apr 2001 | B1 |
| 6219628 | Kodosky | Apr 2001 | B1 |
| 6249288 | Campbell | Jun 2001 | B1 |
| 6249853 | Porterfield | Jun 2001 | B1 |
| 6255849 | Mohan | Jul 2001 | B1 |
| 6256758 | Abramovici et al. | Jul 2001 | B1 |
| 6259460 | Gossett et al. | Jul 2001 | B1 |
| 6307169 | Sun et al. | Oct 2001 | B1 |
| 6317804 | Levy et al. | Nov 2001 | B1 |
| 6323699 | Quiet | Nov 2001 | B1 |
| 6323874 | Gossett | Nov 2001 | B1 |
| 6348811 | Haycock et al. | Feb 2002 | B1 |
| 6359623 | Larson | Mar 2002 | B1 |
| 6362819 | Dalal et al. | Mar 2002 | B1 |
| 6363285 | Wey | Mar 2002 | B1 |
| 6363295 | Akram et al. | Mar 2002 | B1 |
| 6366289 | Johns | Apr 2002 | B1 |
| 6370603 | Silverman et al. | Apr 2002 | B1 |
| 6377898 | Steffan et al. | Apr 2002 | B1 |
| 6388590 | Ng | May 2002 | B1 |
| 6389585 | Masleid et al. | May 2002 | B1 |
| 6392431 | Jones | May 2002 | B1 |
| 6429288 | Esswein et al. | Aug 2002 | B1 |
| 6429747 | Franck et al. | Aug 2002 | B2 |
| 6429877 | Stroyan | Aug 2002 | B1 |
| 6433657 | Chen | Aug 2002 | B1 |
| 6437780 | Baltaretu et al. | Aug 2002 | B1 |
| 6452595 | Montrym et al. | Sep 2002 | B1 |
| 6469707 | Voorhies | Oct 2002 | B1 |
| 6480205 | Greene et al. | Nov 2002 | B1 |
| 6486425 | Seki | Nov 2002 | B2 |
| 6501564 | Schramm et al. | Dec 2002 | B1 |
| 6504542 | Voorhies et al. | Jan 2003 | B1 |
| 6504841 | Larson et al. | Jan 2003 | B1 |
| 6522329 | Ihara et al. | Feb 2003 | B1 |
| 6525737 | Duluk, Jr. et al. | Feb 2003 | B1 |
| 6529207 | Landau et al. | Mar 2003 | B1 |
| 6530045 | Cooper et al. | Mar 2003 | B1 |
| 6530049 | Abramovici et al. | Mar 2003 | B1 |
| 6535986 | Rosno et al. | Mar 2003 | B1 |
| 6550030 | Abramovici et al. | Apr 2003 | B1 |
| 6598194 | Madge et al. | Jul 2003 | B1 |
| 6606093 | Gossett et al. | Aug 2003 | B1 |
| 6611272 | Hussain et al. | Aug 2003 | B1 |
| 6614444 | Duluk, Jr. et al. | Sep 2003 | B1 |
| 6614448 | Garlick et al. | Sep 2003 | B1 |
| 6624823 | Deering | Sep 2003 | B2 |
| 6629181 | Alappat et al. | Sep 2003 | B1 |
| 6633197 | Sutardja | Oct 2003 | B1 |
| 6633297 | McCormack et al. | Oct 2003 | B2 |
| 6636212 | Zhu | Oct 2003 | B1 |
| 6646639 | Greene et al. | Nov 2003 | B1 |
| 6662133 | Engel et al. | Dec 2003 | B2 |
| 6671000 | Cloutier | Dec 2003 | B1 |
| 6693637 | Koneru et al. | Feb 2004 | B2 |
| 6693639 | Duluk, Jr. et al. | Feb 2004 | B2 |
| 6697063 | Zhu | Feb 2004 | B1 |
| 6700581 | Baldwin et al. | Mar 2004 | B2 |
| 6701466 | Fiedler | Mar 2004 | B1 |
| 6717474 | Chen et al. | Apr 2004 | B2 |
| 6717576 | Duluk, Jr. et al. | Apr 2004 | B1 |
| 6717578 | Deering | Apr 2004 | B1 |
| 6718496 | Fukuhisa et al. | Apr 2004 | B1 |
| 6734770 | Aigner et al. | May 2004 | B2 |
| 6734861 | Van Dyke et al. | May 2004 | B1 |
| 6738856 | Milley et al. | May 2004 | B1 |
| 6741247 | Fenney | May 2004 | B1 |
| 6741258 | Peck, Jr. et al. | May 2004 | B1 |
| 6742000 | Fantasia et al. | May 2004 | B1 |
| 6747057 | Ruzafa et al. | Jun 2004 | B2 |
| 6747483 | To et al. | Jun 2004 | B2 |
| 6765575 | Voorhies et al. | Jul 2004 | B1 |
| 6778177 | Furtner | Aug 2004 | B1 |
| 6782587 | Reilly | Aug 2004 | B2 |
| 6785841 | Akrout et al. | Aug 2004 | B2 |
| 6788101 | Rahman | Sep 2004 | B1 |
| 6788301 | Thrasher | Sep 2004 | B2 |
| 6794101 | Liu et al. | Sep 2004 | B2 |
| 6798410 | Redshaw et al. | Sep 2004 | B1 |
| 6803782 | Koob et al. | Oct 2004 | B2 |
| 6803916 | Ramani et al. | Oct 2004 | B2 |
| 6806788 | Marumoto | Oct 2004 | B1 |
| 6819332 | Baldwin | Nov 2004 | B2 |
| 6823283 | Steger et al. | Nov 2004 | B2 |
| 6825847 | Molnar et al. | Nov 2004 | B1 |
| 6833835 | van Vugt | Dec 2004 | B1 |
| 6849924 | Allison et al. | Feb 2005 | B2 |
| 6850133 | Ma | Feb 2005 | B2 |
| 6861865 | Carlson | Mar 2005 | B1 |
| 6862027 | Andrews et al. | Mar 2005 | B2 |
| 6879207 | Nickolls | Apr 2005 | B1 |
| 6906716 | Moreton et al. | Jun 2005 | B2 |
| 6938176 | Alben et al. | Aug 2005 | B1 |
| 6940514 | Wasserman et al. | Sep 2005 | B1 |
| 6947057 | Nelson et al. | Sep 2005 | B2 |
| 6956579 | Diard et al. | Oct 2005 | B1 |
| 6961057 | Van Dyke et al. | Nov 2005 | B1 |
| 6961065 | Sasaki | Nov 2005 | B2 |
| 6966020 | Abramovici et al. | Nov 2005 | B1 |
| 6973608 | Abramovici et al. | Dec 2005 | B1 |
| 6978317 | Anantha et al. | Dec 2005 | B2 |
| 6982718 | Kilgard et al. | Jan 2006 | B2 |
| 7002591 | Leather et al. | Feb 2006 | B1 |
| 7009607 | Lindholm et al. | Mar 2006 | B2 |
| 7009615 | Kilgard et al. | Mar 2006 | B1 |
| 7020598 | Jacobson | Mar 2006 | B1 |
| 7023437 | Voorhies et al. | Apr 2006 | B1 |
| 7043622 | Henry et al. | May 2006 | B2 |
| 7058738 | Stufflebeam, Jr. | Jun 2006 | B2 |
| 7061495 | Leather | Jun 2006 | B1 |
| 7064771 | Jouppi et al. | Jun 2006 | B1 |
| 7069369 | Chou et al. | Jun 2006 | B2 |
| 7069458 | Sardi et al. | Jun 2006 | B1 |
| 7069558 | Stone et al. | Jun 2006 | B1 |
| 7075542 | Leather | Jul 2006 | B1 |
| 7075797 | Leonard et al. | Jul 2006 | B1 |
| 7081902 | Crow et al. | Jul 2006 | B1 |
| 7085824 | Forth et al. | Aug 2006 | B2 |
| 7119809 | McCabe | Oct 2006 | B1 |
| 7124318 | Luick | Oct 2006 | B2 |
| 7126600 | Fowler et al. | Oct 2006 | B1 |
| 7136953 | Bisson et al. | Nov 2006 | B1 |
| 7154066 | Talwar et al. | Dec 2006 | B2 |
| 7158148 | Toji et al. | Jan 2007 | B2 |
| 7170315 | Bakker et al. | Jan 2007 | B2 |
| 7170515 | Zhu | Jan 2007 | B1 |
| 7174407 | Hou et al. | Feb 2007 | B2 |
| 7174411 | Ngai | Feb 2007 | B1 |
| 7184040 | Tzvetkov | Feb 2007 | B1 |
| 7185135 | Briggs et al. | Feb 2007 | B1 |
| 7185225 | Sutardja et al. | Feb 2007 | B2 |
| 7187383 | Kent | Mar 2007 | B2 |
| 7224364 | Yue et al. | May 2007 | B1 |
| 7246274 | Kizer et al. | Jul 2007 | B2 |
| 7260007 | Jain et al. | Aug 2007 | B2 |
| RE39898 | Nally et al. | Oct 2007 | E |
| 7293127 | Caruk | Nov 2007 | B2 |
| 7305571 | Cranford, Jr. et al. | Dec 2007 | B2 |
| 7307628 | Goodman et al. | Dec 2007 | B1 |
| 7307638 | Leather et al. | Dec 2007 | B2 |
| 7324458 | Schoenborn et al. | Jan 2008 | B2 |
| 7340541 | Castro et al. | Mar 2008 | B2 |
| 7362325 | Anderson | Apr 2008 | B2 |
| 7373547 | Sutardja et al. | May 2008 | B2 |
| 7382368 | Molnar et al. | Jun 2008 | B1 |
| 7398336 | Feng et al. | Jul 2008 | B2 |
| 7414636 | Kokojima et al. | Aug 2008 | B2 |
| 7415551 | Pescatore | Aug 2008 | B2 |
| 7424564 | Mehta et al. | Sep 2008 | B2 |
| 7437021 | Satoh | Oct 2008 | B2 |
| 7453466 | Hux et al. | Nov 2008 | B2 |
| 7480808 | Caruk et al. | Jan 2009 | B2 |
| 7483029 | Crow et al. | Jan 2009 | B2 |
| 7525986 | Lee et al. | Apr 2009 | B2 |
| 7548996 | Baker et al. | Jun 2009 | B2 |
| 7551174 | Iourcha et al. | Jun 2009 | B2 |
| 7594061 | Shen et al. | Sep 2009 | B2 |
| 7633506 | Leather et al. | Dec 2009 | B1 |
| 7634637 | Lindholm et al. | Dec 2009 | B1 |
| 7663633 | Diamond et al. | Feb 2010 | B1 |
| 7782325 | Gonzalez et al. | Aug 2010 | B2 |
| 7791617 | Crow et al. | Sep 2010 | B2 |
| 7793029 | Parson et al. | Sep 2010 | B1 |
| 7965902 | Zelinka et al. | Jun 2011 | B1 |
| 8063903 | Vignon et al. | Nov 2011 | B2 |
| 8132015 | Wyatt | Mar 2012 | B1 |
| 8144166 | Lyapunov et al. | Mar 2012 | B2 |
| 8237738 | Crow | Aug 2012 | B1 |
| 8412872 | Wagner et al. | Apr 2013 | B1 |
| 8417838 | Tamasi et al. | Apr 2013 | B2 |
| 8482567 | Moreton et al. | Jul 2013 | B1 |
| 8532098 | Reed et al. | Sep 2013 | B2 |
| 20010005209 | Lindholm et al. | Jun 2001 | A1 |
| 20020005729 | Leedy | Jan 2002 | A1 |
| 20020026623 | Morooka | Feb 2002 | A1 |
| 20020031025 | Shimano et al. | Mar 2002 | A1 |
| 20020050979 | Oberoi et al. | May 2002 | A1 |
| 20020059392 | Ellis, III | May 2002 | A1 |
| 20020087833 | Burns et al. | Jul 2002 | A1 |
| 20020091979 | Cooke et al. | Jul 2002 | A1 |
| 20020097241 | McCormack et al. | Jul 2002 | A1 |
| 20020120723 | Forth et al. | Aug 2002 | A1 |
| 20020130863 | Baldwin | Sep 2002 | A1 |
| 20020138750 | Gibbs et al. | Sep 2002 | A1 |
| 20020140655 | Liang et al. | Oct 2002 | A1 |
| 20020143653 | DiLena et al. | Oct 2002 | A1 |
| 20020158869 | Ohba et al. | Oct 2002 | A1 |
| 20020158885 | Brokenshire et al. | Oct 2002 | A1 |
| 20020196251 | Duluk, Jr. et al. | Dec 2002 | A1 |
| 20020199110 | Kean | Dec 2002 | A1 |
| 20030020173 | Huff et al. | Jan 2003 | A1 |
| 20030023771 | Erickson et al. | Jan 2003 | A1 |
| 20030046472 | Morrow | Mar 2003 | A1 |
| 20030051091 | Leung et al. | Mar 2003 | A1 |
| 20030058244 | Ramani et al. | Mar 2003 | A1 |
| 20030061409 | RuDusky | Mar 2003 | A1 |
| 20030067468 | Duluk, Jr. et al. | Apr 2003 | A1 |
| 20030076325 | Thrasher | Apr 2003 | A1 |
| 20030093506 | Oliver et al. | May 2003 | A1 |
| 20030101288 | Tague et al. | May 2003 | A1 |
| 20030115500 | Akrout et al. | Jun 2003 | A1 |
| 20030122815 | Deering | Jul 2003 | A1 |
| 20030160795 | Alcorn et al. | Aug 2003 | A1 |
| 20030163589 | Bunce et al. | Aug 2003 | A1 |
| 20030164830 | Kent | Sep 2003 | A1 |
| 20030179631 | Koob et al. | Sep 2003 | A1 |
| 20030194116 | Wong et al. | Oct 2003 | A1 |
| 20030201994 | Taylor et al. | Oct 2003 | A1 |
| 20040012082 | Dewey et al. | Jan 2004 | A1 |
| 20040012597 | Zatz et al. | Jan 2004 | A1 |
| 20040046764 | Lefebvre et al. | Mar 2004 | A1 |
| 20040064628 | Chiu | Apr 2004 | A1 |
| 20040085313 | Moreton et al. | May 2004 | A1 |
| 20040102187 | Moller et al. | May 2004 | A1 |
| 20040130552 | Duluk, Jr. et al. | Jul 2004 | A1 |
| 20040183148 | Blasko | Sep 2004 | A1 |
| 20040183801 | Deering | Sep 2004 | A1 |
| 20040188781 | Bar | Sep 2004 | A1 |
| 20040196285 | Rice et al. | Oct 2004 | A1 |
| 20040196290 | Satoh | Oct 2004 | A1 |
| 20040207642 | Crisu et al. | Oct 2004 | A1 |
| 20040225787 | Ma et al. | Nov 2004 | A1 |
| 20040227599 | Shen et al. | Nov 2004 | A1 |
| 20040246251 | Fenney et al. | Dec 2004 | A1 |
| 20050030314 | Dawson | Feb 2005 | A1 |
| 20050041031 | Diard | Feb 2005 | A1 |
| 20050041037 | Dawson | Feb 2005 | A1 |
| 20050044284 | Pescatore | Feb 2005 | A1 |
| 20050045722 | Park | Mar 2005 | A1 |
| 20050060601 | Gomm | Mar 2005 | A1 |
| 20050066148 | Luick | Mar 2005 | A1 |
| 20050088445 | Gonzalez et al. | Apr 2005 | A1 |
| 20050122338 | Hong et al. | Jun 2005 | A1 |
| 20050125629 | Kissell | Jun 2005 | A1 |
| 20050134588 | Aila et al. | Jun 2005 | A1 |
| 20050134603 | Iourcha et al. | Jun 2005 | A1 |
| 20050172135 | Wiersma | Aug 2005 | A1 |
| 20050173233 | Kaelberer | Aug 2005 | A1 |
| 20050174353 | Alcorn et al. | Aug 2005 | A1 |
| 20050179698 | Vijayakumar et al. | Aug 2005 | A1 |
| 20050182881 | Chou et al. | Aug 2005 | A1 |
| 20050210472 | Accapadi et al. | Sep 2005 | A1 |
| 20050237083 | Bakker et al. | Oct 2005 | A1 |
| 20050246460 | Stufflebeam | Nov 2005 | A1 |
| 20050259100 | Teruyama | Nov 2005 | A1 |
| 20050275663 | Kokojima et al. | Dec 2005 | A1 |
| 20050285863 | Diamond | Dec 2005 | A1 |
| 20060033745 | Koselj et al. | Feb 2006 | A1 |
| 20060044317 | Bourd et al. | Mar 2006 | A1 |
| 20060053188 | Mantor et al. | Mar 2006 | A1 |
| 20060053189 | Mantor | Mar 2006 | A1 |
| 20060055641 | Robertus et al. | Mar 2006 | A1 |
| 20060106911 | Chapple et al. | May 2006 | A1 |
| 20060123177 | Chan et al. | Jun 2006 | A1 |
| 20060132495 | Anderson | Jun 2006 | A1 |
| 20060170690 | Leather | Aug 2006 | A1 |
| 20060190663 | Lu | Aug 2006 | A1 |
| 20060203005 | Hunter | Sep 2006 | A1 |
| 20060221086 | Diard | Oct 2006 | A1 |
| 20060245001 | Lee et al. | Nov 2006 | A1 |
| 20060252285 | Shen | Nov 2006 | A1 |
| 20060267981 | Naoi | Nov 2006 | A1 |
| 20060267987 | Litchmanov | Nov 2006 | A1 |
| 20060282604 | Temkine et al. | Dec 2006 | A1 |
| 20070038794 | Purcell et al. | Feb 2007 | A1 |
| 20070050647 | Conroy et al. | Mar 2007 | A1 |
| 20070067535 | Liu | Mar 2007 | A1 |
| 20070088877 | Chen et al. | Apr 2007 | A1 |
| 20070115271 | Seo et al. | May 2007 | A1 |
| 20070115290 | Polzin et al. | May 2007 | A1 |
| 20070115291 | Chen et al. | May 2007 | A1 |
| 20070139440 | Crow et al. | Jun 2007 | A1 |
| 20070268298 | Alben et al. | Nov 2007 | A1 |
| 20070273689 | Tsao | Nov 2007 | A1 |
| 20070296725 | Steiner et al. | Dec 2007 | A1 |
| 20080024497 | Crow et al. | Jan 2008 | A1 |
| 20080024522 | Crow et al. | Jan 2008 | A1 |
| 20080100618 | Woo et al. | May 2008 | A1 |
| 20080198163 | Nakahashi et al. | Aug 2008 | A1 |
| 20080273218 | Kitora et al. | Nov 2008 | A1 |
| 20090044003 | Berthiaume et al. | Feb 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 101093578 | Dec 2007 | CN |
| 61020348 | Jan 1986 | JP |
| H04266768 | Sep 1992 | JP |
| 06180758 | Jun 1994 | JP |
| 07-141526 | Jun 1995 | JP |
| 0916840 | Jun 1997 | JP |
| 10134198 | May 1998 | JP |
| 11195132 | Jul 1999 | JP |
| 11328133 | Nov 1999 | JP |
| 2001-005989 | Jan 2001 | JP |
| 2002076120 | Mar 2002 | JP |
| 2005182547 | Jul 2005 | JP |
| 1235341 | Jul 2005 | TW |
| 093127712 | Jul 2005 | TW |
| 0013145 | Mar 2000 | WO |
| 02054224 | Jul 2002 | WO |
| 2005029329 | Mar 2005 | WO |
| Entry |
|---|
| Welch, D. “Building Self-Reconfiguring Distributed Systems Using Compensating Reconfiguration”, Proceedings Fourth International Journal Conference on Configurable Distributed Systems, May 4-6, 1998, pp. 18-25. |
| Eckert, et al; NVID-P000871RR.1.P1; Functional Component Coordinated Reconfiguration System and Method; U.S. Appl. No. 11/454,313; Filing date: Jun. 16, 2006. |
| Diamond, NVID-P001272; A Semiconductor Die Micro Electro-Mechanical Switch Management System; U.S. Appl. No. 10/942,209; Filing Date: Sep. 15, 2004. |
| Diamond, et al; NVID-P000871.4; A System and Method for Remotely Configuring Semiconductor Functional Circuits; U.S. Appl. No. 10/740,779; Filing date: Dec. 18, 2003. |
| Van Dyke, et al; NVID-P000871.1; An Integrated Circuit Configuration System and Method; U.S. Appl. No. 10/740,721; Filing Date: Dec. 18, 2003. |
| Diamond; NVID-P000871.6; Micro Electro Mechanical Switch System and Method for Testing and Configuring Semiconductor Functional Circuits; U.S. Appl. No. 10/942,169; Filing Date: Sep. 15, 2004. |
| Scotzniovsky, et al; NVID-P000871RR.2.P1; Functional Component Compensation Reconfiguration System and Method; U.S. Appl. No. 11/472,865; Filing Date: Jun. 21, 2006. |
| Diamond; NVID-P000871.5; A System and Method for Configuring Semiconductor Functional Circuits; U.S. Appl. No. 10/876,340; Filing date: Jun. 23, 2004. |
| Non-Final Office Action Dated Nov. 14, 2007; U.S. Appl. No. 10/740,721. |
| Non-Final Office Action Dated Jul. 24, 2008; U.S. Appl. No. 10/740,721. |
| Final Office Action Dated Apr. 30, 2009; U.S. Appl. No. 10/740,721. |
| Non-Final Office Action Dated Mar. 13, 2009; U.S. Appl. No. 11/454,313. |
| Non-Final Office Action Dated Dec. 3, 2008; Application No. 10/942,169. |
| Non-Final Office Action Dated Mar. 10, 2008; U.S. Appl. No. 11/474,161. |
| Final Office Action Dated Sep. 17, 2008; U.S. Appl. No. 11/474,161. |
| Non-Final Office Action Dated Feb. 20, 2009; U.S. Appl. No. 11/474,161. |
| Non-Final Office Action Dated Jul. 14, 2005; U.S. Appl. No. 10/740,779. |
| Non-Final Office Action Dated Jan. 10, 2006; U.S. Appl. No. 10/740,779. |
| Final Office Action Dated Aug. 7, 2006; U.S. Appl. No. 10/740,779. |
| Non-Final Office Action Dated Mar. 26, 2007; U.S. Appl. No. 10/740,779. |
| Final Office Action Dated Dec. 6, 2007; U.S. Appl. No. 10/740,779. |
| Notice of Allowance Dated Jun. 9, 2008; U.S. Appl. No. 10/740,779. |
| Non-Final Office Action Dated Sep. 26, 2008; U.S. Appl. No. 10/740,779. |
| Notice of Allowance Dated Jul. 20, 2009; U.S. Appl. No. 10/740,779. |
| Non-Final Office Action Dated Feb. 6, 2006; U.S. Appl. No. 10/942,209. |
| Final Office Action Dated Sep. 11, 2006; U.S. Appl. No. 10/942,209. |
| Non-Final Office Action Dated Mar. 29, 2007; U.S. Appl. No. 10/942,209. |
| Non-Final Office Action Dated Dec. 21, 2007; U.S. Appl. No. 10/942,209. |
| Non-Final Office Action Dated Jul. 14, 2008; U.S. Appl. No. 10/942,209. |
| Final Office Action Dated Mar. 17, 2009; U.S. Appl. No. 10/942,209. |
| Non-Final Office Action Dated Aug. 5, 2009; U.S. Appl. No. 10/942,209. |
| Non-Final Office Action Dated Feb. 9, 2007; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Aug. 10, 2007; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Nov. 21, 2007; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Mar. 18, 2008; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Aug. 8, 2008; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Nov. 28, 2008; U.S. Appl. No. 10/942,169. |
| Notice of Allowance Dated Apr. 24, 2009; U.S. Appl. No. 10/942,169. |
| Non-Final Office Action Dated Oct. 5, 2006; U.S. Appl. No. 10/876,340. |
| Final Office Action Dated May 23, 2007; U.S. Appl. No. 10/876,340. |
| Notice of Allowance Dated Dec. 4, 2007; U.S. Appl. No. 10/876,340. |
| Notice of Allowance Dated Apr. 29, 2008; U.S. Appl. No. 10/876,340. |
| Notice of Allowance Dated Sep. 4, 2008; U.S. Appl. No. 10/876,340. |
| Notice of Allowance Dated Jan. 12, 2009; U.S. Appl. No. 10/876,340. |
| Notice of Allowance Dated May 14, 2009; U.S. Appl. No. 10/876,340. |
| Non-Final Office Action Dated Jan. 11, 2006; U.S. Appl. No. 10/740,722. |
| Non-Final Office Action Dated Oct. 11, 2006; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated May 30, 2007; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Sep. 18, 2007; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Nov. 21, 2007; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Mar. 14, 2008; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Aug. 21, 2008; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Dec. 22, 2008; U.S. Appl. No. 10/740,722. |
| Notice of Allowance Dated Apr. 16, 2009; U.S. Appl. No. 10/740,722. |
| Non-Final Office Action Dated Dec. 23, 2008; U.S. Appl. No. 12/005,691. |
| Final Office Action Dated Jul. 8, 2009; U.S. Appl. No. 12/005,691. |
| Non-Final Office Action Dated Mar. 17, 2008; U.S. Appl. No. 11/474,027. |
| Final Office Action Dated Oct. 8, 2008; U.S. Appl. No. 11/474,027. |
| Non-Final Office Action Dated Mar. 19, 2009; U.S. Appl. No. 11/474,027. |
| U.S. Appl. No. 10/956,609; Acocella et al., filed Sep. 30, 2004. |
| Non Final Office Action; Mail Date Mar. 26, 2010; U.S. Appl. No. 11/454,313. |
| Non Final Office Action; Mail Date Sep. 14, 2009; U.S. Appl. No. 11/454,313. |
| Final Office Action; Mail Date Sep. 4, 2009; U.S. Appl. No. 11/472,865. |
| Final Office Action dated Jul. 12, 2010; U.S. Appl. No. 10/740,721. |
| Final Office Action Dated Feb. 28, 2011, U.S. Appl. No. 10/740,721. |
| International Search Report, PCT/US2004/030127, Mail Date Jun. 30, 2005. |
| PCT International Preliminary Report on Patentability, PCT/US2004/030127, International filing date Sep. 13, 2004, Applicant: Nvidia Corporation, date of Issuance of this Report: Mar. 16, 2006. |
| “Addressing the System-on-a-Chip Interconnect Woes Through Communication-Based Design” by Sgrol et al., DAC 2001, Jun. 18-22, 2001, copyright ACM. |
| “OSI Reference Model-The ISO Model of Architecture for Open Systems Interconnection,” by Zimmermann, IEEE Transactions on Communicaions, Apr. 1980. |
| “SuperPaint: An Early Frame Buffer Graphics System”, by Richard Shoup, IEEE Annals of the History of Computing, copyright 2001. |
| “Multimedia Processors” by Kuroda et al., Proceedings of the IEEE, Jun. 1998. |
| “Test Requirements for Embedded Core-based Systems and IEEE P1500” by Yervant Zorian, International Test Conference,copyright IEEE 1997. |
| PCI Express Card Electromechanical Specification Rev. 1.1, 2005, p. 87. |
| A parallel algorithm for polygon rasterization Juan Pineda Jun. 1988 ACM. |
| A VLSI architecture for updating raster-scan displays Satish Gupta, Robert F. Sproull, Ivan E. Sutherland Aug. 1981 ACM SIGGRAPH Computer Graphics, Proceedings of the 8th annual conference on Computer graphics and interactive techniques SIGGRAPH '81, vol. 15 Issue 3 Publisher: ACM Press. |
| Blythe, OpenGL Section 3.4.1, “Basic Line Segment Rasterization”, Mar. 29, 1997, pp. 1-3. |
| A hardware assisted design rule check architecture Larry Seiler Jan. 1982 Proceedings of the 19th conference on design automation DAC '82 Publisher: IEEE Press. |
| Foley, J. “Computer Graphics: Principles and Practice”, 1987, Addison-Wesley Publishing, 2nd Edition, p. 545-546. |
| Fuchs; “Fast Spheres Shadow, Textures, Transparencies, and Image Enhancements in Pixel-Planes”; ACM; 1985; Department of Computer Science, University of North Carolina at Chapel Hill, Chapel Hill, NC 27514. |
| Number | Date | Country | |
|---|---|---|---|
| 20050251358 A1 | Nov 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60503710 | Sep 2003 | US |
