Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ fbio(4S) — SunOS 3.0

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

mmap(2)

bwone(4S)

bwtwo(4S)

cgone(4S)

cgtwo(4S)

gpone(4S)

fb(4S)

win(4S)

FBIO(4S)  —  SPECIAL FILES

NAME

fbio − general properties of frame buffers

DESCRIPTION

All of the Sun frame buffers support the same general interface.  Each responds to a FBIOGTYPE ioctl(2) which returns information in a structure defined in <sun/fbio.h>:

structfbtype {
intfb_type;      /∗ as defined below ∗/
intfb_height;/∗ in pixels ∗/
intfb_width;/∗ in pixels ∗/
intfb_depth;/∗ bits per pixel ∗/
intfb_cmsize;/∗ size of color map (entries) ∗/
intfb_size;      /∗ total size in bytes ∗/
};
#define FBTYPE_SUN1BW         0
#define FBTYPE_SUN1COLOR1
#define FBTYPE_SUN2BW         2
#define FBTYPE_SUN2COLOR3
#define FBTYPE_SUN2GP4

Each device has a FBTYPE which is used by higher-level software to determine how to perform raster-op and other functions.  Each device is used by opening it, doing a FBIOGTYPE ioctl to see which frame buffer type is present, and thereby selecting the appropriate device-management routines. 

Full-fledged frame buffers (that is, those that run SunWindows), implement an FBIOGPIXRECT ioctl(2), which returns a pixrect. This call is made only from inside the kernel. The returned pixrect is used by win(4S) for cursor tracking and colormap loading.

SEE ALSO

mmap(2), bwone(4S), bwtwo(4S), cgone(4S), cgtwo(4S), gpone(4S), fb(4S), win(4S)

Sun Release 3.0β  —  Last change: 23 December 1985

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026