*BSD News Article 23121


Return to BSD News archive

Xref: sserve comp.windows.x.i386unix:4430 comp.windows.x:60417 comp.unix.pc-clone.32bit:4781 comp.os.mach:3386 comp.unix.osf.osf1:1280 comp.unix.bsd:12820 comp.unix.sys5.r4:5279 comp.unix.sys5.r3:1402
Newsgroups: comp.windows.x.i386unix,comp.windows.x,comp.unix.pc-clone.32bit,comp.os.mach,comp.unix.osf.osf1,comp,comp.unix.bsd,biz.univel.misc,comp.unix.sys5.r4,comp.unix.sys5.r3
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!crcnis1.unl.edu!wupost!howland.reston.ans.net!pipex!uunet!olivea!hal.com!decwrl!csus.edu!netcom.com!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Annoucing the release of XFree86 2.0
Message-ID: <hastyCFswD9.GG6@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <CFrLs5.9qC@aib.com> <hastyCFrz64.LM5@netcom.com> <2b298e$she@pdq.coe.montana.edu>
Date: Mon, 1 Nov 1993 06:51:09 GMT
Lines: 48

In article <2b298e$she@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes:
>In article <hastyCFrz64.LM5@netcom.com>,
>Amancio Hasty Jr <hasty@netcom.com> wrote:
>>Minor corrections:
>>
>>
>>>                Information for former XS3 users
>
>
>>>  -  Real support for the S3 86C928 (no Hack needed); the server defaults
>>>     to use the Memory-Mapped-IO (mmio) routines for 928 boards which give
>>>     a significant performance boost on some operations. This can be
>>>     overruled with the 'chipset "s3_generic"' keyword.
>>
>>	For quite sometime, XS3 has worked with the 928 cards;however,
>>	the linux support has lacked behind.
>>	XS3.mmio does use memory mapped i/o.
>
>On local bus cards?

Yes!!

David Greeman reported success with XS3.mmio and his #9 S3 928 VLB
for nearly 4 months and this was posted several times in this group.

And I have two systems: a 486DX33 and a 486DX266 VLB.


>you are risking HARDWARE damage to your video card.  At ~$300/card, I
>would not want to be using XS3 when my card went belly-up.  Note that
>the limitation is for a particular RAMDAC, and not for all RAMDACS. A
>fix is in the works, but the release needed to go out the door.
>

Once again, I was not  aware of any such problems but thanks for letting
me know.

I assure that I am not going to wait  for any fix from this group.

Later,
	Amancio


-- 
This message brought to you by the letters X and S and the number 3
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/X