home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.linux:21932 comp.windows.x.i386unix:166
- Newsgroups: comp.os.linux,comp.windows.x.i386unix
- Path: sparky!uunet!noc.near.net!lynx!random.ccs.northeastern.edu!news
- From: jtsilla@damon.ccs.northeastern.edu (James Tsillas)
- Subject: Re: XFree 1.1 with T8900; mixed results.
- In-Reply-To: roell@informatik.tu-muenchen.de's message of 28 Dec 92 18: 18:42 GMT
- Message-ID: <JTSILLA.92Dec28145157@damon.ccs.northeastern.edu>
- Sender: news@random.ccs.northeastern.edu
- Nntp-Posting-Host: damon-gateway.ccs.northeastern.edu
- Organization: Northeastern University, Boston, MA
- References: <1992Dec28.165948.17397@fwi.uva.nl>
- <1992Dec28.181842.21972@Informatik.TU-Muenchen.DE>
- Date: Mon, 28 Dec 1992 19:51:57 GMT
- Lines: 23
-
-
- To answer the first question (Why only use 64k with the Mono server):
-
- As you may be aware the PC architecture only supports shared
- memory in 64k segments in the range between 640k and 1024k in real
- memory. Designers wishing to make more shared memory available have been
- forced to provide a bank switching mechanism to allow access to that
- memory in 64k chunks. A display driver would therefore need to map a
- "virtual" flat range of memory to a segmented range. This is done by the
- color server which can address in excess of 64k. The monochrome server
- has no support yet for the flat to segmented mapping so you are limited
- to the 64k (flat) segment. An effort is underway to implement a banked
- driver for the monochrome server which (if all goes well) will become
- part of XFree86 in some future release (That's all I can say about this
- at this point).
-
- regards,
- -Jim.
- --
- *** James Tsillas jtsilla@damon.ccs.northeastern.edu ***
- *** Work: (508)898-2800, Home: (617)641-0513 ***
- *** "He is after me. Jim is after him." ***
- *** - Hop on Pop, Dr. Seuss ***
-