Date: Sun, 03 Aug 1997 17:26:55 -0700 From: Amancio Hasty <hasty@rah.star-gate.com> To: Terry Lambert <terry@lambert.org> Cc: bde@zeta.org.au (Bruce Evans), jbarrm@panix.com, sherwink@ix.netcom.com, current@FreeBSD.ORG Subject: Re: XFree86-3.3, FBSD-2.2.2 & ViRGE/VX Message-ID: <199708040026.RAA01522@rah.star-gate.com> In-Reply-To: Your message of "Sun, 03 Aug 1997 15:03:09 PDT." <199708032203.PAA02444@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, it is true and this is and old problem also I think it surfaces because some PC chisets incorrectly map the io address by truncating the S3 ioaddress. The problem has been there since day one of S3 chipsets. Cheers, Amancio >From The Desk Of Terry Lambert : > > Some S3 boards uses the same i/o ports as sio3. You shouldn't use both > > sio3 and X these boards. Some S3 boards crash at boot time when sio3 > > is probed. You shouldn't configure sio3 if you have one of these boards > > (even if you don't use X). > > S3 boards? > > Is this true? > > I know there was a problem with Mach32 and Mach64 boards incorrectly > listening to I/O's on some ports before being put into a mode where > listening was mandatory (it's a bug in the chipset). > > I didn't think S3 had the same problem... I run nothing but S3 cards, > and I haven't seen the problem on any of my machines... > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708040026.RAA01522>