The sparc port has the 'eeprom' utility which is used for
	modifying values in the eeprom (or openprom). Maybe it should be
	extended/renamed for macppc also?


		David/absolute

On Fri, 29 Oct 1999, Geoffrey C Kinnel wrote:

> 
> 
> Bill Studenmund wrote:
> > 
> > On Fri, 29 Oct 1999, Aaron Jackson wrote:
> > 
> > > Get the LinuxPPC1997* file from ftp.aaronjackson.com.  There is some
> > > examples of changing screen resolution.  Maybe somebody could port the
> > > vmode program to NetBSD?  I'm not much of a programmer, so I haven't
> > 
> > That might be good. :-)
> > 
> > > looked at the source code, but I think it is just writing values to
> > > nvram.  Also, you could set the screen resolution in macos and it
> > > *should* also carry over into NetBSD, unless something in the boot
> > > process resets the nvram.
> > 
> > It does carry over. MacOS is why my Blue G3 is in 1152xbig mode. :-)
> > 
> > Note: One time I switched monitors, and got only 640x480 until I booted
> > MacOS. OF noticed that the monitor changed, and rolled back to a safe
> > setting.
> >
> 
> Are OF settings held in the same PRAM that screen settings are
> stored? Can you modify the video settings in PRAM via OF? I think
> that is the issue. Linuxppc has the following shell utilities: 
> vmode - for setting res and color depth values for the session,
> nvvideo - for setting res and color depth information in PRAM
> and, 
> nvsetenv - for setting OF values. 
> 
> Anyone grok this fully? Could a theoretical Non-Volatile
> Attribute Controller and Universal Utility Masterfile (N-VACUUM
> :) be created to provide one stop shopping?
> 
> Do the screen-#rows and screen-#columns OF variables do the
> trick? They are in hex, and appear to be counting characters, not
> pixels. *shrug*
> 
> Just tossing out ideas.
> 
> Geoff
>