Abstract: This disclosure describes, in part, systems for enabling physical retail stores and other facilities to implement automated-checkout techniques for the purchase of items that are priced per unit weight. For example, the described systems may enable a facility to implement technology where users are able to remove items from inventory locations, where the inventory locations include weight sensors detecting the weights of the items that were removed. The system then determines the prices based on the weights and charges the users for the prices of the items without performing manual checkout of the items. The price of an item is determined based on the weight of the item and the price per unit weight of the item. The systems described herein thus enable customized retail facilities, as opposed to a retail facility that allows automated-checkout only for prepackaged-type or otherwise non-customizable merchandise.

Abstract: This disclosure describes, in part, systems for enabling physical retail stores and other facilities to implement automated-checkout techniques for the purchase of items that are priced per unit weight. For example, the described systems may enable a facility to implement technology where users are able to remove items from inventory locations, place the items on weight sensors, and then be charged for the prices of the items without performing manual checkout of the items. The price of an item is determined based at least in part on the identifier of the item and the price per unit weight of the item. The systems described herein thus enable customized retail facilities, as opposed to a retail facility that allows automated-checkout only for prepackaged-type or otherwise non-customizable merchandise.

Abstract: A gsprite engine circuit reads a display list identifying gsprite image layers to be composited for display, retrieves gsprite image data from an external memory, and transforms the gsprite data to display device coordinates. The gsprite image layers represent independently rendered graphical objects in a graphics scene. The gsprite engine can simulate the motion of the graphical objects in a sequence of display images by performing affine transformations on the gsprite image layers. The interface to the gsprite engine circuit includes the display list and gsprite header blocks. The display list enumerates the gsprites to be composited as a display image. The header blocks describe a gsprite transform, which can be an affine transform, used to transform gsprites to display device coordinates. The header blocks also provide an array of references to image blocks or "chunks" comprising the gsprite.

Abstract: A graphics rendering chip serially renders a stream of geometric primitives to image regions called chunks. A set-up processor in the chip parses rendering commands and the stream of geometric primitives and computes edge equation parameters. A scan-convert processor receives the edge equation parameters from the set-up processor and scan converts the geometric primitives to produce pixel records and fragment records. An internal, double-buffered pixel buffer stores pixel records for fully covered pixel addresses and also stores references to fragment lists stored in a fragment buffer. A pixel engine performs hidden surface removal and controls storage of pixel and fragment records to the pixel and fragment buffers, respectively. An anti-aliasing engine resolves pixel data for one pixel buffer while the pixel engine fills the other pixel buffer with pixel data for the next chunk.

Abstract: A system for accessing texture data in a graphics rendering system allows texture data to be stored in memories with high latency or in a compressed format. The system utilizes a texture cache to temporarily store blocks of texture data retrieved from an external memory during rendering operations. In one implementation, geometric primitives are stored in a queue long enough to absorb the latency of fetching and possibly decompressing a texture block. The geometric primitives are converted into texture block references, and these references are used to fetch texture blocks from memory. A rasterizer rasterizes each geometric primitives as the necessary texture data becomes available in the texture cache. In another implementation, geometric primitives are converted into pixels, including a pixel address, color data, and a texture request. These pixels are stored in a queue long enough to absorb the latency of a texture block fetch.