Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5785 ; Fri, 01 Jan 93 01:55:45 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!informatik.tu-muenchen.de!roell From: roell@informatik.tu-muenchen.de (Thomas Roell) Subject: Re: ET4000/W32 and VESA VL-Bus In-Reply-To: stripes@pix.com's message of Thu, 24 Dec 1992 04:31:52 GMT References: <BzBEI1.CH@aeon.in-berlin.de> <1992Dec20.153314.24148@Informatik.TU-Muenchen.DE> <1992Dec22.125737.24088@cti-software.nl> <Bzqxx4.614@pix.com> Sender: news@Informatik.TU-Muenchen.DE (USENET Newssystem) Organization: Inst. fuer Informatik, Technische Univ. Muenchen, Germany Date: Thu, 31 Dec 1992 11:48:47 GMT Message-ID: <1992Dec31.114847.6323@Informatik.TU-Muenchen.DE> Lines: 23 > However I can't think of any way in which the 4000/W32 could be bad for X > that the S3 wasn't. (it could include more windows stuff 'tho) Except for > devoting a larger part of the chip for stuff useless to X... Just one example, this time from the XGA. This XGA is tuned for MS-Windows. MS-Windows allows you to have a fullblow bitmap as a clipping area (of cource X does as well, but usually only rectangles or a list thereof are used). The XGA implements this in hardware. But one the other hand if you just want to have the good old scirroring (i.e. only one clipping rectangle instead of a whole bitmap), the performance penalty is significant, and you end up in doing software clipping instead of the hardware clipping you can do with the S3 guys. The point is that MS-Windows is in some places stuff with more (unnecessary ?) features that slow sometimes down the more general cases, when done in hardware. - Thomas -- ------------------------------------------------------------------------------- Das Reh springt hoch, e-mail: roell@sgcs.com das Reh springt weit, #include <sys/pizza.h> was soll es tun, es hat ja Zeit ...