🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.sun
Article #12871

How to catch display blanking interval?

#12871
From: Jeffrey Mulligan
Date: Wed, 17 May 1989 16:23
28 lines
1697 bytes
I am trying to synchronize the updating of a display on the SUN-4/110
console with the display refresh.  In cgfour(4S), the following sentence
appears in the discussion of the ioctl FBIOPUTCMAP:

	The driver uses color board vertical-retrace interrupts to
	load the color map.

I had hoped that this ioctl would cause the program to hang until the
retrace interval, but this does not seem to happen.  I assume that the
ioctl causes the color map change to be queued, and that the hardware gets
loaded by the interrupt handler.

I also turned up the following lines in /usr/include/sun/fbio.h :

/* Vertical retrace support. */
#define FBIOVERTICAL	_IOW(F, 9, int)

What the heck is this for???  I tried calling ioctl with this code, and
nothing happened (i.e., no delays, no data returned).

I remember a few months back there was a long posting on undocumented
features of the sun framebuffer from someone who was hacking their own
operating system.  I'm sure what I want to do can be done, but I'd like to
do it in the approved fashion if possible.

	Jeff Mulligan (jbm@aurora.arc.nasa.gov)
	NASA/Ames Research Ctr., Mail Stop 239-3, Moffet Field CA, 94035
	(415) 694-6290
Technical Details
Message-ID: <3586@eos.UUCP>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!husc6!rice!sun-spots-request

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!husc6!rice!sun-spots-request
From: eos!jbm@eos.arc.nasa.gov (Jeffrey Mulligan)
Newsgroups: comp.sys.sun
Subject: How to catch display blanking interval?
Keywords: Hardware
Message-ID: <3586@eos.UUCP>
Date: 17 May 89 16:23:45 GMT
Sender: usenet@rice.edu
Organization: NASA Ames Research Center, California
Lines: 28
Approved: Sun-Spots@rice.edu
Original-Date: 11 May 89 01:55:28 GMT
X-Sun-Spots-Digest: Volume 7, Issue 290, message 10 of 13