base: Redesign internal frame buffer handling

Currently, frame buffer handling in gem5 is quite ad hoc. In practice,
we pass around naked pointers to raw pixel data and expect consumers
to convert frame buffers using the (broken) VideoConverter.

This changeset completely redesigns the way we handle frame buffers
internally. In summary, it fixes several color conversion bugs, adds
support for more color formats (e.g., big endian), and makes the code
base easier to follow.

In the new world, gem5 always represents pixel data using the Pixel
struct when pixels need to be passed between different classes (e.g.,
a display controller and the VNC server). Producers of entire frames
(e.g., display controllers) should use the FrameBuffer class to
represent a frame.

Frame producers are expected to create one instance of the FrameBuffer
class in their constructors and register it with its consumers
once. Consumers are expected to check the dimensions of the frame
buffer when they consume it.

Conversion between the external representation and the internal
representation is supported for all common "true color" RGB formats of
up to 32-bit color depth. The external pixel representation is
expected to be between 1 and 4 bytes in either big endian or little
endian. Color channels are assumed to be contiguous ranges of bits
within each pixel word. The external pixel value is scaled to an 8-bit
internal representation using a floating multiplication to map it to
the entire 8-bit range.

1 files changed, 0 insertions, 2 deletions

diff --git a/src/sim/byteswap.hh b/src/sim/byteswap.hh
index b46c1e552..7e5d6809e 100644
--- a/src/sim/byteswap.hh
+++ b/src/sim/byteswap.hh
@@ -58,8 +58,6 @@
 #include <libkern/OSByteOrder.h>
 #endif
 
-enum ByteOrder {BigEndianByteOrder, LittleEndianByteOrder};
-
 //These functions actually perform the swapping for parameters
 //of various bit lengths
 inline uint64_t