Texture mapping performance by combining requests for image data

[0001] 1. Field of the Invention

[0002] This invention relates generally to the field of computer graphics and, more particularly, to texture buffer and controller architecture.

[0003] 2. Description of the Related Art

[0004] With each new generation of graphics system, there is more image data to process and less time in which to process it. This consistent increase in data and data rates places additional burden on the memory systems that form an integral part of the graphics system. Attempts to further improve graphics system performance are now running up against the limitations of these memory systems in general, and memory device limitations in particular.

[0005] One example of a memory sub-system defining the upper limit of overall system performance may be the texture buffer of a graphics system. Certain graphics applications such as 3D modeling, virtual reality viewers, and video games may call for the application of an image to a geometric primitive in lieu of a procedurally generated pattern, gradient or solid color. In these applications, geometric primitives carry additional mapping data (e.g., a UV, or UVQ map) which describes how the non-procedural data is to be applied to the primitive. To implement this type of function, a graphics system may employ a texture buffer to store two dimensional image data representative of texture patterns, environment maps, bump maps, and other types of non-procedural data.

[0006] During the rendering process, the mapping data associated with a primitive may be used to interpolate texture map addresses for each pixel in the primitive. The texture map addresses may then be used to retrieve the portion of non-procedural image data in the texture buffer to be applied to the primitive. In some cases (e.g., photo-realistic rendering) a fetch from the texture buffer may result in a neighborhood or tile of texture pixels or texels to be retrieved from the texture buffer and spatially filtered to produce a single texel. In these cases, four or more texels may be retrieved for each displayed pixel, placing a high level of demand on the texture buffer. Thus, poor performance of the texture buffer is capable of affecting a cascading degradation through the graphics system, stalling the render pipeline, and increasing the render or refresh times of displayed images.

[0007] In some cases, dynamic random access memory (DRAM) devices may be used to implement a texture buffer as they are generally less expensive and occupy less real estate than static random access memory (SRAM) alternatives. However, DRAM devices have inherent factors such as pre-charge times, activation times, refresh periods, and others which may complicate integration into high bandwidth applications (e.g., high performance graphics systems). Recent advances in DRAM technology, including the introduction of new families (e.g., SDRAM), have increased the throughput of DRAM memories, but have not overcome all of these performance hurdles. Despite performance issues, the use of DRAM devices in graphics systems is still desirable for economic reasons.

[0008] In most graphics systems, overall memory bandwidth is of greater importance than memory latency (i.e., priority is placed on producing a continuous stream of video data, rather than on the amount of time it takes to initiate the stream). Additionally, certain data such as texture map data are frequently accessed in a predictable and repetitious manner. It is possible to utilize these characteristics of graphics systems to manage the flow of information from the texture buffer, and hence allow for performance enhancement when the memory devices or memory system is defining the upper limit of system throughput. Therefore, for these reasons, a system and method for improving the performance of memory sub-systems, particularly those employed in the texturing process of graphics systems is desired.

[0009] The problems set forth above may at least in part be solved in some embodiments by a system or method for improving the performance of memory sub-systems, particularly those employed in the texturing process of graphics systems. In one embodiment, the system may include an interleaved memory of DRAM devices configured to receive, store, and recall tiles of image data. A request queue may be configured to receive and store pending requests for data from the memory. Control logic may be coupled to the request queue, and configured to examine series of subsequent requests for tiles in order to detect opportunities for merging requests. Merging opportunities may exist as a result of the regular and predictable manner in which texture data is accessed in a graphics system. In such cases, a short series of requested tiles may contain redundant image data. If the nature of the redundant data is consistent with predefined patterns, then the control logic may combine requests, and thereby potentially reduce the number of memory accesses. In combining requests, image data received in response to memory requests may be stored in temporary registers, and reused to build a requested tile that contains redundant image data. In one embodiment, selection logic may be employed to select the source of image data, and output a tile. The source of the image data may be the temporary registers, or the memory. To affect the combination, the control logic may generate an operation code indicative of the tile processing to be performed (i.e., fetch a requested tile from memory, or build the requested tile from stored redundant data). In some embodiments, a state machine may be coupled to the control logic, and may decode and respond to the operation code by generating a sequence of control signals which direct the memory, temporary registers and selection logic to perform the desired actions.

[0010] As noted above, a method for improving the performance of memory sub-systems, particularly those employed in the texturing process of graphics systems is also contemplated. In one embodiment, the method includes maintaining a list of pending requests for data from the memory. A fixed length sequence of the requests may be examined and a determination made as to whether an opportunity to merge requests is present. This determination may be made based on the relative location of the tiles of image data requested. In these cases, the memory requests may comprise the base addresses of the requested tiles, and an examination of the base addresses may indicate whether there is sufficient redundant data shared by requests to allow merging them. For example, two subsequent base addresses with a differential of 1, may indicate that the two requested tiles of image data contain redundancy. If the determination is made to combine requests, tiles of image data may be fetched from the memory, and stored in temporary storage structures. A series of tiles may then be generated and output, these tiles comprising image data selected from one or more of the tiles output by the memory, or stored in the temporary structures.

[0011] The foregoing, as well as other objects, features, and advantages of this invention may be more completely understood by reference to the following detailed description when read together with the accompanying drawings in which:

[0012] FIG. 1 is a perspective view of one embodiment of a computer system;

[0013] FIG. 2 is a simplified block diagram of one embodiment of a computer system;

[0014] FIG. 3 is a functional block diagram of one embodiment of a graphics system;

[0015] FIG. 4 is a functional block diagram of one embodiment of the media processor of FIG. 3;

[0016] FIG. 5A is a functional block diagram of one embodiment of the hardware accelerator of FIG. 3;

[0017] FIG. 5B is a functional block diagram of one embodiment of the video processor of FIG. 3;

[0018] FIG. 6 is a simplified block diagram of one embodiment of a texel request processor;

[0019] FIG. 7 is a diagrammatic illustration of one example of a series of memory requests which present a merging opportunity;

[0020] FIG. 8 is a flow diagram illustrating one embodiment of a method for processing texel requests; and

[0021] FIG. 9 is a flow diagram illustrating a second embodiment of a method for processing texel requests.

[0022] While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. Note, the headings are for organizational purposes only and are not meant to be used to limit or interpret the description or claims. Furthermore, note that the word may is used throughout this application in a permissive sense (i.e., having the potential to, being able to), not a mandatory sense (i.e., must). The term include, and derivations thereof, mean including, but not limited to. The term connected means directly or indirectly connected, and the term coupled means directly or indirectly connected.

[0023] Computer System

[0024] Referring now to FIG. 1, one embodiment of a computer system 80 that includes a graphics system that may be used to implement one embodiment of the invention is shown. The graphics system may be comprised in any of various systems, including a computer system, network PC, Internet appliance, a television, including high definition television (HDTV) systems and interactive television systems, personal digital assistants (PDAs), virtual reality systems, and other devices which display 2D and or 3D graphics, among others.

[0025] As shown, the computer system 80 comprises a system unit 82 and a video monitor or display device 84 coupled to the system unit 82. The display device 84 may be any of various types of display monitors or devices including cathode ray tube (CRT), liquid crystal display (LCD) or gas-plasma display. Various input devices may be connected to the computer system, including a keyboard 86 and/or a mouse 88, or other input device (e.g., a trackball, digitizer, tablet, six-degree of freedom input device, head tracker, eye tracker, data glove, or body sensors). Application software may be executed by the computer system 80 to display graphical objects on display device 84.

[0026] Referring now to FIG. 2, a simplified block diagram illustrating the computer system of FIG. 1 is shown. Elements of the computer system that are not necessary for an understanding of the present invention are not shown for convenience. As shown, the computer system 80 includes a central processing unit (CPU) 102 coupled to a high-speed memory bus or system bus 104 also referred to as the host bus 104. A system memory 106 may also be coupled to high-speed bus 104.

[0027] Host processor 102 may comprise one or more processors of varying types, e.g., microprocessors, multi-processors and CPUs. The system memory 106 may comprise any combination of different types of memory subsystems, including random access memories, (e.g., static random access memories or SRAMs, synchronous dynamic random access memories or SDRAMs, and Rambus dynamic random access memories or RDRAM, among others) and mass storage devices. The system bus or host bus 104 may comprise one or more communication or host computer buses (for communication between host processors, CPUs, and memory subsystems) as well as specialized subsystem buses.

[0028] In FIG. 2, a graphics system 112 is coupled to the high-speed memory bus 104. The 3-D graphics system 112 may be coupled to the bus 104 by, for example, a crossbar switch or other bus connectivity logic. It is assumed that various other peripheral devices, or other buses, may be connected to the high-speed memory bus 104. It is noted that the graphics system may be coupled to one or more of the buses in computer system 80 and/or may be coupled to various types of buses. In addition, the graphics system may be coupled to a communication port and thereby directly receive graphics data from an external source, e.g., the Internet or a network. As shown in the figure, one or more display devices 84 may be connected to the graphics system 112 comprised in the computer system 80.

[0029] Host CPU 102 may transfer information to and from the graphics system 112 according to a programmed input/output (I/O) protocol over host bus 104. Alternately, graphics system 112 may access the memory subsystem 106 according to a direct memory access (DMA) protocol or through intelligent bus mastering.

[0030] A graphics application program conforming to an application programming interface (API) such as OpenGL or Java 3D may execute on host CPU 102 and generate commands and data that define a geometric primitive (graphics data) such as a polygon for output on display device 84. As defined by the particular graphics interface used, these primitives may have separate color properties for the front and back surfaces. Host processor 102 may transfer this graphics data to memory subsystem 106. Thereafter, the host processor 102 may operate to transfer the graphics data to the graphics system 112 over the host bus 104. In another embodiment, the graphics system 112 may read in geometry data arrays over the host bus 104 using DMA access cycles. In yet another embodiment, the graphics system 112 may be coupled to the system memory 106 through a direct port, such as the Advanced Graphics Port (AGP) promulgated by Intel Corporation.

[0031] The graphics system may receive graphics data from any of various sources, including the host CPU 102 and/or the system memory 106, other memory, or from an external source such as a network, e.g., the Internet, or from a broadcast medium, e.g., television, or from other sources.

[0032] Note while graphics system 112 is depicted as part of computer system 80, graphics system 112 may also be configured as a stand-alone device (e.g., with its own built-in display). Graphics system 112 may also be configured as a single chip device or as part of a system-on-a-chip or a multi-chip module. Additionally, in some embodiments, certain elements of the illustrated graphics system 112 may be implemented in software.

[0033] Graphics System

[0034] Referring now to FIG. 3, a functional block diagram illustrating one embodiment of graphics system 112 is shown. Note that many other embodiments of graphics system 112 are possible and contemplated. Graphics system 112 may comprise one or more media processors 14, one or more hardware accelerators 18, one or more texture buffers 20, one or more frame buffers 22, and one or more video output processors 24. Graphics system 112 may also comprise one or more output devices such as digital-to-analog converters (DACs) 26, video encoders 28, flat-panel-display drivers (not shown), and/or video projectors (not shown). Media processor 14 and/or hardware accelerator 18 may be any suitable type of high performance processor (e.g., specialized graphics processors or calculation units, multimedia processors, digital signal processors (DSPs), or general purpose processors).

[0035] In some embodiments, one or more of these components may be removed. For example, the video output processor may be excluded from an embodiment that does not provide video output signals to drive a display device. In other embodiments, all or part of the functionality implemented in either or both of the media processor or the graphics accelerator may be implemented in software.

[0036] In some embodiments, media processor 14 and hardware accelerator 18 may be comprised within the same integrated circuit. In other embodiments, portions of media processor 14 and/or hardware accelerator 18 may be comprised within separate integrated circuits.

[0037] As shown, graphics system 112 may include an interface to a host bus such as host bus 104 in FIG. 2 to enable graphics system 112 to communicate with a host system such as computer system 80. More particularly, host bus 104 may allow a host processor to send commands to the graphics system 112. In one embodiment, host bus 104 may be a bi-directional bus.

[0038] Each functional block of graphics system 112 is described in more detail below.

[0039] Media Processor

[0040] FIG. 4 shows one embodiment of media processor 14. As shown, media processor 14 operates as the interface between graphics system 112 and computer system 80 by controlling the transfer of data between graphics system 112 and computer system 80. In some embodiments, media processor 14 may also be configured to perform transform, lighting, and/or other general-purpose processing on graphical data.

[0041] Transformation refers to manipulating an object and includes translating the object (i.e., moving the object to a different location), scaling the object (i.e., stretching or shrinking), and rotating the object (e.g., in three-dimensional space, or 3-space).

[0042] Lighting refers to calculating the illumination of the objects within the displayed image to determine what color and or brightness each individual object will have. Depending upon the shading algorithm being used (e.g., constant, Gourand, or Phong), lighting may be evaluated at a number of different locations. For example, if constant shading is used (i.e., each pixel of a polygon has the same lighting), then the lighting need only be calculated once per polygon. If Gourand shading is used, then the lighting is calculated once per vertex. Phong shading calculates the lighting on a per-pixel basis.

[0043] As illustrated, media processor 14 may be configured to receive graphical data via host interface 11. A graphics queue 148 may be included in media processor 14 to buffer a stream of data received via the accelerated port of host interface 11. The received graphics data may comprise one or more graphics primitives. As used herein, the term graphics primitive may include polygons, parametric surfaces, splines, NURBS (nonuniform rational B-splines), sub-divisions surfaces, fractals, volume primitives, voxels (i.e., three-dimensional pixels), and particle systems. In one embodiment, media processor 14 may also include a geometry data preprocessor 150 and one or more microprocessor units (MPUs) 152. MPUs 152 may be configured to perform vertex transform and lighting calculations and programmable functions and to send results to hardware accelerator 18. MPUs 152 may also have read/write access to texels (i.e. the smallest addressable unit of a texture map, which is used to wallpaper a three-dimensional object) and pixels in the hardware accelerator 18. Geometry data preprocessor 150 may be configured to decompress geometry, to convert and format vertex data, to dispatch vertices and instructions to the MPUs 152, and to send vertex and attribute tags or register data to hardware accelerator 18.

[0044] As shown, media processor 14 may have other possible interfaces, including an interface to a memory. For example, as shown, media processor 14 may include direct Rambus interface 156 to a direct Rambus DRAM (DRDRAM) 16. A memory such as DRDRAM 16 may be used for program and data storage for MPUs 152. DRDRAM 16 may also be used to store display lists and/or vertex texture maps.

[0045] Media processor 14 may also include interfaces to other functional components of graphics system 112. For example, media processor 14 may have an interface to another specialized processor such as hardware accelerator 18. In the illustrated embodiment, controller 160 includes an accelerated port path that allows media processor 14 to control hardware accelerator 18. Media processor 14 may also include a direct interface, such as bus interface unit (BIU) 154, which provides a direct port path to memory 16 and to hardware accelerator 18 and video output processor 24 via controller 160.

[0046] Hardware Accelerator

[0047] Referring now to FIG. 5A, one embodiment of the hardware accelerator 18 is shown. One or more hardware accelerators 18 may be configured to receive graphics instructions and data from media processor 14 and then to perform a number of functions on the received data according to the received instructions. For example, hardware accelerator 18 may be configured to perform rasterization, 2D or 3D texturing, pixel transfers, imaging, fragment processing, clipping, depth cueing, transparency processing, set-up, and/or screen space rendering of various graphics primitives occurring within the graphics data.

[0048] Clipping refers to the elimination of graphics primitives or portions of graphics primitives that lie outside of a 3D view volume in world space. The 3D view volume may represent that portion of world space that is visible to a virtual observer (or virtual camera) situated in world space. For example, the view volume may be a solid truncated pyramid generated by a 2D view window and a viewpoint located in world space. The solid truncated pyramid may be imagined as the union of all rays emanating from the viewpoint and passing through the view window. The viewpoint may represent the world space location of the virtual observer. In most cases, primitives or portions of primitives that lie outside the 3D view volume are not currently visible and may be eliminated from further processing. Primitives or portions of primitives that lie inside the 3D view volume are candidates for projection onto the 2D view window.

[0049] Set-up refers to mapping primitives to a three-dimensional viewport. This involves translating and transforming the objects from their original world-coordinate system to the established viewport's coordinates. This creates the correct perspective for three-dimensional objects displayed on the screen.

[0050] Screen-space rendering refers to the calculation performed to generate the data used to form each pixel that will be displayed. For example, hardware accelerator 18 may calculate samples. Samples are points have color information but no real area. Samples allow hardware accelerator 18 to super-sample, or calculate more than one sample per pixel. Super-sampling may result in a higher quality image.

[0051] Hardware accelerator 18 may also include several interfaces. For example, in the illustrated embodiment, hardware accelerator 18 has four interfaces. Hardware accelerator 18 has an interface 161 (referred to as the North Interface) to communicate with media processor 14. Hardware accelerator 18 may also be configured to receive commands from media processor 14 through this interface. Additionally, hardware accelerator 18 may include an interface 176 to bus 32. Bus 32 may connect hardware accelerator 18 to boot PROM (programmable read-only memory) 30 and/or video output processor 24. Boot PROM 30 may be configured to store system initialization data and/or control code for frame buffer 22. Hardware accelerator 18 may communicate with texture buffer 20 using an eight-way interleaved texel bus that allows hardware accelerator 18 to read from and write to texture buffer 20. Hardware accelerator 18 may also interface to a frame buffer 22. For example, hardware accelerator 18 may be configured to read from and/or write to frame buffer 22 using a four-way interleaved pixel bus.

[0052] The vertex processor 162 may be configured to use the vertex tags received from the media processor 14 to perform ordered assembly of the vertex data from the MPUs 152. Vertices may be saved in and/or retrieved from a mesh buffer 164.

[0053] The render pipeline 166 may be configured to receive vertices and convert them to fragments. The render pipeline 166 may be configured to rasterize 2D window system primitives (e.g., dots, fonts, Bresenham lines, polygons, rectangles, fast fills, and BLITs (Bit Block Transfers, which move a rectangular block of bits from main memory into display memory, which may speed the display of moving objects on screen)) and 3D primitives (e.g., smooth and large dots, smooth and wide DDA (Digital Differential Analyzer) lines, triangles, polygons, and fast clear) into pixel fragments. The render pipeline 166 may be configured to handle full-screen size primitives, to calculate plane and edge slopes, and to interpolate data down to pixel tile resolution using interpolants or components such as r, g, b (i.e., red, green, and blue vertex color); r2, g2, b2 (i.e., red, green, and blue specular color from lit textures); a (alpha); and z, s, t, r, and w (texture components).

[0054] In embodiments using supersampling, the sample generator and evaluator 174 may be configured to generate samples from the fragments output by the render pipeline 166 and to determine which samples are inside the rasterization edge. Sample positions may be defined in loadable tables to enable stochastic sampling patterns.

[0055] Hardware accelerator 18 may be configured to write textured fragments from 3D primitives to frame buffer 22. The render pipeline 166 may send pixel tiles defining r, s, t and w to the texture address unit 168. The texture address unit 168 may determine the set of neighboring texels that are addressed by the fragment(s), as well as the interpolation coefficients for the texture filter, and request texels from the texture buffer 20 (as described in greater detail below). The texture buffer 20 may be interleaved to obtain as many neighboring texels as possible in each clock. The texture filter 170 may perform bilinear, trilinear or quadlinear interpolation. The texture environment 180 may apply texels to samples produced by the sample generator and evaluator 174. The texture environment 180 may also be used to perform geometric transformations on images (e.g., bilinear scale, rotate, flip) as well as to perform other image filtering operations on texture buffer image data (e.g., bicubic scale and convolutions).

[0056] Fragment processor 184 may be used to perform standard fragment processing operations such as the OpenGL fragment processing operations. For example, the fragment processor 184 may be configured to perform the following operations: fog, area pattern, scissor, alpha/color test, ownership test (WID), stencil test, depth test, alpha blends or logic ops (ROP), plane masking, buffer selection, pick hit/occlusion detection, and/or auxiliary clipping in order to accelerate overlapping windows.

[0057] Texture Buffer

[0058] Texture buffer 20 may include several SDRAMs. Texture buffer 20 may be configured to store texture maps, image processing buffers, and accumulation buffers for hardware accelerator 18. Texture buffer 20 may have many different capacities (e.g., depending on the type of SDRAM included in texture buffer 20). In some embodiments, each pair of SDRAMs may be independently row and column addressable.

[0059] Frame Buffer

[0060] Graphics system 112 may also include a frame buffer 22. In one embodiment, frame buffer 22 may include multiple 3DRAM64s. Frame buffer 22 may be configured as a display pixel buffer, an offscreen pixel buffer, and/or a supersample buffer. Furthermore, in one embodiment, certain portions of frame buffer 22 may be used as a display pixel buffer, while other portions may be used as an offscreen pixel buffer and supersample buffer.

[0061] Video Output Processor

[0062] In some embodiments, a video output processor 24 may buffer and process pixels output from frame buffer 22 as suggested by FIG. 5B. For example, video output processor 24 may be configured to read bursts of pixels from frame buffer 22. Video output processor 24 may also be configured to perform double buffer selection (dbsel) if the frame buffer 22 is double-buffered, overlay transparency, plane group extraction, gamma correction, pseudocolor or color lookup or bypass, and/or cursor generation. In one embodiment, frame buffer 22 may include multiple 3DRAM64 devices that include the transparency overlay function and all or some of the lookup tables. Video output processor 24 may also be configured to support two video output streams to two displays using the two independent video raster timing generators. For example, one raster (e.g., 196A) may drive a 12801024 CRT while the other (e.g., 196B) may drive a NTSC or PAL device with encoded television video.

[0063] In one embodiment, the video output processor 24 may directly output digital pixel data in lieu of analog video signals. This may be useful when a display device is based on a digital technology (e.g., an LCD-type display or a digital micro-mirror display).

[0064] DAC and Encoder

[0065] In some embodiments, the video output processor 24 may be configured to output a stream of digital video data to a DAC (digital to analog converter) 26. The DAC 26 may, in turn be configured to provide a high resolution RGB analog video output at dot rates of 240 MHz. This analog video output may be used to drive a display device such as a cathode ray tube (CRT) monitor. In some embodiments, the video output processor 24 may also output a stream of digital video data to one or more encoders 28. Each encoder 28 may be configured to supply an encoded video signal to a display (e.g., encoded NTSC or PAL video).

[0066] Processing Texel Requests

[0067] Turning now to FIG. 6, one embodiment of a texel request processor is shown. In some embodiments, the functional blocks shown in FIG. 6 may be distributed between the texture address 168 (shown in FIG. 5A), and the texture buffer 20. In other embodiments, the entire apparatus may be located within the texture buffer 20. The physical location and distribution of the functional blocks is unimportant to the following description of the texel request processing, and potentially contains a high degree of variability, limited only by the design objective of minimizing the lengths of interconnects.

[0068] Requests for texels may be received and pushed onto a request queue 200 which may operate as a first-in-first-out memory (FIFO). The request queue may be small in terms of capacity, and may differ from a conventional FIFO in that parallel access to the bottom three elements (i.e., the three least recently added entries to the queue) may be provided for. For the purposes of this discussion, these three entries will be herein referred to as R₁, R₀, and R₁, where R₀ represents the next request in the queue to process, R₁ represents the request to be processed after R₀, and R₁ represents the last request that was processed (i.e., the request which preceded R₀).

[0069] In some embodiments, R₀, R₁ and R₁ may comprise the base addresses of arrays of spatially contiguous texels. In these embodiments, the base addresses of the three arrays or tiles of texels may be examined by the control logic 202 in order to determine if there are any shared elements or texels. If subsequent tiles are determined to share common elements, then it may be possible to reduce the number of memory operations employed in fetching the tiles.

[0070] The control logic 202 may therefore test the base address differential between the three requests, and signal potentially shared elements. For example, if the tiles of texels fetched from the texture buffer 20 are two texels wide and two texels high and two subsequent requests (i.e., R₀ and R₁, or R₀ and R₁) have a base address differential of 1, then the requested tiles may share a common column. As another example, assuming the same tile size of two by two texels, a base address differential equal to the width of the texture map image, may indicate that two requested tiles share a common row.

[0071] In response to testing the base address differential, the control logic 202 may output the base address of the next tile of texels to fetch, to the address generator 206. Additionally, the control logic 202 may provide an operation code to the state machine 204. This operation code may relay information to the state machine concerning the operations to perform in fetching the requested tile of texels.

[0072] The address generator 206 may receive the base address of a tile of texels from the control logic 202. The address generator 206 may utilized the received base address along with information regarding the texture map image size, tile size and the current level of detail (LOD) to generate the addresses of each element in the requested tile. The address generator 206 may also receive control signals from the state machine 204 indicating that a new fetch is to be performed (i.e., the requested information has not been fetched by the previous request), and forcing the generated addresses to be driven onto the bus of the memory array 208.

[0073] The memory array 208 may be comprised of one or more banks of DRAM memory. In some embodiments, SDRAM (synchronous dynamic random access memory) devices may be employed. The memory array 208 may receive the addresses of each texel comprising the requested tile from the address generator 206, and control signals from the state machine 204. In response to the address information and control signals, the memory array 208 may output a complete tile of texels.

[0074] The read buffer 210 may receive a tile of texel data from the memory array 208 and control signals from the state machine 204. In response to the control signals, the read buffer 210 may store the tile of texel data in a set of temporary registers. Also in response to the control signals, the read buffer 210 may output a tile of texel data. The data comprising the tile conveyed to the output of the read buffer 210 may be the texel data received from the memory array 208, a combination of data received from the memory array 208 and data stored in the temporary registers, or data wholly residing in the temporary registers. The state machine 204 controls the sources of the output data, and how the output tile is constructed (described below) in accordance with the operation code received from the control logic.

[0075] In one embodiment of the read buffer 210, the width of the temporary registers, measured in storage cells may be equal to the number of bits in a tile of texel data, and the depth may be sufficient for storing up to two full tiles of texel data. The storage capacity in the temporary registers may vary with each embodiment with a practical lower limit of one tile plus the size of the potential intersecting area between two subsequent tiles. In the previous example, a tile was assumed to be two texels wide and two texels high, therefore, the practical lower limit for the temporary register capacity may be six texels.

[0076] In one embodiment, the state machine 204 may receive an operation code from the control logic 202. This operation code may contain information which indicates the sequence of events to perform in order to fulfill the current and pending requests for texel data. The state machine 204 may step through the indicated sequence of events, generating the control signals which fetch, move and store data within the texel request processor.

[0077] Turning now to FIG. 7, one example of three subsequent requests for tiles of texel data is illustrated. In FIG. 7a, an area of the texture buffer 20 memory containing the texture map image 286 is shown. The relationship between the three subsequent tiles to be fetched is illustrated. As seen in the figure, the first tile (280) and the second tile (282) overlap, and hence share a common column of texels. Similarly, the second (282) and third (284) tiles overlap and share a common column of texels. This relationship between the requested tiles may be detected by the control logic 202 upon examination of the associated base addresses (i.e., determining that the base address differential is 1).

[0078] In FIG. 7b, a sequence of events is illustrated which may satisfy the three subsequent requests (R₁, R₀ and R₁) by performing only two texel buffer 20 fetches, thereby potentially reducing the impact of the texel buffer 20 performance on the overall system throughput. The first requested tile may be fetched from the texture buffer 20 and placed in a temporary register 288(a). The contents of the temporary register may then be output from the texel request processor. In response to determining that both the first and third tiles share a common column of texels with the second tile, the fetch of the second tile may be skipped. The third tile may be fetched from the texture buffer 20 and placed in a second temporary register 288(b). In order to satisfy the second request (R₀), texels (b) and (f) may be read from the first temporary register 288(a) and texels (c) and (g) may be read from the second temporary register 288(b), the four texels may be used to construct a tile which may then be output. Finally, the contents of the second temporary register may be output in order to satisfy the third request (R₁).

[0079] Turning now to FIG. 8, a flow diagram illustrates one embodiment of a method for processing texel requests. The process may remain in an idle state, or an idle loop if there are no pending requests for texels (step 250). If there are pending requests, the current request (R₀) is first tested against the next future request (R₁) to determine whether there are any common elements (i.e., the tiles intersect) (step 252). If there is no intersection found between the two tiles, or if there is only one pending request, then the current request may be removed from the queue and issued to the memory array 208 (step 254). The memory array 208 may respond to the request by returning a tile of texel data, which may be first stored in the read buffer 210, and then output (step 256). If, however, an intersection between R₀ and R₁ is detected, then R₀ is similarly tested against the preceding request (R₁) (step 258). If R₀ and R₁ are found to have no intersection, then there may be no opportunity for merging requests, and execution may branch to step 254. If, however, an intersection is detected between R₀ and R_1, then an opportunity for combining requests may be indicated. Therefore, R₀ and R₁ may be removed from the queue, combined, and issued to the memory array 208 (steps 260, 262). The tile requested as part of R₀ may then be built in part with texels stored in the read buffer 210 (i.e., the texels common to R₀ and R₁), and in part with texels received from the memory array (i.e., the texels common to R₀ and R₁), and then output (step 264). Finally, the tile associated with R₁ may be output (step 266) with no further texel buffer 20 fetches, as this tile was received as part of the combined request in step 262.

[0080] Turning now to FIG. 9, a flow diagram illustrates a second embodiment of a method for processing texel requests. The embodiment illustrated assumes that a continuous stream of texel requests is received by the texel request processor. In other embodiments, a continuous stream of requests may not be achievable, and consequently, wait states or wait loops may be employed.

[0081] The process may be initialized by issuing the first request (R₁) to the memory array 208. The corresponding tile (T₁) may be received, stored in a temporary register, and then conveyed to the output (steps 302, 304). A test may then be performed by calculating the two base address differentials between three subsequent requests (R₁, R₀, and R₁) and arithmetically comparing the results to 1 (step 306). If the two base address differentials are equal to 1, it may be determined that the tiles corresponding to R₁ and R₀ share a common column of texels, and the tiles corresponding to R₀ and R₁ share a common column of texels. In this case, R₁ is issued to the memory, and the corresponding tile (T₁) is received and stored in a temporary register (steps 308, 310). The tile corresponding to R₀ (T₀) is then built from the texels shared with T₁ and T₁, and conveyed to the output (step 312). Finally, T₁ is read from the associated temporary register and conveyed to the output (step 324).

[0082] Referring back to step 306, if the two address differentials are not equal to 1, processing branches to step 314 where the two address differentials may then be tested for equality to the width of a texture map image row. If both address differentials are equal to the width of a row, then it may be determined that the tiles corresponding to R₁ and R₀ share a common row of texels, and that the tiles corresponding to R₀ and R₁ share a common row of texels. In this case, processing may branch to step 308 and proceed as described above. If, however, the address differentials indicate no common rows of texels, then there may be no opportunity to combine texel requests. R₀ may then be issued to the memory array 208, and the corresponding tile (T₀) received (step 316). T₀ may then be conveyed to the output (step 318). Before the process is repeated by branching back to step 306, the request queue may be updated (step 320). As part of updating the request queue, R₁ may be removed, and R₀ and R₁ shifted in order that R₀ replaces R₁, and R₁ replaces R₀. The next pending request may then replace R₁.

[0083] Although the embodiments above have been described in considerable detail, other versions are possible. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. Note the headings used herein are for organizational purposes only and are not meant to limit the description provided herein or the claims attached hereto.