Commit Graph

11 Commits

Author SHA1 Message Date
perry
015e898c02 RCSID Police. 1998-01-05 07:02:46 +00:00
jonathan
1f44934407 * Change Sprite MACH_xxx prefix to MIPS_xxx.
* Use standard mips terminology (xxx_KSEG0, xxx_KSEG1) instead of the
  (more meaningful) Sprite names (xxx_CACHED, xxx_UNCACHED).
1997-06-22 07:42:25 +00:00
jonathan
22d3d9819d Correct sense of FBIO[GS]VIDEO ioctl as noted in PR #3515. 1997-04-19 08:21:59 +00:00
jonathan
0c048bf278 poll(2) changes for rcons, pmax framebuffer hardware-independent layer. 1996-10-13 12:47:55 +00:00
christos
d286889901 backout previous kprintf change 1996-10-13 03:39:27 +00:00
mhitch
784dc6bd1b poll(2) changes for framebuffer. 1996-10-12 16:00:21 +00:00
christos
19d8368f2f printf -> kprintf, sprintf -> ksprintf 1996-10-11 00:44:42 +00:00
jonathan
9bdcc60e97 more cleanups for -Wall:
Fix generic framebuffer (X-server interface)  cdevsw entry points to match
    declarations.
1996-05-19 01:01:10 +00:00
jonathan
764d54390c SAdd support for Sun-style framebuffer ioctl()s, as used by other NetBSD
[programs, notably /usr/sbin/screenblank.
1996-01-16 02:43:01 +00:00
jonathan
6d9de6f768 Fix qvss/pm compatible ioctl to set colormap entry. 1995-09-18 02:57:31 +00:00
jonathan
1d976e39b9 Change pmax framebuffer drivers to use Ted Lemon's port of the
NetBSD/sparc rcons glass-tty console pseudo-device driver, via
the "fb" generic-framebuffer pseudo-device driver.

Individual framebuffer device drivers are now autoconfig glue,
and initialization code for a set of vdac/ramdac-level methods,
called "fbdriver", that's used by all the pmax device drivers.
All the handlers for user-level requests (open/ioctl/read/write/close)
are moved into the fb pseudo-device driver, which uses the
the "fbdriver" methods to work on any given pmax hardware driver.
Framebuffers  supported are: sfb cfb mfb xcfb pm.

Move the qvss (pm) -style mmap()ed device interface, kernel tracking
of mouse button/movement events, and placing mouse/keyboard
events in an mmap()ed ring buffer, out of the framebuffer device
drivers and into separate source files. The fb pseudo-device driver
uses the qvss-compatible interface, since that's what the (R5) X
server uses.
1995-09-11 07:45:36 +00:00