🚀 go-pugleaf

  $@@iMUBg3X$N66K\$G$9!#(Jsparc $@$N(JCLASSIC $@$G:#;H$C$F$$$k%b%K%?$,(J
 $@;H$($k$+$N<ALd$r$7$^$7$?$,!"<+8J(Jfollow $@$r$7$^$9!#(J

comp.sys.sun.hardware $@$G$=$N5-;v$r$_$^$7$?(J>$@$H$$$&$3$H$G(J
$@$"$?$7$N>l9g$O(JOK $@$H$$$&$3$H$G$7$?!#(J
# $@F|K\%5%s$N1D6H$5$s%3%N(J news $@$r8+$J$$$G(J > ishida san 
-----------------------------------------------------------------
From: paulr@fulcrum.oz.au (Paul Rosham)
Subject: Re: SPARCclassic frame buffer - can it be fooled?
Message-ID: <1993Jan29.053056.29080@fulcrum.oz.au>
Keywords: frame buffer cgthree cgtwo resulution monitor
Organization: The Fulcrum Consulting Group
References: <haberman.728100659@msi.umn.edu>
Date: Fri, 29 Jan 1993 05:30:56 GMT
Lines: 27


haberman@s6.msi.umn.edu (Joe Habermann) writes:

>The other day I tried an experiment.  I took a 15" SPARCclassic
>monitor (machine hasn't been set up yet because we're waiting on
>software) and hooked it up to a 4/330.  It worked fine and
>displayed a resolution of 1152x900.  This got me wonderering.

>What kind of frame buffer does the Classic use?  Is it a cgtwo
>or cgthree?  Can it be fooled into believing that a 15" monitor
>is really a 16" monitor?  Just wondering if there is a way to
>sacrifice pixel size in exchange for real estate.

The pixel size is irrelevant to the framebuffer, if the monitor+cable
signals say that the monitor can do 1152x900@66Hz, the framebuffer will
obey if it can.  Similar to when it says it can do 1152x900@76Hz, or
1024x768@76Hz, which the 15" tube does both of.

Most new Sun monitors will do 1152x900@76Hz, older monitors do
1152x900@66Hz.

Some framebuffers will also support 1280x1024@76Hz and even
1600x1280@76Hz.

Summary: if you have a 16" or 19" tube, the Classic will probably
use them at 1152x900@76Hz. Standard Sun frequencies are used.
-PaulR.