1fbio(7I)                        Ioctl Requests                        fbio(7I)
2
3
4

NAME

6       fbio - frame buffer control operations
7

DESCRIPTION

9       The  frame  buffers provided with this release support the same general
10       interface that is defined by <sys/fbio.h>. Each responds to  an  FBIOG‐
11       TYPE ioctl(2) request which returns information in a fbtype structure.
12
13
14       Each  device  has  an  FBTYPE which is used by higher-level software to
15       determine how to perform graphics functions. Each  device  is  used  by
16       opening  it,  doing an FBIOGTYPE ioctl() to see which frame buffer type
17       is present, and thereby  selecting  the  appropriate  device-management
18       routines.
19
20
21       FBIOGINFO returns information specific to the GS accelerator.
22
23
24       FBIOSVIDEO and FBIOGVIDEO are general-purpose ioctl() requests for con‐
25       trolling possible  video  features  of  frame  buffers.  These  ioctl()
26       requests  either  set  or  return the value of a flags integer. At this
27       point,  only  the  FBVIDEO_ON  option  is  available,   controlled   by
28       FBIOSVIDEO. FBIOGVIDEO returns the current video state.
29
30
31       The  FBIOSATTR  and  FBIOGATTR ioctl() requests allow access to special
32       features of newer frame buffers. They  use  the   fbsattr  and  fbgattr
33       structures.
34
35
36       Some  color  frame  buffers  support  the  FBIOPUTCMAP  and FBIOGETCMAP
37       ioctl() requests, which provide access to the colormap.  They  use  the
38       fbcmap structure.
39
40
41       Also,  some framebuffers with multiple colormaps will either encode the
42       colormap identifier in the high-order bits of the "index" field in  the
43       fbcmap  structure,  or  use  the  FBIOPUTCMAPI and FBIOGETCMAPI ioctl()
44       requests.
45
46
47       FBIOVERTICAL is used to wait for the start of the next vertical retrace
48       period.
49
50
51       FBIOVRTOFFSET  Returns  the offset to a read-only vertical retrace page
52       for those framebuffers that support it.  This vertical retrace page may
53       be  mapped into user space with mmap(2). The first word of the vertical
54       retrace page (type unsigned int) is a counter that is incremented every
55       time  there  is  a  vertical  retrace.   The  user process can use this
56       counter in a variety of ways.
57
58
59       FBIOMONINFO returns a mon_info  structure  which  contains  information
60       about the monitor attached to the framebuffer, if available.
61
62
63       FBIOSCURSOR,  FBIOGCURSOR, FBIOSCURPOS and FBIOGCURPOS are used to con‐
64       trol the hardware cursor for those framebuffers that have this feature.
65       FBIOGCURMAX  returns  the  maximum sized cursor supported by the frame‐
66       buffer.  Attempts to create a cursor larger than this will fail.
67
68
69       Finally FBIOSDEVINFO and FBIOGDEVINFO are used  to  transfer  variable-
70       length, device-specific information into and out of framebuffers.
71

SEE ALSO

73       ioctl(2), mmap(2), cgsix(7D)
74

BUGS

76       The  FBIOSATTR  and  FBIOGATTR  ioctl()  requests are only supported by
77       frame buffers which emulate older frame buffer types. If a frame buffer
78       emulates  another frame buffer, FBIOGTYPE returns the emulated type. To
79       get the real type, use FBIOGATTR.
80
81
82       The FBIOGCURPOS ioctl was incorrectly  defined  in  previous  operating
83       systems,  and  older  code running in binary compatibility mode may get
84       incorrect results.
85
86
87
88SunOS 5.11                        12 May 2003                         fbio(7I)
Impressum