*BSD News Article 25453


Return to BSD News archive

Newsgroups: comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: FreeBSD 1.0R, XFree-86 2.0, and Diamond Speedstar
Message-ID: <hastyCIu9K5.LGy@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <1993Dec29.041309.17997@pool.info.sunyit.edu> <CIt0rC.F49@usenet.ucs.indiana.edu> <1993Dec30.044656.23447@pool.info.sunyit.edu>
Date: Thu, 30 Dec 1993 08:14:28 GMT
Lines: 20

In article <1993Dec30.044656.23447@pool.info.sunyit.edu> uddc@pool.info.sunyit.edu (David D. Colbey) writes:
>Jim Pitts (pitts@mimosa.astro.indiana.edu) wrote:
>: In article <1993Dec29.041309.17997@pool.info.sunyit.edu>,
>: David D. Colbey <uddc@pool.info.sunyit.edu> wrote:
<stuff about diamond clock programming deleted>

It seems to me that the proper way for more than one reason is 
to provide a mechanism under *bsd to initialize the cards via 
a bios call. The problem with Diamond products is one extreme 
the other is the general initialization of new graphic cards
or special resolutions provided via the manufacturer.

	My 0.1 cent :)
	Amancio

-- 
free unix, tcp/ip, X, gcc, sound: freebsd at freebsd.cdrom.com:/pub/FreeBSD
Amancio Hasty,  Consultant |
Home: (415) 495-3046       |  
e-mail hasty@netcom.com	   |  ftp-site depository of all my work:    
ahasty@cisco.com           |  sunvis.rtpnc.epa.gov:/pub/386bsd/X