fbio(4i) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

fbio(4i)

fbio(4I)          Ioctls for a class of drivers or subsystems         fbio(4I)

NAME
       fbio - frame buffer control operations

DESCRIPTION
       The  frame  buffers provided with this release support the same general
       interface that is defined by <sys/fbio.h>. Each responds to  an  FBIOG‐
       TYPE  ioctl(2) request which returns information in a fbtype structure.


       Each device has an FBTYPE which is used by higher-level software to de‐
       termine how to perform graphics functions. Each device is used by open‐
       ing  it,  doing an FBIOGTYPE  ioctl() to see which frame buffer type is
       present, and thereby selecting the appropriate  device-management  rou‐
       tines.


       FBIOGINFO returns information specific to the GS accelerator.


       FBIOSVIDEO and FBIOGVIDEO are general-purpose ioctl() requests for con‐
       trolling  possible  video  features of frame buffers. These ioctl() re‐
       quests either set or return the value  of  a  flags  integer.  At  this
       point,   only   the  FBVIDEO_ON  option  is  available,  controlled  by
       FBIOSVIDEO. FBIOGVIDEO returns the current video state.


       The FBIOSATTR and FBIOGATTR  ioctl() requests allow access  to  special
       features  of  newer  frame  buffers.  They  use the fbsattr and fbgattr
       structures.


       Some color  frame  buffers  support  the  FBIOPUTCMAP  and  FBIOGETCMAP
       ioctl()  requests,  which  provide access to the colormap. They use the
       fbcmap structure.


       Also, some framebuffers with multiple colormaps will either encode  the
       colormap  identifier  in  the high-order bits of the index field in the
       fbcmap structure, or use the FBIOPUTCMAPI and FBIOGETCMAPI  ioctl() re‐
       quests.


       FBIOVERTICAL is used to wait for the start of the next vertical retrace
       period.


       FBIOVRTOFFSET Returns the offset to a read-only vertical  retrace  page
       for  those framebuffers that support it. This vertical retrace page may
       be mapped into user space with mmap(2). The first word of the  vertical
       retrace page (type unsigned int) is a counter that is incremented every
       time there is a vertical retrace. The user process can use this counter
       in a variety of ways.


       FBIOMONINFO  returns  a  mon_info  structure which contains information
       about the monitor attached to the framebuffer, if available.


       FBIOSCURSOR, FBIOGCURSOR, FBIOSCURPOS and FBIOGCURPOS are used to  con‐
       trol the hardware cursor for those framebuffers that have this feature.
       FBIOGCURMAX  returns  the  maximum sized cursor supported by the frame‐
       buffer. Attempts to create a cursor larger than this will fail.


       Finally FBIOSDEVINFO and FBIOGDEVINFO are used  to  transfer  variable-
       length, device-specific information into and out of framebuffers.

SEE ALSO
       ioctl(2), mmap(2)

BUGS
       The  FBIOSATTR  and  FBIOGATTR   ioctl() requests are only supported by
       frame buffers which emulate older frame buffer types. If a frame buffer
       emulates another frame buffer, FBIOGTYPE returns the emulated type.  To
       get the real type, use FBIOGATTR.


       The  FBIOGCURPOS  ioctl  was  incorrectly defined in previous operating
       systems, and older code running in binary compatibility  mode  may  get
       incorrect results.

Oracle Solaris 11.4               28 Oct 2009                         fbio(4I)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3