diff options
Diffstat (limited to 'xc/programs/Xserver/hw/xfree86/doc')
45 files changed, 1275 insertions, 1050 deletions
diff --git a/xc/programs/Xserver/hw/xfree86/doc/DESIGN b/xc/programs/Xserver/hw/xfree86/doc/DESIGN index 9bd7e9cee..72f4c8755 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/DESIGN +++ b/xc/programs/Xserver/hw/xfree86/doc/DESIGN @@ -2,7 +2,7 @@ The XFree86 Project, Inc - Last modified 2 December 2000 + Last modified 1 May 2001 NOTE: This is a DRAFT document, and the interfaces described here are subject to change without notice. @@ -2100,13 +2100,14 @@ Next, the higher level functions that most drivers would use. ScreenInit() function, but only when serverGeneration == 1. - OptionInfoPtr xf86TokenToOptinfo(OptionInfoPtr table, int token) + OptionInfoPtr xf86TokenToOptinfo(const OptionInfoRec *table, int + token) Returns a pointer to the OptionInfoRec in table with a token field matching token. Returns NULL if no match is found. - Bool xf86IsOptionSet(OptionInfoPtr table, int token) + Bool xf86IsOptionSet(const OptionInfoRec *table, int token) Returns the found field of the OptionInfoRec in table with a token field matching token. This can be used for @@ -2115,13 +2116,13 @@ Next, the higher level functions that most drivers would use. mine the value of the option. Returns FALSE if no match is found. - char *xf86GetOptValString(OptionInfoPtr table, int token) + char *xf86GetOptValString(const OptionInfoRec *table, int token) Returns the value.str field of the OptionInfoRec in table with a token field matching token. Returns NULL if no match is found. - Bool xf86GetOptValInteger(OptionInfoPtr table, int token, + Bool xf86GetOptValInteger(const OptionInfoRec *table, int token, int *value) @@ -2132,21 +2133,21 @@ Next, the higher level functions that most drivers would use. tion. The function return value is as for xf86IsOption- Set(). - Bool xf86GetOptValULong(OptionInfoPtr table, int token, + Bool xf86GetOptValULong(const OptionInfoRec *table, int token, unsigned long *value) Like xf86GetOptValInteger(), except the value is treated as an unsigned long. - Bool xf86GetOptValReal(OptionInfoPtr table, int token, + Bool xf86GetOptValReal(const OptionInfoRec *table, int token, double *value) Like xf86GetOptValInteger(), except that value.realnum is used. - Bool xf86GetOptValFreq(OptionInfoPtr table, int token, + Bool xf86GetOptValFreq(const OptionInfoRec *table, int token, OptFreqUnits expectedUnits, double *value) @@ -2161,7 +2162,8 @@ Next, the higher level functions that most drivers would use. "10000" and expectedUnits is OPTUNITS_MHZ, the value returned is 10. - Bool xf86GetOptValBool(OptionInfoPtr table, int token, Bool *value) + Bool xf86GetOptValBool(const OptionInfoRec *table, int token, Bool + *value) This function is used to check boolean options (OPTV_BOOLEAN). If the function return value is FALSE, @@ -2176,7 +2178,8 @@ Next, the higher level functions that most drivers would use. present. It should normally be set to a default value before calling this function. - Bool xf86ReturnOptValBool(OptionInfoPtr table, int token, Bool def) + Bool xf86ReturnOptValBool(const OptionInfoRec *table, int token, + Bool def) This function is used to check boolean options (OPTV_BOOLEAN). If the option is set, its value is @@ -4905,7 +4908,15 @@ WRec. They are defined in vgaHW.h. fields of hwp with the standard VGA set of functions. This is called by vgaHWGetHWRec(), so there is usually no need to call this explicitly. The register access func- - tions are described below. + tions are described below. If the registers are shadowed + in some other port I/O space (for example a PCI I/O + region), these functions can be used to access the shad- + owed registers if hwp->PIOOffset is initialised with off- + set, calculated in such a way that when the standard VGA + I/O port value is added to it the correct offset into the + PIO area results. This value is initialised to zero in + vgaHWGetHWRec(). (Note: the PIOOffset functionality is + present in XFree86 4.1.0 and later.) void vgaHWSetMmioFuncs(vgaHWPtr hwp, CARD8 *base, int offset) @@ -4977,6 +4988,16 @@ WRec. They are defined in vgaHW.h. vgahw module is not loaded (for example, in the Chip- Probe() function). + void vgaHWEnable(vgaHWPtr hwp) + + This function enables the VGA subsystem. (Note, this + function is present in XFree86 4.1.0 and later.). + + void vgaHWDisable(vgaHWPtr hwp) + + This function disables the VGA subsystem. (Note, this + function is present in XFree86 4.1.0 and later.). + void vgaHWSave(ScrnInfoPtr pScrn, vgaRegPtr save, int flags) This function saves the VGA state. The state is written @@ -5236,6 +5257,17 @@ VGA access. The access functions are described here. Return the value read from the DAC Data register. + CARD8 readEnable(vgaHWptr hwp) + + Return the value read from the VGA Enable register. + (Note: This function is present in XFree86 4.1.0 and + later.) + + void writeEnable(vgaHWPtr hwp, CARD8 value) + + Write value to the VGA Enable register. (Note: This + function is present in XFree86 4.1.0 and later.) + 20. Some notes about writing a driver NOTE: some parts of this are not up to date @@ -5433,6 +5465,7 @@ Drivers must NOT include the following: Bool noAccel; Bool hwCursor; CloseScreenProcPtr CloseScreen; + OptionInfoPtr Options; ... } ZZZRec, *ZZZPtr; @@ -5447,7 +5480,7 @@ Drivers must NOT include the following: OPTION_NOACCEL } ZZZOpts; - static OptionInfoRec ZZZOptions[] = { + static const OptionInfoRec ZZZOptions[] = { { OPTION_FOO_HACK, "FooHack", OPTV_INTEGER, {0}, FALSE }, { OPTION_PCI_RETRY, "PciRetry", OPTV_BOOLEAN, {0}, FALSE }, { OPTION_HW_CURSOR, "HWcursor", OPTV_BOOLEAN, {0}, FALSE }, @@ -5455,8 +5488,6 @@ Drivers must NOT include the following: { -1, NULL, OPTV_NONE, {0}, FALSE } }; - #define nZZZOptions (sizeof(ZZZOptions) / sizeof(ZZZOptions[0])) - 20.3 Functions 20.3.1 SetupProc @@ -5704,8 +5735,6 @@ NOTES: static Bool ZZZPreInit(ScrnInfoPtr pScrn, int flags) { - OptionInfoRec options[nZZZOptions]; - /* Fill in the monitor field */ pScrn->monitor = pScrn->confScreen->monitor; @@ -5784,10 +5813,14 @@ NOTES: /* * Process the options based on the information in ZZZOptions. - * The results are written to options. + * The results are written to pZzz->Options. If all of the options + * processing is done within this function a local variable "options" + * can be used instead of pZzz->Options. */ - (void)memcpy(options, ZZZOptions, sizeof(ZZZOptions)); - xf86ProcessOptions(pScrn->scrnIndex, pScrn->options, options); + if (!(pZzz->Options = xalloc(sizeof(ZZZOptions)))) + return FALSE; + (void)memcpy(pZzz->Options, ZZZOptions, sizeof(ZZZOptions)); + xf86ProcessOptions(pScrn->scrnIndex, pScrn->options, pZzz->Options); /* * Set various fields of ScrnInfoRec and/or ZZZRec based on @@ -5795,25 +5828,25 @@ NOTES: */ from = X_DEFAULT; pZzz->hwCursor = FALSE; - if (xf86IsOptionSet(options, OPTION_HW_CURSOR)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_HW_CURSOR)) { from = X_CONFIG; pZzz->hwCursor = TRUE; } xf86DrvMsg(pScrn->scrnIndex, from, "Using %s cursor\n", pZzz->hwCursor ? "HW" : "SW"); - if (xf86IsOptionSet(options, OPTION_NOACCEL)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_NOACCEL)) { pZzz->noAccel = TRUE; xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "Acceleration disabled\n"); } else { pZzz->noAccel = FALSE; } - if (xf86IsOptionSet(options, OPTION_PCI_RETRY)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_PCI_RETRY)) { pZzz->UsePCIRetry = TRUE; xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "PCI retry enabled\n"); } pZzz->fooHack = 0; - if (xf86GetOptValInteger(options, OPTION_FOO_HACK, + if (xf86GetOptValInteger(pZzz->Options, OPTION_FOO_HACK, &pZzz->fooHack)) { xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "Foo Hack set to %d\n", pZzz->fooHack); @@ -6302,7 +6335,7 @@ eScreen() function. ZZZFreeRec(xf86Screens[scrnIndex]); } - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml,v 1.40 2000/12/27 04:57:08 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml,v 1.44 2001/05/19 00:40:30 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/DESIGN,v 1.35 2001/01/21 21:53:25 tsi Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/DESIGN,v 1.36.2.1 2001/06/01 18:26:42 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/Imakefile b/xc/programs/Xserver/hw/xfree86/doc/Imakefile index a0ffbbf17..8c0b4350f 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/Imakefile +++ b/xc/programs/Xserver/hw/xfree86/doc/Imakefile @@ -4,7 +4,7 @@ XCOMM $XConsortium: Imakefile /main/33 1996/10/28 05:12:24 kaleb $ -XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/doc/Imakefile,v 3.75 2001/03/02 02:45:37 dawes Exp $ +XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/doc/Imakefile,v 3.76.2.1 2001/06/01 18:09:46 dawes Exp $ #include <Server.tmpl> #include <lnxdoc.rules> @@ -76,7 +76,7 @@ HWREADME = \ /*ReadmeFile(WstDig)*/ \ $(_NULLENTRY_) -MAINDOCS = LICENSE README /*ReadmeFile(Config)*/ /*BUILD*/ RELNOTES \ +MAINDOCS = LICENSE README /*ReadmeFile(Config)*/ /*BUILD*/ /*RELNOTES*/ \ Install Status DESIGN Versions OTHERDOCS = /*VideoModes.doc*/ /*QuickStart.doc*/ /*xinput*/ \ @@ -85,7 +85,7 @@ OTHERDOCS = /*VideoModes.doc*/ /*QuickStart.doc*/ /*xinput*/ \ #endif MISCDOCS = ServersOnly /*LbxproxyOnly*/ $(REPORTFORM) ReadmeFile(DGA) \ - VideoBoard98 + VideoBoard98 ReadmeFile(rapidaccess) DATABASE = /* modeDB.txt */ /* AccelCards Monitors Devices */ diff --git a/xc/programs/Xserver/hw/xfree86/doc/Install b/xc/programs/Xserver/hw/xfree86/doc/Install index 7846ad0f2..fc1a90ca9 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/Install +++ b/xc/programs/Xserver/hw/xfree86/doc/Install @@ -1,8 +1,8 @@ - Installation Details for XFree86[tm] 4.0.2 + Installation Details for XFree86[tm] 4.1.0 The XFree86 Project, Inc - 15 December 2000 + 1 June 2001 Abstract @@ -20,10 +20,10 @@ vide a customized version of the GNU tar utility called "extract" and an installation script. We recommend that these be used to install the bina- ries. -2. Downloading the XFree86 4.0.2 binaries +2. Downloading the XFree86 4.1.0 binaries -We provide XFree86 4.0.2 binaries for a range of operating systems at our ftp -site <URL:ftp://ftp.xfree86.org/pub/XFree86/4.0.2/binaries/>. Often during +We provide XFree86 4.1.0 binaries for a range of operating systems at our ftp +site <URL:ftp://ftp.xfree86.org/pub/XFree86/4.1.0/binaries/>. Often during releases our ftp site is heavily loaded. Instead of downloading directly from us we recommend that instead you use one of our mirror sites. Another advantage of using our mirror sites is that some of them support http access @@ -43,31 +43,46 @@ The output of this utility tells you which is the correct set of binaries for you to download. If you are careful with this step you will save yourself a lot time and trouble from NOT downloading an incompatible distribution. -NOTE: the Xinstall.sh script must be downloaded in binary mode, otherwise it -won't run correctly. If you get lots of "command not found" messages when -you try to run it, then it is most likely because the script wasn't down- -loaded in binary mode. Some web browsers won't do this for files of that -name, so we also have a copy of it called "Xinstall.bin", and most browsers -should download that correctly. When downloading it under this name, select -"save as" on your browser, and save the file under the name "Xinstall.sh". +NOTES: + + o The Xinstall.sh script must be downloaded in binary mode, otherwise it + won't run correctly. If you get lots of "command not found" messages + when you try to run it, then it is most likely because the script wasn't + downloaded in binary mode. Some web browsers won't do this for files of + that name, so we also have a copy of it called "Xinstall.bin", and most + browsers should download that correctly. When downloading it under this + name, select "save as" on your browser, and save the file under the name + "Xinstall.sh". + + o The Xinstall.sh script requires some system commands and utilities to + function correctly. While most systems will have these, some Linux + installations may not. If you find that the script is failing because + of some missing system command, you will need to install it before you + can continue. If you don't know how to do this, then we recommend that + you obtain this version of XFree86 from your Operating System distribu- + tor. + + o Always use the version of the Xinstall.sh script that's provided with + the release you're installing. Older versions of the script may not + install newer releases correctly. Once you're run the Xinstall.sh script and found which binary distribution is suitable for your system, download the necessary files. The twelve (12) mandatory files for all installations are listed below. If you have not downloaded all of the files, the installer script will complain. - 1. Xinstall.sh The installer script - 2. extract The utility for extracting tarballs - 3. Xbin.tgz X clients/utilities and run-time libraries - 4. Xlib.tgz Some data files required at run-time - 5. Xman.tgz Manual pages - 6. Xdoc.tgz XFree86 documentation - 7. Xfnts.tgz Base set of fonts - 8. Xfenc.tgz Base set of font encoding data - 9. Xetc.tgz Run-time configuration files - 10. Xvar.tgz Run-time data - 11. Xxserv.tgz XFree86 X server - 12. Xmod.tgz XFree86 X server modules + 1. Xinstall.sh The installer script + 2. extract The utility for extracting tarballs + 3. Xbin.tgz X clients/utilities and run-time libraries + 4. Xlib.tgz Some data files required at run-time + 5. Xman.tgz Manual pages + 6. Xdoc.tgz XFree86 documentation + 7. Xfnts.tgz Base set of fonts + 8. Xfenc.tgz Base set of font encoding data + 9. Xetc.tgz Run-time configuration files + 10. Xvar.tgz Run-time data + 11. Xxserv.tgz XFree86 X server + 12. Xmod.tgz XFree86 X server modules NOTES: @@ -86,22 +101,20 @@ NOTES: o Some distributions may have additional mandatory tarballs. While rare, the installer script will tell you if any are missing. -The following thirteen (13) tarballs are optional. You should download the +The following eleven (11) tarballs are optional. You should download the ones you want to install. - 1. Xfsrv.tgz Font server - 2. Xnest.tgz Nested X server - 3. Xprog.tgz X header files, config files and compile-time libs - 4. Xprt.tgz X Print server - 5. Xvfb.tgz Virtual framebuffer X server - 6. Xf100.tgz 100dpi fonts - 7. Xfcyr.tgz Cyrillic fonts - 8. Xflat2.tgz Latin-2 fonts - 9. Xfnon.tgz Some large bitmap fonts - 10. Xfscl.tgz Scalable fonts (Speedo and Type1) - 11. Xhtml.tgz HTML version of the documentation - 12. Xps.tgz PostScript version of the documentation - 13. Xjdoc.tgz Documentation in Japanese + 1. Xfsrv.tgz Font server + 2. Xnest.tgz Nested X server + 3. Xprog.tgz X header files, config files and compile-time libs + 4. Xprt.tgz X Print server + 5. Xvfb.tgz Virtual framebuffer X server + 6. Xf100.tgz 100dpi fonts + 7. Xfcyr.tgz Cyrillic fonts + 8. Xfscl.tgz Scalable fonts (Speedo and Type1) + 9. Xhtml.tgz HTML version of the documentation + 10. Xps.tgz PostScript version of the documentation + 11. Xjdoc.tgz Documentation in Japanese NOTES: @@ -110,9 +123,9 @@ NOTES: If you miss some and want to install them later, go to the Manual Installa- tion (section 4., page 1) section. -3. Installing XFree86 4.0.2 using the Xinstall.sh script +3. Installing XFree86 4.1.0 using the Xinstall.sh script -We strongly recommend that our XFree86 4.0.2 binaries be installed using the +We strongly recommend that our XFree86 4.1.0 binaries be installed using the Xinstall.sh script that we provide. There are a lot of steps in the manual installation process, and those steps can vary according to the platform and hardware setup. There is a description of the manual installation process @@ -229,7 +242,7 @@ later that you need it, you can create it easily by running: The next step is to configure the X server. That is covered in detail in an as-yet unwritten document :-(. In the meantime, there are three ways to cre- -ate a basic X server configuration file for XFree86 4.0.2. One is to run the +ate a basic X server configuration file for XFree86 4.1.0. One is to run the xf86config utility. Another is to run the xf86cfg utility. The third option is to use the new -configure X server option: @@ -248,9 +261,9 @@ old XF86_* and/or XF98_* X server binaries from /usr/X11R6/bin. After the X server configuration is done, it may be advisable to reboot, especially if you run xdm (or equivalent) or the font server (xfs). -4. Installing XFree86 4.0.2 manually +4. Installing XFree86 4.1.0 manually -This section describes how to manually install the XFree86 4.0.2 binary dis- +This section describes how to manually install the XFree86 4.1.0 binary dis- tributions. You should only use this method if you know what you're doing. The information here covers some common cases, but not every possible case. @@ -288,6 +301,7 @@ tion procedure for this case is as follows: ln -s /etc/X11/xinit /usr/X11R6/lib/X11 ln -s /etc/X11/xsm /usr/X11R6/lib/X11 ln -s /etc/X11/xserver /usr/X11R6/lib/X11 + chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK /sbin/ldconfig /usr/X11R6/lib # For Linux /sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD /usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc @@ -347,11 +361,12 @@ Once that's done, the main part of the installation can be done: ./extract -C /usr/X11R6 `pwd`/X[a-df-uw-z]*.tgz ./extract -C /usr/X11R6 Xvfb.tgz # If you are installing Xvfb ./extract -C /var Xvar.tgz + chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK /sbin/ldconfig /usr/X11R6/lib # For Linux /sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD /usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml,v 1.11 2001/03/02 17:40:48 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml,v 1.11.2.2 2001/06/01 18:09:48 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/Install,v 1.11 2001/03/02 17:47:52 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/Install,v 1.11.2.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/LICENSE b/xc/programs/Xserver/hw/xfree86/doc/LICENSE index c6890edc3..993d4d700 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/LICENSE +++ b/xc/programs/Xserver/hw/xfree86/doc/LICENSE @@ -595,4 +595,4 @@ For further information, contact: Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/LICENSE.sgml,v 1.8 2001/03/16 22:13:19 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/LICENSE,v 1.12 2001/03/25 05:42:43 tsi Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/LICENSE,v 1.12.2.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/OS2.Notes b/xc/programs/Xserver/hw/xfree86/doc/OS2.Notes index b39511bee..d28e99232 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/OS2.Notes +++ b/xc/programs/Xserver/hw/xfree86/doc/OS2.Notes @@ -226,4 +226,4 @@ Well, you see, this was quite easy :-) $XConsortium: OS2note.sgml /main/1 1996/02/24 10:08:59 kaleb $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/OS2.Notes,v 3.17 2000/12/01 19:47:45 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/OS2.Notes,v 3.17.4.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README b/xc/programs/Xserver/hw/xfree86/doc/README index ffc669ceb..76ac496f1 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README +++ b/xc/programs/Xserver/hw/xfree86/doc/README @@ -1,8 +1,8 @@ - README for XFree86[tm] 4.0.2 + README for XFree86[tm] 4.1.0 The XFree86 Project, Inc - 15 December 2000 + 2 June 2001 Abstract @@ -10,9 +10,9 @@ supports several UNIX(R) and UNIX-like (such as Linux, the BSDs and Solaris x86) operating systems on Intel and other platforms. -1. What is XFree86 4.0.2? +1. What is XFree86 4.1.0? -XFree86 4.0.2 is the third full release in the new XFree86 4 series. +XFree86 4.1.0 is the fourth full release in the XFree86 4 series. XFree86 release 4 is a major re-design of the basic architectural underpin- nings of XFree86's implementation of the original X Consortium's X Server. @@ -25,7 +25,7 @@ installing the new driver module and updating the configuration file. The road to XFree86 release 4 began as an architectural concept in mid 1997, with the serious framework being implemented in code the beginning of 1998. There were several snapshots on the road to 4.0 which are now part of the 4.0 -base release. The 4.0.2 version is an upgrade to 4.0.1, which include more +base release. The 4.1.0 version is an upgrade to 4.0.3, which include more hardware ports, code enhancements and bug fixes. Release 4 also included the long-awaited integration of the DRI (Direct Ren- @@ -38,8 +38,6 @@ converted over to the 4.x series, those required for most modern video hard- ware are available. Please check the Driver Status document first to see whether your hardware is supported before upgrading to the 4.x series. -Specific release enhancements can be viewed in the Release Notes. - The XFree86 version numbering system has had some changes as of the 4.0.2 release. Information about this can be found in the Versions Document. @@ -116,38 +114,47 @@ Once your work is finished (coded, debugged and documented) please send your fix to <fixes@XFree86.org>. This will ensure that they are included in future releases. And thanks! You make this truly an Open group. -4. How to get XFree86 4.0.2 +4. How to get XFree86 4.1.0 -XFree86 4.0.2 can be found at the XFree86 ftp server -<URL:ftp://ftp.xfree86.org/pub/XFree86/4.0.2/>, and at mirrors of this +XFree86 4.1.0 can be found at the XFree86 ftp server +<URL:ftp://ftp.xfree86.org/pub/XFree86/4.1.0/>, and at mirrors of this server. Information about obtaining and installing binary distributions of this release can be found in the Installation Document. Information about obtaining the release in source form is given below. -The source for version 4.0.2 is split into three tarballs: X402src-1.tgz, -X402src-2.tgz, X402src-3.tgz. The first contains everything except the fonts -and general X11 documentation. It is sufficient for building XFree86 is you +The source for version 4.1.0 is split into three tarballs: X410src-1.tgz, +X410src-2.tgz, X410src-3.tgz. The first contains everything except the fonts +and general X11 documentation. It is sufficient for building XFree86 if you already have a set of fonts. The second contains the fonts and the source for the general X11 documentation. The third contains the general X11 docu- mentation in hardcopy format. -A source patch relative to version 4.0.1 is also available. Because of its -size, it is split into four parts. The patch files are 4.0.1-4.0.2.diff1.gz, -4.0.1-4.0.2.diff2.gz, 4.0.1-4.0.2.diff3.gz and 4.0.1-4.0.2.diff4.gz. There +A source patch relative to version 4.0.2 is also available. Because of its +size, it is split into four parts. The patch files are 4.0.2-4.1.0.diff1.gz, +4.0.2-4.1.0.diff2.gz, 4.0.2-4.1.0.diff3.gz and 4.0.2-4.1.0.diff4.gz. There is also a tarball that contains some files that have components that can't be -included in a diff. It is 4.0.2.tgz. These patches should be applied to a -clean 4.0.1 source tree, working from the directory containing the xc/ direc- +included in a diff. It is 4.1.0.tgz. These patches should be applied to a +clean 4.0.2 source tree, working from the directory containing the xc/ direc- tory. The patches should be applied by running: - gzip -d < 4.0.1-4.0.2.diff1.gz | patch -p0 -E - gzip -d < 4.0.1-4.0.2.diff2.gz | patch -p0 -E - gzip -d < 4.0.1-4.0.2.diff3.gz | patch -p0 -E - gzip -d < 4.0.1-4.0.2.diff4.gz | patch -p0 -E + gzip -d < 4.0.2-4.1.0.diff1.gz | patch -p0 -E + gzip -d < 4.0.2-4.1.0.diff2.gz | patch -p0 -E + gzip -d < 4.0.2-4.1.0.diff3.gz | patch -p0 -E + gzip -d < 4.0.2-4.1.0.diff4.gz | patch -p0 -E + + rm -f xc/programs/xieperf/images/image.012 + rm -fr xc/fonts/bdf/latin2 + rm -fr xc/fonts/bdf/100dpi + rm -fr xc/fonts/bdf/75dpi + + gzip -d < 4.1.0.tgz | tar vxf - - gzip -d < 4.0.2.tgz | tar vxf - +Patches might also be available relative to 4.0.3. If so, the instructions +for applying them are the same, except that you should start with a clean +4.0.3 source tree. -The contrib part of the distribution has been folded into the main source -tree, so a separate contrib tarball is no longer required. +The contrib part of the distribution was folded into the main source tree a +while ago, so a separate contrib tarball is not required. To format the XFree86 documentation use the latest version of our doctools package available as doctools-1.2.tgz. @@ -161,7 +168,7 @@ yourself, send the entire log file with your bug report but not the operating system core dump. Do not edit the log file as our developers use it to reproduce and debug your problem. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.113 2001/03/16 22:13:19 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.113.2.3 2001/06/02 16:17:40 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README,v 3.111 2001/03/25 05:42:43 tsi Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README,v 3.111.2.3 2001/06/02 16:21:49 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.DECtga b/xc/programs/Xserver/hw/xfree86/doc/README.DECtga index b48be24d2..d734dfcda 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.DECtga +++ b/xc/programs/Xserver/hw/xfree86/doc/README.DECtga @@ -6,7 +6,7 @@ 1. DEC 21030 - o The DEC 21030 is supported by XFree86 4.0.2. The driver is now par- + o The DEC 21030 is supported by XFree86 4.1.0. The driver is now par- tially accelerated. The built-in graphics on the Multia is supported in 8-plane mode, and PCI cards with 8 or 16 MB framebuffers are supported in 24-plane mode. TGA2 (aka PowerStorm 3D30/4D20) cards are not cur- @@ -65,4 +65,4 @@ Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DECtga.sgml,v 3.9 2000/03/06 22:59:23 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DECtga,v 3.17 2000/12/01 19:47:46 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DECtga,v 3.17.4.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.DRI b/xc/programs/Xserver/hw/xfree86/doc/README.DRI index 5509f502b..0d3f897f4 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.DRI +++ b/xc/programs/Xserver/hw/xfree86/doc/README.DRI @@ -2,7 +2,7 @@ VA Linux Systems, Inc. Professional Services - Graphics. - 15 March 2001 + 3 May 2001 1. Preamble @@ -114,21 +114,20 @@ graphics hardware: o ATI Rage 128, supported on Intel x86 and AMD: - o Rage Fury AGP + o Rage Fury - o Rage Magnum AGP + o Rage Magnum - o XPERT 2000 AGP + o XPERT 2000 - o XPERT 128 AGP + o XPERT 128 - o XPERT 99 AGP + o XPERT 99 - o All-in-Wonder 128 AGP + o All-in-Wonder 128 - The PCI versions of these cards also have minimal support. Note that - there are Rage 128 Pro boards on the market but they're not yet sup- - ported. + Note that both PCI and AGP versions of Rage 128 based cards are sup- + ported at this time. o ATI Radeon, supported on Intel x86 and AMD: @@ -563,7 +562,7 @@ bleshooting. 10.1 3dfx Banshee, Voodoo3, Voodoo4 and Voodoo5 Series -10.1.1 Dependencies +10.1.1 Requirements The 3dfx DRI driver requires special versions of the 3dfx Glide library. Different versions of Glide are needed for Banshee/Voodoo3 than for @@ -659,7 +658,7 @@ A software-based accumulation buffer is available in both 16 and 32bpp modes. acceleration is not supported in that mode. 32bpp mode is fully 3D accelerated. -10.1.4 Performance +10.1.4 Performance and Features o Normally, buffer swapping in double-buffered applications is synchro- nized to your monitor's refresh rate. This may be overridden by setting @@ -727,6 +726,9 @@ A software-based accumulation buffer is available in both 16 and 32bpp modes. o The lowest mipmap level is sometimes miscolored in trilinear- sampled polygons. + o The GL_EXT_texture_env_combine extension is supported on the Voodoo4 and + Voodoo5. + 10.1.5 Known Problems o The lowest mipmap level is sometimes miscolored in trilinear- sampled @@ -745,11 +747,9 @@ A software-based accumulation buffer is available in both 16 and 32bpp modes. 10.2 Intel i810 -10.2.1 Dependencies +10.2.1 Requirements -A Linux kernel with AGP GART support is required. The 2.2.x kernel series -does not have AGP GART support. The 2.4.x test kernels have AGP GART and -have been tested with the i810. +A kernel with AGP GART support (such as Linux 2.4.x) is needed. 10.2.2 Configuration @@ -800,12 +800,31 @@ ules/dri/i810_dri.so. This will be automatically loaded by libGL.so. too little memory is available for DMA buffers, back and depth buffers and textures, direct rendering will be disabled. +10.2.4 Performance and Features + +Basically all of the i810 features which can be exposed through OpenGL 1.2 +are implemented. However, the following OpenGL features are implemented in +software and will be slow: + + o Stencil buffer and accumulation buffer operations + + o Blend subtract, min/max and logic op blend modes + + o glColorMask when any mask is set to false + + o GL_SEPARATE_SPECULAR_COLOR lighting mode + + o glDrawBuffer(GL_FRONT_AND_BACK) + + o Using 1D or 3D textures + + o Using texture borders + 10.3 Matrox G200 and G400 -10.3.1 Dependencies +10.3.1 Requirements -A Linux kernel with AGP GART support (such as the 2.4.x test kernels) is -needed. +A kernel with AGP GART support (such as Linux 2.4.x) is needed. 10.3.2 Configuration @@ -855,7 +874,7 @@ by the Xserver if needed. The DRI 3D driver for the G200/G400 should be in /usr/X11R6/lib/mod- ules/dri/mga_dri.so. This will be automatically loaded by libGL.so. -10.3.3 Performance +10.3.3 Performance and Features Software rendering will be used under any of the following conditions: @@ -878,7 +897,7 @@ Software rendering will be used under any of the following conditions: The AGP mode may be set to 1, 2, or 4. One is used by default. Higher AGP speeds may result in unreliable performance depending on your motherboard. -Compaq has funded the implementation of AGP acclerated ReadPixels and Draw- +Compaq has funded the implementation of AGP accelerated ReadPixels and Draw- Pixels in this driver. With this implementation, on a G400 drawing directly from AGP memory (exported to the client), throughput of up to 1 GB/sec has been measured. @@ -938,10 +957,9 @@ None. 10.4 ATI Rage 128 -10.4.1 Dependencies +10.4.1 Requirements -A Linux kernel with AGP GART support (such as the 2.4.x test kernels) is -needed. +A kernel with AGP GART support (such as Linux 2.4.x) is needed. 10.4.2 Configuration @@ -983,7 +1001,7 @@ ules/dri/r128_dri.so. This will be automatically loaded by libGL.so. You may also set your screen depth to 32 for 32bpp mode. -10.4.3 Performance +10.4.3 Performance and Features While PCI Rage 128 based cards are supported, they do not yet support PCI GART, so they will not perform as well as their AGP counterparts. @@ -992,6 +1010,22 @@ For AGP cards, the AGP mode may be set to 1, 2, or 4. One is used by default. Higher AGP speeds may result in unreliable performance depending on your motherboard. +Note that even at 32bpp there is no alpha channel. + +The following OpenGL features are implemented in software and will be slow: + + o Stencil buffer and accumulation buffer operations + + o Blend subtract, min/max and logic op blend modes + + o GL_SEPARATE_SPECULAR_COLOR lighting mode + + o glDrawBuffer(GL_FRONT_AND_BACK) + + o Using 1D or 3D textures + + o Using texture borders + 10.4.4 Known Problems If you experience stability problems you may try setting the UseCCEFor2D @@ -1000,10 +1034,9 @@ Performance will be degraded, of course. 10.5 ATI Radeon -10.5.1 Dependencies +10.5.1 Requirements -A Linux kernel with AGP GART support (such as the 2.4.x test kernels) is -needed. +A kernel with AGP GART support (such as Linux 2.4.x) is needed. 10.5.2 Configuration @@ -1044,7 +1077,7 @@ ules/dri/radeon_dri.so. This will be automatically loaded by libGL.so. You may also set your screen depth to 32 for 32bpp mode. -10.5.3 Performance +10.5.3 Performance and Features While this driver supports many of the features of ATI Radeon cards, we do not yet fully support the card's TCL features. This work is progressing, but @@ -1053,9 +1086,38 @@ is not yet ready. The AGP mode may be set to 1, 2, or 4. One is used by default. Higher AGP speeds may result in unreliable performance depending on your motherboard. +The following OpenGL features are implemented in software and will be slow: + + o Blend subtract, blend min/max and blend logicops + + o Stencil and accumulation operations + + o 1D and 3D textures + + o Texture borders + +The GL_EXT_texture_env_combine, GL_EXT_texture_env_add and GL_EXT_tex- +ture_env_dot3 extensions are supported (or will be soon supported in the new +driver based on Mesa 3.5). + +We hope to implement support for the following features in the future: + + o Vertex transformation, clipping and lighting (TCL) + + o Hardware stencil buffer + + o Cube map textures + + o 3D textures + + o Three texture units + 10.5.4 Known Problems -None. +Certain (early?) revisions of the AMD Irongate chipset have AGPGART problems +which effect Radeon, and other graphics cards. The card may work unreliably, +or not work at all. If the DRM kernel module is not loaded, the 2D Xserver +may work. There's hope that this can be fixed in the future. 10.6 3DLabs Oxygen GMX 2000 @@ -1069,8 +1131,8 @@ oped or supported. The following OpenGL features are not supported at this time: overlays, stereo, hardware-accelerated indirect rendering. -OpenGL-like functionality is provided with the Mesa library. XFree86 4.0.2 -uses Mesa 3.4. Subsequent releases of XFree86 will use newer versions of +OpenGL-like functionality is provided with the Mesa library. XFree86 4.1.0 +uses Mesa 3.4.2. Subsequent releases of XFree86 will use newer versions of Mesa. When newer versions of Mesa are available, the 3D drivers can be updated without reinstalling XFree86 or libGL.so. @@ -1144,8 +1206,7 @@ has already been reported and perhaps fixed. 12.1 Software A collection of useful configuration files, libraries, headers, utilities and -demo programs is available from http://dri.source- -forge.net/resources/resources.html +demo programs is available from http://dri.sourceforge.net/res.phtml 12.2 Documentation @@ -1170,7 +1231,7 @@ forge.net/resources/resources.html o In the future there may be IHV and Linux vendor support resources for the DRI. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml,v 1.21 2001/04/10 16:07:58 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml,v 1.24 2001/05/19 00:42:22 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DRI,v 1.15 2001/04/10 16:44:31 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DRI,v 1.16.2.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp b/xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp index c37706cf9..ae1f31e12 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp +++ b/xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp @@ -2,7 +2,7 @@ VA Linux Systems, Inc. Professional Services - Graphics. - 15 March 2001 + 21 April 2001 1. Preamble @@ -137,7 +137,8 @@ Here are the basic steps for kernel setup. o Go to Character devices o Disable Direct Rendering Manager (XFree86 DRI support) since we'll - use the DRI module from the XFree86/DRI tree. + use the DRI code from the XFree86/DRI tree and will compile it + there. o Go to /dev/agpgart (AGP Support) (EXPERIMENTAL) (NEW) @@ -424,7 +425,7 @@ headers. This can be fixed by explicitly setting the value of TREE. If the path to your kernel source is /usr/src/linux-2.4.x, cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel - make TREE=/usr/src/linux-2.4 + make TREE=/usr/src/linux-2.4.x/include or alternatively, edit Makefile to include this change. @@ -437,7 +438,7 @@ first. The DRI kernel modules are in ~/DRI-CVS/build/xc/pro- grams/Xserver/hw/xfree86/os-support/linux/drm/kernel/. -To load the appropriate DRI module in your running kernel you can either use +To load the appropriate DRM module in your running kernel you can either use ismod and restart your X server or copy the kernel module to /lib/mod- ules/2.4.x/kernel/drivers/char/drm/ then run depmod and restart your X server. @@ -445,6 +446,8 @@ server. Make sure you first unload any older DRI kernel modules that might be already loaded. +Note that some DRM modules require that the agpgart module be loaded first. + 9. Normal Installation and Configuration Most users will want to install the new X server and use it instead of the @@ -595,7 +598,7 @@ At this point your X server should be up and running with hardware-acceler- ated direct rendering. Please read the DRI User Guide for information about trouble shooting and how to use the DRI-enabled X server for 3D applications. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml,v 1.13 2001/04/05 19:29:42 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml,v 1.14 2001/05/02 15:06:08 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp,v 3.9 2001/04/10 16:44:31 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.DRIcomp,v 3.10.2.1 2001/06/01 18:26:43 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.Darwin b/xc/programs/Xserver/hw/xfree86/doc/README.Darwin index c3d118175..ad3950e04 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.Darwin +++ b/xc/programs/Xserver/hw/xfree86/doc/README.Darwin @@ -2,7 +2,7 @@ Torrey T. Lyons - 11 December 2000 + 25 May 2001 1. Introduction @@ -14,19 +14,31 @@ working on modifications to the Darwin X server, please let me know. 2. Hardware Support and Configuration -The Darwin port of XFree86 uses the IOKit for device driver loading and dis- -covery, rather than the XFree86 module loader. Because of this, the XFree86 -configuration file is not used on Darwin systems. The descriptions found -elsewhere of devices supported by XFree86 for other operating systems also do -not apply. - -XFree86 for Darwin will work with any video card that you have an IOKit -driver for. If you are running Mac OS X, this typically means any card that -has been shipped by Apple. If a card works for you with the Mac OS X GUI, it -will work on the same machine with XFree86. If you have a pure Darwin instal- -lation, your hardware support may be somewhat limited because Apple does not -include all its hardware drivers with Darwin. IOKit drivers are typically -found in /System/Library/Extensions/ or /Library/Extensions/. +XFree86 can be run either from the console or side by side with Mac OS X's +Aqua desktop in a full screen mode. In full screen mode with Aqua, when the X +window system is active, it takes over the entire screen. You can switch back +to the Mac OS X desktop by holding down Command-Option-A. This key combina- +tion can be changed in the user preferences. From the Mac OS X desktop, just +click on the XDarwin icon in the floating switch window to switch back to the +X window system. You can change this behavior in the user preferences so +that clicking on the XDarwin icon in the Dock switches as well. The full +screen cooperative mode with Aqua is known as Quartz mode, named after the +Quartz 2D compositing engine used by Aqua. + +From the console, the Darwin port of XFree86 uses the IOKit for device driver +loading and discovery, rather than the XFree86 module loader. Because of +this, the XFree86 configuration file is not used on Darwin or Mac OS X sys- +tems. The descriptions found elsewhere of devices supported by XFree86 for +other operating systems also do not apply. Running XFree86 from the text +console is known as IOKit mode. + +XFree86 for Darwin or Mac OS X will work with any video card that you have an +IOKit driver for. If you are running Mac OS X, this typically means any card +that has been shipped by Apple. If a card works for you with the Mac OS X +GUI, it will work on the same machine with XFree86. If you have a pure Darwin +installation, you may need to download additional third-party drivers from +Apple's Darwin site. IOKit drivers are typically installed in /Sys- +tem/Library/Extensions/ or /Library/Extensions/. Multi-button and scroll wheel mouse support works well with all USB mice that I have tested. I have done no testing with serial mice. @@ -35,30 +47,20 @@ I have tested. I have done no testing with serial mice. Following are instructions for building and running your own copy of XFree86. The procedure for getting your X server up and running on Darwin and Mac OS X -are very similar, but it is actually somewhat more difficult on Mac OS X. -Where there are differences I have noted them below. Both Mac OS X Develop- -ers' Preview 4 and Mac OS X Public Beta are covered. Note that to build -XFree86 for yourself on Mac OS X Beta, you will need to have the Developers' -Tools. If you did not receive these as a member of ADC, they are available -for download from the Apple Developer Connection. - -If you want to save some time, you can use the precompiled binaries provided -by the XFree86 server at <URL:ftp://ftp.xfree86.org/pub/XFree86/4.0.2/bina- -ries/Darwin/>. Follow the instructions in the Install document to install -it. - -This will create two new directory trees, /usr/X11R6 and /private/etc/X11. If -you have the developers' tools, you may have to run ranlib on all the -libraries in /usr/X11R6/lib/* before trying to build other X applications. - -If you get the precompiled binaries you can skip ahead to the section on run- -ning X windows (section 4., page 1) +are very similar. Where there are differences I have noted them below. Note +that to build XFree86 for yourself on Mac OS X, you will need to install the +Developers' Tools. -On the other hand, if you want to build things yourself from scratch, follow -the directions below. +If you don't feel the need to live on the cutting edge, you can save some +time and effort by using the precompiled binaries available on the XFree86 +FTP server at <URL:ftp://ftp.xfree86.org/pub/XFree86/4.1.0/binaries/Darwin/>. +Follow the instructions in the Install document to install it. This will cre- +ate two new directory trees, /usr/X11R6 and /etc/X11 For Mac OS X Quartz sup- +port, download the optional Xquartz.tgz tarball. -If you want to recompile the X server on Mac OS X, you will have to make the -header files as described below (section 3.2, page 1). +If you get the precompiled binaries you can skip ahead to the section on run- +ning the X window system (section 4., page 1) On the other hand, if you want +to build things yourself from scratch, follow the directions below. 3.1 Get the Code @@ -68,8 +70,8 @@ project. o Setup CVS: Both Darwin and Mac OS X include CVS (Concurrent Versions System), which is an easy way to download and keep up to date with open source code released by XFree86 and others. You do have to setup CVS - properly, however, to tell it where to look. Follow the instructions - here on how to do this either via ssh or via the cvs pserver. + properly, however, to tell it where to look. Follow the XFree86 instruc- + tions on how to do this either via ssh or via the cvs pserver. o Now make a directory in some convenient place which will serve as your top level directory for you open source development efforts. I am going @@ -83,22 +85,7 @@ project. Wait for all the files to complete downloading. -3.2 Make Header Files for Mac OS X - -These next steps are not necessary if you are building XFree86 on Darwin. Mac -OS X Beta or DP4 does not include many of the 'in-progress' header files that -are needed to successfully build XFree86. The general philosophy is that at -any given time, Mac OS X will include only headers files that are 'ready for -prime time' while Darwin will include a snapshot of Apple's current efforts. -So if you have access to a Darwin system, I would suggest using this instead -of Mac OS X to build XFree86. If you don't, read the appropriate page below -for an outline of what you need to do: - - o Mac OS X Public Beta (section 6.1, page 1) - - o Mac OS X Developers' Preview 4 (section 6.2, page 1) - -3.3 Build XFree86 +3.2 Build XFree86 Once you have everything ready it is easy to build and install XFree86. From the command line: @@ -108,61 +95,69 @@ the command line: (wait for several hours) - su root - make install >& install.log - make install.man >& man.log + sudo make install >& install.log + sudo make install.man >& man.log -4. Run X Windows +4. Run the X Window System -You will want to add the X windows executables to your path. Your path is the +You will want to add the X window executables to your path. Your path is the list of directories to be searched when you type a command. You will also want to add the man pages from XFree86 to the list of pages to be searched when you are looking for documentation. The way to do this depends on the shell you are using. With tcsh or csh add the following two lines to a file -in your home directory called .cshrc (create this file if you don't have one -yet): +named ~/Library/init/tcsh/path: (You may need to create this file and direc- +tory path if it does not exist already.) - setenv MANPATH "${MANPATH}:/usr/X11R6/man:/usr/local/man" setenv PATH "${PATH}:/usr/X11R6/bin" - -Now type ``source ~/.cshrc;rehash'' to get these changes to take effect. On -future logins, this file will be executed automatically. - -You are now ready to go. On Mac OS X, you have to do a few extra steps each -time you want to run X windows. You can't run XFree86 with CoreGraphics run- -ning since they both want to control the screen. So for Mac OS X you first -need to logout. Then for Mac OS X DP4, from the login window type ``console'' -as the user name and push login. For Mac OS X Beta, type ``>console'' as the -user name. This should shutdown CoreGraphics and bring you up with a text -console. Login again. - -Now from the text console you can start X Windows in either Darwin or Mac OS -X by typing ``startx''. After a brief wait at least one terminal window -should pop up for you. So far it probably isn't very impressive as you might -not even have a window manager running to allow you to move windows around. - -When you are ready to quit X windows type ``exit'' in the main terminal win- -dow or quit with the window manager if you have one running. Unfortunately -the X server won't shutdown correctly and you will get an apparently frozen -screen with only a spinning beachball cursor on it. Nothing you type shows up -on the screen, but in fact your keystrokes are being received by the console. -Type ``logout'' to return to normalcy after a brief delay. With Darwin this -should put you back at the text console login prompt. With Mac OS X, Core- -Graphics will restart and you should be given a login window. + setenv MANPATH "${MANPATH}:/usr/X11R6/man" + +The next time you login or open a Terminal window, this file will be executed +automatically. + +You are now ready to go. On Mac OS X, you can run XFree86 from the text con- +sole or in full screen mode with Aqua. To get to the text console in Mac OS X +you need to logout and type ``>console'' as the user name. This will shutdown +Core Graphics and bring up the console login prompt. Login again as your +user. + +From the text console you can start the X Window System by typing ``startx''. +After a brief wait at least one terminal window should pop up for you. So +far it probably isn't very impressive as you might not even have a window +manager running to allow you to move windows around. + +When you are ready to quit XFree86 type ``exit'' in the main terminal window +or quit with the window manager if you have one running. Unfortunately the X +server won't shutdown correctly and you will get an apparently frozen screen +with only a spinning beachball cursor on it. Nothing you type shows up on the +screen, but in fact your keystrokes are being received by the console. Type +``logout'' to return to normalcy after a brief delay. With Darwin this should +put you back at the text console login prompt. With Mac OS X, Core Graphics +will restart and you should be given a login window. + +To start XFree86 in Quartz mode you can launch the XDarwin application in the +/Applications folder, or from the command line type ``startx -- -quartz''. +When the X window system is active, it takes over the entire screen. You can +switch back to the Mac OS X desktop by holding down Command-Option-A. This +key combination can be changed in the user preferences. From the Mac OS X +desktop, just click on the XDarwin icon in the floating switch window to +switch back to the X window system. You can change this behavior in the user +preferences so that clicking on the XDarwin icon in the Dock switches as +well. Customize X Windows -X windows is very customizable and you will certainly want to change some -things. There is a lot you can do to control how your windows look, how the -windows are moved, resized, etc. You will likely want to get a better window -manager than twm, which is included with XFree86. The .xinitrc file in your -home directory controls what programs are run when you start X windows. You -can find a sample .xinitrc file in /private/etc/X11/xinit/xinitrc. +The X window system is very customizable and you will certainly want to +change some things. There is a lot you can do to control how your windows +look, how the windows are moved, resized, etc. You will likely want to get a +better window manager than twm, which is included with XFree86. The .xinitrc +file in your home directory controls what programs are run when you start the +X window system. You can find a sample .xinitrc file in /etc/X11/xinit/xini- +trc. -There are several window managers that have been ported to Darwin. The best -collection of window managers and other X windows applications is at Dar- -winfo's ports page. Another good place to look for Darwin ports in general is -at Stepwise's Softrak site. +There are several window managers that have been ported to Darwin. The best +collection of window managers and other X window clients is at Darwinfo's +ports page. Another good place to look for Darwin ports in general is at +Stepwise's Softrak site. Good luck! @@ -173,176 +168,20 @@ know if you are interested in working on any of these issues. Things that are broken: - o The bell is broken. + o The bell does not work in IOKit mode. - o Server shutdown problem: After quitting the X server the colored beach- - ball cursor reappears, but the screen never returns to the console dis- - play. The console is accepting input however, so typing ``logout'' will - return you to the login prompt. + o Server shutdown problem: After quitting the X server in IOKit mode, the + colored beachball cursor reappears, but the screen never returns to the + console display. The console is accepting input however, so typing + ``logout'' will return you to the login prompt. o Only one display is currently supported. - o Screen saver not supported. - - o Key repeat rate can not be adjusted. - -Things I am working on: - - o Allowing rootless use on Mac OS X - - o Correct wake from sleep behavior - -6. Appendix - -6.1 Installing IOKit Header files on Mac OS X Beta - -Here is what you need to do to be able to build XFree86 (or other clients of -IOGraphics services) on Mac OS X Public Beta. - - 1. You need to install some more build tools that aren't included in Mac - OS X Beta, but are included in Darwin. These are needed for the next - step. Go to your development directory and type: - - cvs checkout bootstrap_cmds - cd bootstrap_cmds - make - - Now su to root and do a ``make install'' from the bootstrap_cmds direc- - tory. - - 2. The IOKit framework included with Mac OS X Beta is a little on the - wimpy side, even after installing the Developer Tools. You'll need to - rebuild it, but to do so safely we'll take advantage of the cool direc- - tory structure of Mac OS X and put the new version in /Library/Frame- - works/. This will override the version in /System/Library/Frameworks/. - Or at least, that's where you should put it using the new Mac OS X Beta - file structure, but in fact the compiler doesn't know this and still - looks in /Local/Library/Frameworks. (I have already filed a developer's - bug report on this.) To start we make a copy of the original. Login as - root and do the following: - - cd /Library - mkdir -p Frameworks - cp -R /System/Library/Frameworks/IOKit.framework Frameworks/IOKit.framework - cd / - mkdir -p Local - ln -s /Library /Local/Library - - 3. Now you need to get a full version of the IOKit framework from the Dar- - win repository. This comes as part of the kernel. So, in your develop- - ment directory again: - - cvs checkout xnu - cd xnu - source SETUP/setup.csh - make exporthdrs - make install - - The "make install" will start by assembling all the headers you need, - but then will proceed to build a new kernel. You can Control-C out of - the build once it starts compiling things if you want. Otherwise, just - be patient. - - 4. You also need to get the IOKitUser project, which contains the user - interface to the IOKit, and merge it into the IOKit framework. From - your development directory type: - - cvs checkout IOKitUser - - Then you need to change the Makefile so it builds on top of the new - IOKit framework you are building. Change to the IOKitUser project - directory and edit the Makefile. Change the following line: - - NEXTSTEP_BUILD_OUTPUT_DIR = /$(USER)/build/$(NAME) - - to: - - NEXTSTEP_BUILD_OUTPUT_DIR = <your xnudir>/BUILD/dst/System/Library/Frameworks - - Now, run ``make'' while in the IOKitUser directory. It will likely not - finish building since the IOKitUser project relies on some stuff that - Apple hasn't really made public yet, but it should finish populating - the new IOKit framework with headers and start compiling. (Strangely - enough, the headers installed in your new IOKit framework don't contain - the real header files. They are just single line files with an #import - of the file in your IOKitUser project. This works fine as long as you - don't ever delete or move your IOKitUser project. I imagine that using - ``make install'' would fix this up, but you can't do this as long as - the project doesn't build correctly. So for now you can either move the - header files by hand, or make sure you leave your IOKitUser project in - place.) - - 5. Now put the new IOKit headers into our local copy. Change to the xnu - project directory and do the following as root: - - cd BUILD/dst/System/Library/Frameworks/ - cp -R IOKit.framework/Versions/A/Headers/* \ - /Library/Frameworks/IOKit.framework/Versions/A/Headers - - 6. The System framework needs touching up a bit too. You need to copy the - libkern header files from the new System.framework. As root, go to the - xnu project directory and type: (Of course you could make a local copy - of the System framework in /Library/Frameworks/, but the additions to - the System framework are small.) - - cd BUILD/dst/System/Library/Frameworks/System.framework/Versions/B/Headers - cp -R libkern /System/Library/Frameworks/System.framework/Headers/libkern - -6.2 Installing IOKit Header files on Mac OS X DP4 - -Here is an outline of what you need to do to be able to build XFree86 (or -other clients of IOGraphics services) on Mac OS X Developers' Preview 4. - - 1. Checkout, build, and install bootstrap_cmds from the CVS repository. - - 2. Checkout xnu from the CVS repository. Go to sandbox/xnu and do the fol- - lowing: - - source SETUP/setup.csh - make exporthdrs - - 3. su to root and do the following: - - mkdir -p /Local/Library/Frameworks - cp -R /System/Library/Frameworks/IOKit.framework /Local/Library/Frameworks - - This will create a new local version of the IOKit framework that will - override the System version without changing the original. - - 4. You now want to merge the IOKit headers from the xnu project into your - local IOKit framework. I did this fairly tediously by hand, but I would - suggest something like: - - cp -R sandbox/xnu/BUILD/dst/System/Library/Frameworks/IOKit.framework/Versions/A/Headers \ - /Local/Library/Frameworks/IOKit.framework/Versions/A - - The only problem with this is that there are a few stub header files - included that are just a single line with an #import to the appropriate - place in the xnu source on your disk. This is fine as long as you don't - move your xnu project. If you do, you can copy the original file to - replace the stub. There is probably an easier way to automatically - build a clean version of the IOKit framework, but I didn't find it. - (Let me know if you do.) - - 5. There are just a few more files you need in the IOKit framework. Check- - out the IO project from CVS. Get the necessary header files from there - and put them in your new local IOKit framework. You'll get errors when - you try to build XFree86 from which you can tell which files are - needed. I also needed to make the following patch to IOLLEvent.h. Your - mileage may vary. - - 47c47 - < #include <Kernel/libkern/OSTypes.h> - --- - > #include <libkern/OSTypes.h> + o The display mode can not be changed once the X server has started. - 6. You'll also need a few extra CoreFoundation header files. Checkout - CoreFoundation. You can make a new local version of the CoreFoundation - framework as above, or just add to the existing one. The files you need - are CFMachPort.h and CFMessagePort.h in the RunLoop.subproj and CFStor- - age.h in Collections.subproj. + o A screen saver is not supported. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.4 2000/12/12 18:54:29 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.4.4.2 2001/06/02 04:44:37 torrey Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.Darwin,v 1.3 2000/12/12 19:04:02 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.Darwin,v 1.3.4.4 2001/06/02 16:02:08 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.I128 b/xc/programs/Xserver/hw/xfree86/doc/README.I128 index b49c54b22..74d525713 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.I128 +++ b/xc/programs/Xserver/hw/xfree86/doc/README.I128 @@ -100,4 +100,4 @@ and special help from: Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/I128.sgml,v 1.6 2000/12/13 01:55:47 robin Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.I128,v 1.10 2000/12/14 17:12:00 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.I128,v 1.10.4.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.LynxOS b/xc/programs/Xserver/hw/xfree86/doc/README.LynxOS index 05e190d43..f352a081a 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.LynxOS +++ b/xc/programs/Xserver/hw/xfree86/doc/README.LynxOS @@ -1,4 +1,4 @@ - README for XFree86 4.0.2 on LynxOS + README for XFree86 4.1.0 on LynxOS Thomas Mueller @@ -13,19 +13,19 @@ ments as well as many bug fixes. See the Copyright Notice. -The sources for XFree86 4.0.2 are available by anonymous ftp from: +The sources for XFree86 4.1.0 are available by anonymous ftp from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2 +ftp://ftp.XFree86.org/pub/XFree86/4.1.0 Binaries of XFree86 for LynxOS x86 are available from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2/binaries/LynxOS +ftp://ftp.XFree86.org/pub/XFree86/4.1.0/binaries/LynxOS A list of mirror sites is provided by ftp://ftp.XFree86.org/pub/XFree86/MIR- RORS The binaries on the FTP site were built on the latest released LynxOS version -at the time XFree86 4.0.2 was released. In this case it is `LynxOS x86 +at the time XFree86 4.1.0 was released. In this case it is `LynxOS x86 3.0.1'. Because of changes made to the object format they don't run on LynxOS versions earlier than 3.0.0. @@ -37,7 +37,7 @@ this OS release was not available long enough for serious testing `LynxOS 3.1.0' support has to be considered to be in `alpha state'. Initial tests were performed on LynxOS x86 only! -XFree86 4.0.2 supports LynxOS on the x86 and on the PowerPC platform. X +XFree86 4.1.0 supports LynxOS on the x86 and on the PowerPC platform. X servers are currently available only on the x86 platform. The X server may work with some PowerPC platforms supported by LynxOS though this has not (yet) been thoroughly tested. @@ -163,7 +163,7 @@ to 3.5 X Server debug diagnostics output and other VT peculiarities Output made by the XFree86 X on its stdout or stderr will be lost after the -server switches to graphics mode. The XFree86 4.0.2 server stores its output +server switches to graphics mode. The XFree86 4.1.0 server stores its output in /usr/adm/XFree86.n.log (where n is the screen number). When the X server is running output made to other consoles will be lost. @@ -266,4 +266,4 @@ duplicate entries: Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/LynxOS.sgml,v 3.20 2000/06/17 00:27:32 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.LynxOS,v 3.28 2000/12/01 19:47:46 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.LynxOS,v 3.28.4.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.NetBSD b/xc/programs/Xserver/hw/xfree86/doc/README.NetBSD index da9b9dafc..4a8d5709f 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.NetBSD +++ b/xc/programs/Xserver/hw/xfree86/doc/README.NetBSD @@ -1,4 +1,4 @@ - README for XFree86 4.0.2 on NetBSD + README for XFree86 4.1.0 on NetBSD Rich Murphey, David Dawes, Marc Wandschneider, Mark Weaver, Matthieu Herrb @@ -14,10 +14,10 @@ See the Copyright Notice. The sources for XFree86 are available by anonymous ftp from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2 +ftp://ftp.XFree86.org/pub/XFree86/4.1.0 Binaries for NetBSD 1.4 and later are available from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2/binaries/NetBSD +ftp://ftp.XFree86.org/pub/XFree86/4.1.0/binaries/NetBSD A list of mirror sites is provided by http://www.xfree86.org/MIRRORS.shtml @@ -33,8 +33,6 @@ if you have comments or suggestions about this file and we'll revise it. 3. New OS dependent features -See the Release Notes for non-OS dependent new features in XFree86 4.0.2. - 3.1 New OS dependent features in 4.0.2 o A fix for libXmu OS detection which was broken since unix isn't defined @@ -101,7 +99,7 @@ the xvidtune utility. 5.1 About mouse configuration -XFree86 4.0.2 has support for the mouse driver included in the wscons console +XFree86 4.1.0 has support for the mouse driver included in the wscons console driver introduced by NetBSD 1.4. Specify ``wsmouse'' as the protocol and ``/dev/wsmouse0'' as the device in /etc/X11/XF86Config if you're using NetBSD 1.4 or later with a PS/2 mouse. @@ -219,14 +217,14 @@ By default NetBSD include the BSD 4.4 kernel security feature that disable access to the /dev/mem device when in multi-users mode. But XFree86 servers can take advantage (or require) linear access to the display memory. -Most XFree86 4.0.2 card drivers require linear memory access. There are two +Most XFree86 4.1.0 card drivers require linear memory access. There are two ways to allow XFree86 to access linear memory: The first way is to disable the kernel security feature by adding ``option INSECURE'' in the kernel configuration file and build a new kernel. The second way is to install the aperture driver, included in source form in -xc/programs/Xserver/hw/xfree86/etc/apNetBSD.shar in the XFree86 4.0.2 source +xc/programs/Xserver/hw/xfree86/etc/apNetBSD.shar in the XFree86 4.1.0 source distribution. Unpack it in a new directory of your choice by running: sh apNetBSD.shar @@ -370,7 +368,7 @@ Many thanks to all people who contributed to make XFree86 work on *BSD, in particular, David Dawes, Pace Willison, Amancio Hasty, Christoph Robitschko, Nate Williams, Rod Grimes, Jack Velte and Michael Smith. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml,v 3.60 2001/03/04 09:47:34 herrb Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml,v 3.60.2.1 2001/06/01 18:09:48 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.NetBSD,v 3.76 2001/03/04 09:48:47 herrb Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.NetBSD,v 3.76.2.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD b/xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD index bc01998fe..843b8bde1 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD +++ b/xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD @@ -1,4 +1,4 @@ - README for XFree86 4.0.2 on OpenBSD + README for XFree86 4.1.0 on OpenBSD Matthieu Herrb @@ -12,13 +12,13 @@ ing systems on Intel and other platforms. See the Copyright Notice. -The sources for XFree86 4.0.2 are available by anonymous ftp from: +The sources for XFree86 4.1.0 are available by anonymous ftp from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2 +ftp://ftp.XFree86.org/pub/XFree86/4.1.0 Binaries for OpenBSD/i386 2.8 and later are available from: -ftp://ftp.XFree86.org/pub/XFree86/4.0.2/binaries/OpenBSD +ftp://ftp.XFree86.org/pub/XFree86/4.1.0/binaries/OpenBSD A list of mirror sites is provided by http://www.xfree86.org/MIRRORS.shtml @@ -32,7 +32,7 @@ if you have comments or suggestions about this file and we'll revise it. 3. New OS dependent features -See the Release Notes for non-OS dependent new features in XFree86 4.0.2. +See the Release Notes for non-OS dependent new features in XFree86 4.1.0. 3.1 New OS dependent features in 4.0.3 @@ -122,7 +122,7 @@ the xvidtune utility. 5.1 About mouse configuration -XFree86 4.0.2 has support for the mouse driver included in the new wscons +XFree86 4.1.0 has support for the mouse driver included in the new wscons console driver introduced by OpenBSD-current after 2.8. Specify ``wsmouse'' as the protocol and ``/dev/wsmouse0'' as the device in /etc/X11/XF86Config if you're using OpenBSD-current with a PS/2 mouse. @@ -335,4 +335,4 @@ Nate Williams, Rod Grimes, Jack Velte and Michael Smith. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/OpenBSD.sgml,v 1.17 2001/04/05 19:29:43 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD,v 1.22 2001/04/10 16:44:31 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.OpenBSD,v 1.22.2.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.SiS b/xc/programs/Xserver/hw/xfree86/doc/README.SiS index 339ee77c9..cf5af1b14 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.SiS +++ b/xc/programs/Xserver/hw/xfree86/doc/README.SiS @@ -113,4 +113,4 @@ Document based on 3.3 version written by Xavier Ducoin. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/SiS.sgml,v 3.7 2000/03/06 22:59:24 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.SiS,v 3.16 2000/12/01 19:47:48 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.SiS,v 3.16.4.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.apm b/xc/programs/Xserver/hw/xfree86/doc/README.apm index 7c821ad7d..37ad919ea 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.apm +++ b/xc/programs/Xserver/hw/xfree86/doc/README.apm @@ -111,4 +111,4 @@ be possible to add support for the 3210 chipset if someone needs it. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/apm.sgml,v 1.3 2000/03/08 05:38:43 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.apm,v 1.8 2000/12/01 19:47:48 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.apm,v 1.8.4.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.ati b/xc/programs/Xserver/hw/xfree86/doc/README.ati index af39d20db..16d0d5add 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.ati +++ b/xc/programs/Xserver/hw/xfree86/doc/README.ati @@ -694,4 +694,4 @@ Intel architectures. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/ati.sgml,v 3.37 2001/04/16 15:02:08 tsi Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.ati,v 3.56 2001/04/16 15:06:49 tsi Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.ati,v 3.56.2.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.chips b/xc/programs/Xserver/hw/xfree86/doc/README.chips index 23d8180c4..b5043af1a 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.chips +++ b/xc/programs/Xserver/hw/xfree86/doc/README.chips @@ -3,11 +3,11 @@ David Bateman (<dbateman@club-internet.fr>), Egbert Eich (<eich@xfree86.org>) - 14th June 2000 + 1st January 2001 1. Introduction -With the release of XFree86 version 4.0.2, the Chips and Technologies driver +With the release of XFree86 version 4.1.0, the Chips and Technologies driver has been extensively rewritten and contains many new features. This driver must be considered work in progress, and those users wanting stability are encouraged to use the older XFree86 3.3.x versions. However this version of @@ -260,14 +260,6 @@ Screen, Monitor, Device. grammable clock makes this option obsolete and so it's use isn't recommended. It is completely ignored for HiQV chipsets. - Option "UseVclk1" - The HiQV series of chips have three programmable clocks. The - first two are usually loaded with 25.175 and 28.322MHz for VGA - backward compatibility, and the third is used as a fully pro- - grammable clock. On at least one system (the Inside 686 LCD/S - single board computer) the third clock is unusable. This option - forces the use of VClk1 as the programmable clock. - TextClockFreq 25.175 Except for the HiQV chipsets, it is impossible for the server to read the value of the currently used frequency for the text con- @@ -291,18 +283,29 @@ Screen, Monitor, Device. or 32bpp LCD panel clocks, where the options above set the clocks to 65MHz. + Option "CRTClkIndx" "2" + Option "FPClkIndx" "1"" The HiQV series of chips have three pro- + grammable clocks. The first two are usually loaded with 25.175 + and 28.322MHz for VGA backward compatibility, and the third is + used as a fully programmable clock. On at least one system (the + Inside 686 LCD/S single board computer) the third clock is unus- + able. These options can be used to force a particular clock index + to be used + Option "MMIO" This has a different effect depending on the hardware on which it is used. For the 6554x machines MMIO is only used to talk to the BitBLT engine and is only usable with PCI buses. It is enabled by default for 65545 machines since the blitter can not be used otherwise. The HiQV series of chipsets must use MMIO with - their BitBLT engines, and so this is enabled by default. However - the 690xx chipsets can use MMIO for all communications with the + their BitBLT engines, and so this is enabled by default. + + Option "FullMMIO" + The 690xx chipsets can use MMIO for all communications with the video processor. So using this option on a 690xx chipset forces them to use MMIO for all communications. This only makes sense when the 690xx is on a PCI bus so that normal PIO can be dis- - abled. (WARNING!! 690xx MMIO is untested) + abled. Option "SuspendHack" This option sets the centering and stretching to the BIOS default @@ -409,6 +412,20 @@ Screen, Monitor, Device. 255 for 8bit depth, 0 to 32,767 for 15bit depth, etc. This option might be used if the default video overlay key causes problems. + Option "DualRefresh" + The 69030 chipset has independent display channels, that can be + configured to support independent refresh rates on the flat panel + and on the CRT. The default behaviour is to have both the flat + panel and the CRT use the same display channel and thus the same + refresh rate. This option forces the two display channels to be + used, giving independent refresh rates. + + Option "Crt2Memory" "2048" + The ct69030 supports dual-head display. By default the two dis- + play share equally the available memory. This option forces the + second display to take a particular amount of memory. Please read + the section below about dual-head display. + Option "XaaNoScreenToScreenCopy", Option "XaaNoSolidFillRect", Option "XaaNoSolidHorVertLine", Option "XaaNoMono8x8PatternFillRect", Option "XaaNoColor8x8Pat- @@ -499,6 +516,13 @@ you'll needed to considered several points after a suspend/resume or LCD/CRT switch. For a complete discus- sion on the dot clock limitations, see the next section. + * Dual-head display + Dual-head display has two effects on the modelines. Firstly, the + memory requirements of both heads must fit in the available mem- + ory. Secondly, the memory bandwidth of the video processor is + shared between the two heads. Hence the maximum dot-clock might + need to be limited. + The driver is capable of driving both a CRT and a flat panel display. In fact the timing for the flat panel are dependent on the specification of the panel itself and are independent of the particular mode chosen. For this reason it @@ -530,7 +554,97 @@ The NEC Versa 4080 just needs the "FixPanelSize" option. To the best of my knowledge no machine with a HiQV needs the "UseModeline" or "FixPanelSize" options. -5. The Full Story on Clock Limitations +5. Dual Display Channel + +XFree86 releases later than 4.1.0 support dual-channel display on the +ct69030. This support can be used to give a single display image on two +screen with different refresh rates, or entirely different images on the two +displays. + +Dual refresh rate display can be selected with the "DualRefresh" option +described above. However to use the dual-head support is slightly more com- +plex. Firstly, the ct69030 chipset must be installed on a PCI bus. This is a +driver limitation that might be relaxed in the future. In addition the +device, screen and layout sections of the "XF86Config" must be correctly con- +figured. A sample of an incomplete "XF86Config" is given below + + Section "Device" + Identifier "Chips and Technologies - Pipe A" + Driver "chips" + BusID "PCI:0:20:0" + Screen 0 + EndSection + + Section "Device" + Identifier "Chips and Technologies - Pipe B" + Driver "chips" + BusID "PCI:0:20:0" + Screen 1 + EndSection + + Section "Screen" + Identifier "Screen 0" + Device "Chips and Technologies - Pipe A" + Monitor "generic LCD" + + SubSection "Display" + Depth 16 + Modes "1024x768" + EndSubsection + EndSection + + Section "Screen" + Identifier "Screen 1" + Device "Chips and Technologies - Pipe B" + Monitor "generic CRT" + + SubSection "Display" + Depth 16 + Modes "1024x768" + EndSubsection + EndSection + + Section "ServerLayout" + Identifier "Main Layout" + Screen "Screen 0" + Screen "Screen 1" RightOf "Screen 0" + InputDevice "Mouse1" "CorePointer" + InputDevice "Keyboard1" "CoreKeyboard" + EndSection + +The device section must include the PCI BusID. This can be found from the log +file of a working single-head installation. For instance, the line + + (--) PCI:*(0:20:0) C&T 69030 rev 97, Mem @ 0xed000000/24 + +appears for the case above. Additionally, the "Screen" option must appear in +the device section. It should be noted that if a flat panel is used, this it +must be allocated to "Screen 0". + +The server can then be started with the "+xinerama" option as follows + + startx -- +xinerama + +For more information, read the Xinerama documentation. + +It should be noted that the dual channel display options of the 69030 require +the use of additional memory bandwidth, as each display channel independently +accesses the video memory. For this reason, the maximum colour depth and res- +olution that can be supported in a dual channel mode will be reduced compared +to a single display channel mode. However, as the driver does not prevent you +from using a mode that will exceed the memory bandwidth of the 69030, but a +warning like + + (WW) Memory bandwidth requirements exceeded by dual-channel + (WW) mode. Display might be corrupted!!! + +If you see such display corruption, and you have this warning, your choices +are to reduce the refresh rate, colour depth or resolution, or increase the +speed of the memory clock with the the "SetMClk" option described above. Note +that increasing the memory clock also has its own problems as described +above. + +6. The Full Story on Clock Limitations There has been much confusion about exactly what the clock limitations of the Chips and Technologies chipsets are. Hence I hope that this section will @@ -575,17 +689,24 @@ EDO, might not be fast enough to handle this, resulting in drawing errors on the screen. The formula to determine the maximum usable dotclock on the HiQV series of chips is + Max dotclock = min(MaxDClk, 0.70 * 8 * MemoryClk / (BytesPerPixel + + (isDSTN == TRUE ? 1 : 0))) + +if you chips is a 69030 or 69000 or + Max dotclock = min(MaxDClk, 0.70 * 4 * MemoryClk / (BytesPerPixel + (isDSTN == TRUE ? 1 : 0))) -which says that there are two limits on the dotclock. One the overall maxi- -mum, and another due to the available memory bandwidth of the chip. For the -memory bandwidth 4 bytes are transfered every clock cycle (Hence the 4), but -after accounting for the RAS/CAS signaling only about 70% of the bandwidth is -available. The whole thing is divided by the bytes per pixel, plus an extra -byte if you are using a DSTN. The extra byte with DSTN screens is used for -the frame buffering/acceleration in these screens. So for the various Chips -and Technologies chips the maximum specifications are +otherwise. This effectively means that there are two limits on the dotclock. +One the overall maximum, and another due to the available memory bandwidth of +the chip. The 69030 and 69000 have a 64bit memory bus and thus transfer 8 +bytes every clock thus (hence the 8), while the other HiQV chipsets are 32bit +and transfer 4 bytes per clock cycle (hence the 4). However, after accounting +for the RAS/CAS signaling only about 70% of the bandwidth is available. The +whole thing is divided by the bytes per pixel, plus an extra byte if you are +using a DSTN. The extra byte with DSTN screens is used for the frame buffer- +ing/acceleration in these screens. So for the various Chips and Technologies +chips the maximum specifications are Max DClk MHz Max Mem Clk MHz 65550 rev A 3.3v 80 38 @@ -613,8 +734,8 @@ chips are 65554 94.5 77 51.33 77 51.33 38.5 65555 110 77 51.33 77 51.33 38.5 68554 110 77 51.33 77 51.33 38.5 - 69000 135 116.2 77.47 116.2 77.47 58.1 - 69030 170 140 93.33 140 93.33 70 + 69000 135 135 135 135 135 116.2 + 69030 170 170 170 170 170 140 If you exceed the maximum set by the memory clock, you'll get corruption on the screen during graphics operations, as you will be starving the HW BitBlt @@ -632,7 +753,7 @@ ticular mode to work. However use caution with these options, because there is no guarantee that driving the video processor beyond it capabilities won't cause damage. -6. Troubleshooting +7. Troubleshooting The cursor appears as a white box, after switching modes There is a known bug in the H/W cursor, that sometimes causes the @@ -805,13 +926,13 @@ cause damage. My ct69030 machine locks up when starting XFree The ct69030 chipset introduced a new dual channel architecture. - In its current form, XFree can not take advantage of this second - display channel. In fact if the video BIOS on the machine sets - the ct69030 to a dual channel mode by default, XFree will lockup - hard at this point. The solution is to use the BIOS setup to - change to a single display channel mode, ensuring that both the - IOSS and MSS registers are set to a single channel mode. Work is - underway to fix this. + In its current form, XFree86 can not take advantage of this sec- + ond display channel. In fact if the video BIOS on the machine + sets the ct69030 to a dual channel mode by default, XFree86 will + lockup hard at this point. The solution is to use the BIOS setup + to change to a single display channel mode, ensuring that both + the IOSS and MSS registers are set to a single channel mode. Work + is underway to fix this. I can't start X-windows with 16, 24 or 32bpp Firstly, is your machine capable of 16/24/32bpp with the mode @@ -829,7 +950,7 @@ cause damage. startx -- -depth 24 -fbbpp 32 8-8-8 RGB truecolor - however as XFree86 version 4.0.2 allows 32bpp pixmaps to be used + however as XFree86 version 4.1.0 allows 32bpp pixmaps to be used with framebuffers operating in 24bpp, this mode of operating will cost performance for no gain in functionality. @@ -847,7 +968,8 @@ perhaps more stable clock by simply changing the clock value slightly. For example 65.00MHz might be unstable while 65.10MHz is not. So for unexplained problems not addressed above, please try to alter the clock you are using slightly, say in steps of 0.05MHz and see if the problem goes away. Alterna- -tively, using the "UseVClk1" option with HiQV chips might also help. +tively, using the "CRTClkIndx" or "FPClkIndx" option with HiQV chips might +also help. For other screen drawing related problems, try the "NoAccel" or one of the XAA acceleration options discussed above. A useful trick for all laptop com- @@ -860,19 +982,19 @@ tacting the XFree86 team (the current driver maintainer can be reached at <dbateman@club-internet.fr> or <eich@xfree86.org>), or post in the Usenet newsgroup "comp.windows.x.i386unix". -7. Disclaimer +8. Disclaimer XFree86, allows the user to do damage to their hardware with software. Although the authors of this software have tried to prevent this, they dis- claim all responsibility for any damage caused by the software. Use caution, if you think the Xserver is frying your screen, TURN THE COMPUTER OFF!! -8. Acknowledgement +9. Acknowledgement The authors of this software wish to acknowledge the support supplied by Chips and Technologies during the development of this software. -9. Authors +10. Authors Major Contributors (In no particular order) @@ -899,7 +1021,7 @@ Contributors (In no particular order) We also thank the many people on the net who have contributed by reporting bugs and extensively testing this server. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml,v 3.33 2000/12/02 21:52:22 dbateman Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml,v 3.36 2001/05/19 00:35:42 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.chips,v 3.35 2000/12/04 19:47:24 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.chips,v 3.36.2.1 2001/06/01 18:26:44 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.cyrix b/xc/programs/Xserver/hw/xfree86/doc/README.cyrix index 457e3d3f8..f480f4de1 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.cyrix +++ b/xc/programs/Xserver/hw/xfree86/doc/README.cyrix @@ -50,4 +50,4 @@ lowing Cyrix CPUs with integrated graphics: Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/cyrix.sgml,v 1.3 2000/03/08 05:38:43 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.cyrix,v 1.8 2000/12/01 19:47:49 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.cyrix,v 1.8.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.dps b/xc/programs/Xserver/hw/xfree86/doc/README.dps index da1bf9fdc..25b300daf 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.dps +++ b/xc/programs/Xserver/hw/xfree86/doc/README.dps @@ -167,4 +167,4 @@ Developers. 15 April 1993. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/dps.sgml,v 1.1 2001/03/02 02:45:37 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.dps,v 1.2 2001/03/02 17:47:53 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.dps,v 1.2.2.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.fonts b/xc/programs/Xserver/hw/xfree86/doc/README.fonts index 9a3b84b26..fb30c0aa2 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.fonts +++ b/xc/programs/Xserver/hw/xfree86/doc/README.fonts @@ -1013,4 +1013,4 @@ favourite is RFC 373. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/fonts.sgml,v 1.13 2001/03/01 00:37:09 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.fonts,v 1.16 2001/03/02 17:47:53 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.fonts,v 1.16.2.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.i740 b/xc/programs/Xserver/hw/xfree86/doc/README.i740 index bf790fdd8..12bfdf00d 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.i740 +++ b/xc/programs/Xserver/hw/xfree86/doc/README.i740 @@ -178,4 +178,4 @@ http://www.precisioninsight.com Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/i740.sgml,v 1.3 2000/03/04 00:26:30 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.i740,v 1.8 2000/12/01 19:47:49 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.i740,v 1.8.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.i810 b/xc/programs/Xserver/hw/xfree86/doc/README.i810 index cee453c26..38e255969 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.i810 +++ b/xc/programs/Xserver/hw/xfree86/doc/README.i810 @@ -109,4 +109,4 @@ http://www.precisioninsight.com Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/i810.sgml,v 1.3 2001/04/04 01:34:18 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.i810,v 1.6 2001/04/10 16:44:32 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.i810,v 1.6.2.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.isc b/xc/programs/Xserver/hw/xfree86/doc/README.isc index 83627198d..6151da7c9 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.isc +++ b/xc/programs/Xserver/hw/xfree86/doc/README.isc @@ -489,4 +489,4 @@ tribute to this excellent piece of free software. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/isc.sgml,v 3.24 2000/03/06 22:59:25 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.isc,v 3.39 2000/12/01 19:47:50 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.isc,v 3.39.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.mouse b/xc/programs/Xserver/hw/xfree86/doc/README.mouse index 89dadc30f..a3e3527f3 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.mouse +++ b/xc/programs/Xserver/hw/xfree86/doc/README.mouse @@ -6,7 +6,7 @@ 1. Introduction -This document describes mouse support in XFree86 4.0.2. +This document describes mouse support in XFree86 4.1.0. Mouse configuration has often been mysterious task for novice users. How- ever, once you learn several basics, it is straightforward to write the mouse @@ -928,4 +928,4 @@ wheel's movement will be reported as the buttons 6 and 7. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/mouse.sgml,v 1.11 2000/03/01 00:25:23 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.mouse,v 1.11 2000/12/01 19:47:50 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.mouse,v 1.11.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.newport b/xc/programs/Xserver/hw/xfree86/doc/README.newport index 647969cdc..9ef0f4d10 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.newport +++ b/xc/programs/Xserver/hw/xfree86/doc/README.newport @@ -41,4 +41,4 @@ The following Section "Device" options are supported by the newport driver: Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/newport.sgml,v 1.2 2000/12/12 18:54:29 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.newport,v 1.2 2000/12/12 19:04:03 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.newport,v 1.2.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.r128 b/xc/programs/Xserver/hw/xfree86/doc/README.r128 index a666b3035..b6cfc6f48 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.r128 +++ b/xc/programs/Xserver/hw/xfree86/doc/README.r128 @@ -119,4 +119,4 @@ http://www.suse.com Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/r128.sgml,v 1.8 2000/06/14 00:16:09 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.r128,v 1.13 2000/12/01 19:47:51 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.r128,v 1.13.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.rapidaccess b/xc/programs/Xserver/hw/xfree86/doc/README.rapidaccess new file mode 100644 index 000000000..a78dfb9bc --- /dev/null +++ b/xc/programs/Xserver/hw/xfree86/doc/README.rapidaccess @@ -0,0 +1,48 @@ +The IBM Rapid Access keyboard have some extra buttons +on it to launch programs, control a cd-player and so on. + +These buttons is not functional when the computer is turned +on but have to be activated by sending the codes 0xea 0x71 +to it. + +I've written the following hack to send codes to the keyboard: + +-------------------------------------------------------------- +/* gcc -O2 -s -Wall -osend_to_keyboard send_to_keyboard.c */ +#include <stdlib.h> +#include <unistd.h> +#include <sys/io.h> + +int main( int argc, char *argv[] ) +{ + int i; + + ioperm( 0x60, 3, 1 ); + + for( i = 1; i < argc; i++ ) { + int x = strtol( argv[i], 0, 16 ); + + usleep( 300 ); + outb( x, 0x60 ); + } + + return 0; +} +-------------------------------------------------------------- + +As root you can then call this program (in your boot scripts) +as "send_to_keyboard ea 71" to turn on the extra buttons. + +It's not a good idea to run several instances of this program +at the same time. It is a hack but it works. If you try to +send other codes to the keyboard it probably will lock up. +For other codes see: + +http://www.win.tue.nl/~aeb/linux/kbd/scancodes-2.html#ss2.22 + +-- +Dennis Björklund <db@zigo.dhs.org> + + + +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.rapidaccess,v 1.1 2001/05/18 23:35:32 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.rendition b/xc/programs/Xserver/hw/xfree86/doc/README.rendition index bc9db34bd..70cc35a00 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.rendition +++ b/xc/programs/Xserver/hw/xfree86/doc/README.rendition @@ -145,4 +145,4 @@ on the list of features to be included. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/rendition.sgml,v 1.12 2000/06/17 02:30:33 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.rendition,v 1.12 2000/12/01 19:47:51 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.rendition,v 1.12.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/README.s3virge b/xc/programs/Xserver/hw/xfree86/doc/README.s3virge index 8b878827e..6b71b8f22 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/README.s3virge +++ b/xc/programs/Xserver/hw/xfree86/doc/README.s3virge @@ -6,7 +6,7 @@ 1. Supported hardware -The s3virge driver in XFree86 4.0.2 supports the S3 ViRGE, ViRGE DX, GX, MX, +The s3virge driver in XFree86 4.1.0 supports the S3 ViRGE, ViRGE DX, GX, MX, MX+, and VX chipsets. A majority of testing is done on ViRGE DX chips, mak- ing them the most stable to date. This release has improved support for ViRGE GX2 stability, XVideo support for ViRGE DX (tested) and ViRGE @@ -63,4 +63,4 @@ tact our support email address <XFree86@Xfree86.org> Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/s3virge.sgml,v 1.3 2000/11/28 20:59:17 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.s3virge,v 1.6 2000/12/01 19:47:51 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/README.s3virge,v 1.6.4.1 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/RELNOTES b/xc/programs/Xserver/hw/xfree86/doc/RELNOTES index a1dd1afdb..eb39ead36 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/RELNOTES +++ b/xc/programs/Xserver/hw/xfree86/doc/RELNOTES @@ -1,4 +1,4 @@ - Release Notes for XFree86[tm] 4.0.2 + Release Notes for XFree86[tm] 4.1.0 The XFree86 Project, Inc @@ -7,17 +7,17 @@ Abstract This document contains some information about the features present - in XFree86 4.0.2 and their status. + in XFree86 4.1.0 and their status. 1. Introduction to the 4.x Release Series XFree86 4.0 was the first official release of the new XFree86 4 series. The -current release (4.0.2) is the latest in that series. XFree86 4 represents a +current release (4.1.0) is the latest in that series. XFree86 4 represents a significant redesign of the XFree86 X server. Not all of the hardware drivers from 3.3.x have been ported to 4.x yet, but conversely, 4.x has some hardware support not present in 3.3.x. Our Driver Status document summarizes -how the hardware driver support compares between 3.3.6 and 4.0.2. Please -check there first before downloading 4.0.2. +how the hardware driver support compares between 3.3.6 and 4.1.0. Please +check there first before downloading 4.1.0. The 4.0.1 release introduced a new graphical configuration tool, "xf86cfg", and a text mode interface was added to it for the 4.0.2 release. It is work @@ -28,7 +28,7 @@ built-in to the X server. It is included in the release, and it works well for some hardware. To try it out, just run (as root) "XFree86 -configure". Each of these configuration options will give you a reasonable starting point for a suitable configuration file. We've put some effort into documenting -the 4.0.2 config file format, and you can find that information in the +the 4.1.0 config file format, and you can find that information in the XF86Config manual page. Check that, the driver manual pages and the related documentation for further information. @@ -37,17 +37,18 @@ release, please have a quick read through the Installation Document. It may save you some time and help you figure out which of the binary releases you need. -The next section describes what is new in the latest version (4.0.2). The +The next section describes what is new in the latest version (4.1.0). The other sections below describe some of the new features and changes between 3.3.x and 4.0. There are lot's of new features, and we definitely don't have enough space to cover them all here. -2. Summary of new features in 4.0.2. +2. Summary of new features in 4.1.0. 2.1 X server - o Darwin/Mac OS X is now supported and the X server runs on PowerPC. The - X server for this platform is called "Xdarwin", and its installation and + o Darwin/Mac OS X is now supported on PowerPC and Intel/x86. The X server + runs from the console or in cooperation with the Mac OS X Aqua GUI. The + X server for this platform is called "XDarwin", and its installation and configuration is different from the "XFree86" server used on other plat- forms. Please read the XFree86 on Darwin and Mac OS X document for fur- ther information. @@ -289,7 +290,7 @@ enough space to cover them all here. 3.1 Video Drivers -XFree86 4.0.2 includes the following video drivers: +XFree86 4.1.0 includes the following video drivers: +--------------+--------------------------+----------------------------------+ |Driver Name | Description | Further Information | @@ -341,7 +342,7 @@ Drivers marked with (-) are for Linux/mips only. Darwin/Mac OS X uses IOKit drivers and does not use the module loader drivers listed above. Further information can be found in README.Darwin. -XFree86 4.0.2 includes the following input drivers: +XFree86 4.1.0 includes the following input drivers: 3.2 Input Drivers @@ -367,12 +368,12 @@ XFree86 4.0.2 includes the following input drivers: 4. Summary of XFree86 4. Unlike XFree86 3.3.x where there are multiple X server binaries, each of -which drive different hardware, XFree86 4.0.2 has a single X server binary +which drive different hardware, XFree86 4.1.0 has a single X server binary called XFree86. This binary can either have one or more video drivers linked in statically, or, more usually, dynamically load the video drivers and other modules that are needed. -XFree86 4.0.2 has X server support for most UNIX(R) and UNIX-like operating +XFree86 4.1.0 has X server support for most UNIX(R) and UNIX-like operating systems on Intel/x86 platforms, plus support for Linux on Alpha, PowerPC, IA-64, Sparc, and Mips platforms, and for Darwin on PowerPC. Work on support for additional architectures and operating systems is in progress, and is @@ -394,7 +395,7 @@ they do not need to be recompiled for every different operating system. In the future we plan to take advantage of this to provide more frequent driver module updates in between major releases. -The loader in version 4.0.2 has support for Intel (x86), Alpha and PowerPC +The loader in version 4.1.0 has support for Intel (x86), Alpha and PowerPC platforms. It also has preliminary support for Sparc platforms. The X server makes use of modules for video drivers, X server extensions, @@ -733,7 +734,7 @@ Known problems: 4.7 DGA version 2 -DGA 2.0 is included in 4.0.2, but is not implemented by all drivers. Prelim- +DGA 2.0 is included in 4.1.0, but is not implemented by all drivers. Prelim- inary documentation for the client libraries can be found in the README.DGA document. A good degree of backwards compatibility with version 1.0 is pro- vided. @@ -801,7 +802,7 @@ anti-aliased text and geometric objects as well as perform translucent image overlays and other image operations not possible with the core X rendering system. -XFree86 4.0.2 provides a partial implementation of Render sufficient for +XFree86 4.1.0 provides a partial implementation of Render sufficient for drawing anti-aliased text and image composition. Still to be implemented are geometric primitives and affine transformation of images. @@ -836,10 +837,10 @@ the Xft man page. 4.11.2 FreeType support in Xft -XFree86 4.0.2 includes sources for FreeType version 2.0.1, and, by default, +XFree86 4.1.0 includes sources for FreeType version 2.0.1, and, by default, they are built and installed automatically. -If you prefer, you can configure XFree86 4.0.2 to use an existing Freetype2 +If you prefer, you can configure XFree86 4.1.0 to use an existing Freetype2 installation by telling XFree86 not to build the internal copy and indicating where that external version has been installed. Edit (or create) con- fig/cf/host.def to include: @@ -856,7 +857,7 @@ the FreeType release. 4.11.3 Application Support For Anti-Aliased Text -Only three applications have been modified in XFree86 4.0.2 to work with the +Only three applications have been modified in XFree86 4.1.0 to work with the Render extension and the Xft and FreeType libraries to provide anti-aliased text. Xterm, xditview and x11perf. Migration of other applications may occur in future releases. @@ -1085,4 +1086,4 @@ symbolic links in the old location. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.60 2001/03/02 17:40:48 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/RELNOTES,v 3.97 2001/03/02 17:47:53 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/RELNOTES,v 3.97.2.2 2001/06/02 04:44:36 torrey Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/Status b/xc/programs/Xserver/hw/xfree86/doc/Status index bc8b7fa42..8280311b9 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/Status +++ b/xc/programs/Xserver/hw/xfree86/doc/Status @@ -1,24 +1,24 @@ - Driver Status for XFree86[tm] 4.0.2 + Driver Status for XFree86[tm] 4.1.0 The XFree86 Project, Inc - 4 December 2000 + 1 June 2001 Abstract This document provides information about the status of the driver - and hardware support in XFree86 4.0.2 compared with that in XFree86 + and hardware support in XFree86 4.1.0 compared with that in XFree86 3.3.6. Please send updates for this document to <fixes@xfree86.org>. Please do not send requests for information - or support to that address. + or support to that address (they will not be answered). 1. Introduction This document contains one section per vendor (organised alphabetically) for -each chipset family that is supported in XFree86 3.3.6 or XFree86 4.0.2. It +each chipset family that is supported in XFree86 3.3.6 or XFree86 4.1.0. It includes information about the status of the drivers and the hardware they support, including a comparison of the level of support between versions -3.3.6 and 4.0.2. Unless otherwise stated, hardware is classified as "sup- +3.3.6 and 4.1.0. Unless otherwise stated, hardware is classified as "sup- ported" if its driver provides basic 2D support. Support for additional fea- tures may or may not be present. @@ -27,9 +27,9 @@ XF86_SVGA server, which has a set of driver modules that are built into it at compile time. In other cases, X servers for specific chips (or families of chips) are provided (such as XF86_AGX, XF86_Mach64, etc.). -In XFree86 4.0.2, there is only one X server, called "XFree86", which can +In XFree86 4.1.0, there is only one X server, called "XFree86", which can load driver modules at runtime. Thus there is no specific mention of a -server binary when 4.0.2 is discussed; only the XFree86 server is used. +server binary when 4.1.0 is discussed; only the XFree86 server is used. Third-party vendors (often the manufacturers of various video chipsets) may provide their own drivers for the XFree86 server, but these third-party mod- ules are beyond the scope of this document. @@ -45,7 +45,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (including acceleration) for Voodoo Banshee and Voodoo3 cards is provided by the XF86_SVGA server with the tdfx driver. - 4.0.2: + 4.1.0: Support for Voodoo Graphics and Voodoo 2 chips is available on platforms where Glide is available (Linux and FreeBSD(?)) and is provided by the "glide" driver (requires version 2.x of the Glide @@ -55,7 +55,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. Voodoo4, and Voodoo5 is provided by the "tdfx" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 3. 3Dlabs @@ -65,14 +65,14 @@ architectures known to work on (e.g., Alpha, PPC), etc. ramdacs), Permedia with IBM RGB526 RAMDAC, and Permedia 2, 2a, 2v is provided by the XF86_3DLabs server. - 4.0.2: + 4.1.0: Support (including acceleration) for Permedia, Permedia 2, 2v, (and 2a?), Permedia 3, GLINT 500TX, GLINT MX, GLINT Gamma, and GLINT Delta coproc is provided by the "glint" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. The - Permedia 3 is only supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. The + Permedia 3 is only supported in 4.1.0. 4. Alliance @@ -80,14 +80,14 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (including acceleration) for the AT24, AP6422, AT3D. Support is provided by the XF86_SVGA server with the apm driver. - 4.0.2: + 4.1.0: Support (including acceleration?) for the AT24, AT25 and AT3D. This support is provided by the "apm" driver. This driver cur- rently has only incomplete support for the AP6422. Summary: - The AP6422 is supported in 3.3.6 but not fully in 4.0.2. The - AT25 is supported in 4.0.2 but not in 3.3.6. + The AP6422 is supported in 3.3.6 but not fully in 4.1.0. The + AT25 is supported in 4.1.0 but not in 3.3.6. 5. ARK Logic @@ -96,12 +96,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. and ARK2000MT. Support is provided by the XF86_SVGA server with the ark driver. - 4.0.2: + 4.1.0: Support (including acceleration) for the ARK1000PV, ARK2000PV, and ARK2000MT. Support is provided by the "ark" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 6. ATI @@ -119,17 +119,17 @@ architectures known to work on (e.g., Alpha, PPC), etc. driver. Accelerated support is provided for the Rage 128 chips by the XF86_SVGA server with the r128 driver. - 4.0.2: + 4.1.0: Accelerated support is provided for Mach64, Rage, Rage 128 and Radeon chips. Unaccelerated support is provided for all of the others except the Mach8 and some early Mach32 chips by the "ati" driver. Summary: - All chips supported in 3.3.6 are supported in 4.0.2 except for - Mach8 and some old Mach32 chips. The support in 4.0.2 is, how- - ever, unaccelerated for all chips except the Mach64, Rage and - Rage 128 variants. + All chips supported in 3.3.6 are supported in 4.1.0 except for + Mach8 and some old Mach32 chips. The support in 4.1.0 is, how- + ever, unaccelerated for all chips except the Mach64, Rage, Rage + 128 and Radeon variants. 7. Avance Logic @@ -140,12 +140,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. the others. These drivers reportedly work, but they have no maintainer. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old drivers have not been ported. Summary: - No Avance Logic chips are supported in 4.0.2. + No Avance Logic chips are supported in 4.1.0. 8. Chips and Technologies @@ -155,13 +155,13 @@ architectures known to work on (e.g., Alpha, PPC), etc. 64300. This support is provided by the XF86_SVGA server with the chips driver. - 4.0.2: + 4.1.0: Support (accelerated) for the 65520, 65525, 65530, 65535, 65540, 65545, 65546, 65548, 65550, 65554, 65555, 68554, 69000, 64200 and 64300. This support is provided by the "chips" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 9. Cirrus Logic @@ -173,13 +173,13 @@ architectures known to work on (e.g., Alpha, PPC), etc. 7541, 7542, 7543, 7548, 7555 and 7556 is provided by the XF86_SVGA server with the cirrus driver. - 4.0.2: + 4.1.0: Support (accelerated) for the Alpine (5430, 5434, 5436, 5446, 5480, 7548), and Laguna (5462, 5464, 5465) chips is provided by the "cirrus" driver. Summary: - The following chips are supported in 3.3.6 but not in 4.0.2: + The following chips are supported in 3.3.6 but not in 4.1.0: 6410, 6412, 6420, 6440, 5420, 5422, 5424, 5426, 5428, 5429, 6205, 6215, 6225, 6235, 7541, 7542, 7543, 7555 and 7556. @@ -195,7 +195,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. 24 plane 3D chips (on Alpha platforms) is provided by the XF86_TGA server. - 4.0.2: + 4.1.0: No support for the Compaq AVGA (driver hasn't been ported). Support (accelerated) for the DEC 21030 TGA 8 plane, 24 plane and @@ -203,8 +203,8 @@ architectures known to work on (e.g., Alpha, PPC), etc. the "tga" driver. Summary: - No Compaq AVGA support in 4.0.2. DEC TGA support is equivalent - in both 3.3.6 and 4.0.2. + No Compaq AVGA support in 4.1.0. DEC TGA support is equivalent + in both 3.3.6 and 4.1.0. 11. Cyrix @@ -212,12 +212,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (accelerated) for the Cyrix MediaGX is provided by the XF86_SVGA server with the cyrix driver. - 4.0.2: - The 3.3.6 driver has been ported to 4.0.2, including accelera- + 4.1.0: + The 3.3.6 driver has been ported to 4.1.0, including accelera- tion, but feedback is needed. Summary: - Cyrix MediaGX users are encouraged to test its support in 4.0.2. + Cyrix MediaGX users are encouraged to test its support in 4.1.0. 12. Epson @@ -225,12 +225,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (accelerated) for the Epson SPC8110 is provided by the XF86_SVGA server with the spc8100 driver. - 4.0.2: + 4.1.0: No native support for this chipset, because the old driver has not been ported. Summary: - No Epson chips are supported in 4.0.2. + No Epson chips are supported in 4.1.0. 13. Genoa @@ -240,12 +240,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. because we don't have any recent test reports, and this driver has no maintainer. - 4.0.2: + 4.1.0: No native support for this chipset, because the old driver has not been ported. Summary: - No Genoa chips are supported in 4.0.2. + No Genoa chips are supported in 4.1.0. 14. IBM @@ -260,7 +260,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support for the IBM XGA-2 chip is provided by the XF86_AGX server. - 4.0.2: + 4.1.0: Support for the standard IBM VGA chip (and compatibles) is pro- vided by the "vga" driver. @@ -269,7 +269,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. Summary: The standard VGA core is supported in both versions, but there is - no support for the 8514/A or XGA-2 in 4.0.2. + no support for the 8514/A or XGA-2 in 4.1.0. 15. IIT @@ -277,12 +277,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (accelerated) for the AGX-016, AGX-015 and AGX-014 is provided by the XF86_AGX server. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old driver has not been ported. Summary: - No IIT chips are supported in 4.0.2. + No IIT chips are supported in 4.1.0. 16. Integrated Micro Solutions (IMS) @@ -290,12 +290,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (accelerated) for the IMS Twin Turbo 128 is provided by the XF86_SVGA server with the imstt driver. - 4.0.2: + 4.1.0: Support (accelerated) for the IMS Twin Turbo 128 is provided by the "imstt" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 17. Intel @@ -306,7 +306,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. Linux, and requires the agpgart.o kernel module in order to use modes that require more than 1MB of video memory. - 4.0.2: + 4.1.0: Support (accelerated) for the Intel i740 is provided by the "i740" driver, and support for the Intel i810 (including i810-dc100 and i810e) and i815 is provided by the "i810" driver. @@ -325,13 +325,13 @@ architectures known to work on (e.g., Alpha, PPC), etc. (Mystique), MGA2164W (Millennium II) (PCI and AGP), G100, G200 and G400 is provided by the XF86_SVGA server with the mga driver. - 4.0.2: + 4.1.0: Support (accelerated) for the MGA2064W (Millennium I), MGA1064SG (Mystique), MGA2164W (Millennium II) (PCI and AGP), G100, G200 and G400 is provided by the "mga" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 19. MX (???) @@ -341,12 +341,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. is unknown because we don't have any recent test reports, and this driver has no maintainer. - 4.0.2: + 4.1.0: No native support for this chipset, because the old driver has not been ported. Summary: - No MX (???) chips are supported in 4.0.2. + No MX (???) chips are supported in 4.1.0. 20. NCR @@ -355,12 +355,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. XF86_SVGA server and the ncr77c22 driver. The status of this support is unknown because we don't have any recent test reports. - 4.0.2: + 4.1.0: No native support for this chipset, because the old driver has not been ported. Summary: - No NCR chips are supported in 4.0.2. + No NCR chips are supported in 4.1.0. 21. NeoMagic @@ -369,14 +369,14 @@ architectures known to work on (e.g., Alpha, PPC), etc. NM2097, NM2160 and NM2200 chipsets is provided by the XF86_SVGA server with the neo driver. - 4.0.2: + 4.1.0: Support (accelerated) for the NeoMagic NM2070, NM2090, NM2093, NM2097, NM2160, NM2200, NM2230, NM2360 and NM2380 chipsets is provided by the "neomagic" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. The - NM2230 and later chips are only supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. The + NM2230 and later chips are only supported in 4.1.0. 22. NVIDIA @@ -385,15 +385,15 @@ architectures known to work on (e.g., Alpha, PPC), etc. (Ultra, Vanta, M64), GeForce (DDR, 256) and Quadro is provided by the XF86_SVGA server and the nv driver. - 4.0.2: + 4.1.0: Support (accelerated) for the Riva 128, 128ZX, TNT, TNT2 (Ultra, Vanta, M64), GeForce (DDR, 256), GeForce2 (GTS, Ultra, MX), Quadro, and Quadro2 is provided by the "nv" driver. Summary: All chipsets supported in 3.3.6 except the NV1 are also supported - in 4.0.2. Support for the newer chips (GeForce2 and later) is - only available in 4.0.2. + in 4.1.0. Support for the newer chips (GeForce2 and later) is + only available in 4.1.0. 23. Number Nine @@ -401,12 +401,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support (accelerated) for the Imagine 128, Ticket 2 Ride, Revolu- tion 3D and Revolution IV is provided by the XF86_I128 server. - 4.0.2: + 4.1.0: Support (accelerated) for the Imagine 128, Ticket 2 Ride, Revolu- tion 3D and Revolution IV is provided by the "i128" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 24. Oak Technologies, Inc. @@ -415,12 +415,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. acceleration) is provided by the XF86_SVGA server and the oak driver. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old driver has not been ported. Summary: - No Oak chips are supported in 4.0.2. + No Oak chips are supported in 4.1.0. 25. Paradise/Western Digital @@ -431,12 +431,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. port for some of these chipsets is uncertain because we don't have any recent test reports, and this driver has no maintainer. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old driver has not been ported. Summary: - No Paradise/Western Digital chips are supported in 4.0.2. + No Paradise/Western Digital chips are supported in 4.1.0. 26. RealTek @@ -446,12 +446,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. unknown because we don't have any recent test reports, and this driver has no maintainer. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old driver has not been ported. Summary: - No RealTek chips are supported in 4.0.2. + No RealTek chips are supported in 4.1.0. 27. Rendition/Micron @@ -459,12 +459,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. Support for the Verite 1000, 2100 and 2200 is provided by the XF86_SVGA server with the rendition driver. - 4.0.2: + 4.1.0: Support for the Verite 1000, 2100 and 2200 is provided by the "rendition" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 28. S3 @@ -481,7 +481,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. age2000, is provided by the XF86_SVGA server with the s3_savage driver on some OSes (Linux, *BSD). - 4.0.2: + 4.1.0: Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the "s3virge" driver. Support (accelerated) for the @@ -491,19 +491,19 @@ architectures known to work on (e.g., Alpha, PPC), etc. Summary: Only the ViRGE, Trio3D and Savage chipsets are supported in - 4.0.2. All of the other chipsets are only supported in 3.3.6. + 4.1.0. All of the other chipsets are only supported in 3.3.6. 29. Silicon Graphics, Inc. (SGI) 3.3.6: No SGI hardware is supported in 3.3.6. - 4.0.2: + 4.1.0: Unaccelerated support for the SGI Indy's Newport cards is pro- vided by the "newport" driver. Summary: - SGI hardware is supported only in 4.0.2. + SGI hardware is supported only in 4.1.0. 30. Silicon Integrated Systems (SiS) @@ -512,7 +512,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. 86C225, 5597, 5598, 6326, 530, 620, 300, 630 and 540 is provided by the XF86_SVGA server with the sis driver. - 4.0.2: + 4.1.0: Support (accelerated) for the SiS 530, 620, 6326 is provided by the "sis" driver. The 630, 300, and 540 are also supported, but this code is new and there are @@ -529,20 +529,20 @@ architectures known to work on (e.g., Alpha, PPC), etc. LynxEM+ and Lynx3DM chips is provided by the XF86_SVGA server with the smi driver. - 4.0.2: + 4.1.0: Support (accelerated) for the Lynx, LynxE, Lynx3D, LynxEM, LynxEM+ and Lynx3DM chips is provided by the "siliconmotion" driver. Summary: - All hardware supported in 3.3.6 is also supported in 4.0.2. + All hardware supported in 3.3.6 is also supported in 4.1.0. 32. Sun Microsystems 3.3.6: No Sun hardware is supported in 3.3.6. - 4.0.2: + 4.1.0: Sun BW2 framebuffers are supported by the "sunbw2" driver. Sun CG3 framebuffers are supported by the "suncg3" driver. Sun CG6 framebuffers are supported by the "suncg6" driver. Sun CG14 @@ -552,7 +552,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. framebuffers are supported by the "suntcx" driver. Summary: - Sun hardware is supported only in 4.0.2. + Sun hardware is supported only in 4.1.0. 33. Trident Microsystems @@ -567,7 +567,7 @@ architectures known to work on (e.g., Alpha, PPC), etc. CyberBlade/DSTN/i7 and CyberBlade/i1 is provided by the XF86_SVGA server with the tvga8900 driver. - 4.0.2: + 4.1.0: Support (accelerated where the chip supports it) for the TVGA8900D, TGUI9440AGi, TGUI9660, TGUI9680, ProVidia 9682, Pro- Vidia 9685, Cyber9320, Cyber9382, Cyber9385, Cyber9388, @@ -579,10 +579,10 @@ architectures known to work on (e.g., Alpha, PPC), etc. Summary: The following (older) chipsets that are supported in 3.3.6 are - not supported in 4.0.2: TVGA8200LX, TVGA8800CS, TVGA8900B, + not supported in 4.1.0: TVGA8200LX, TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000, TVGA9000i, TVGA9100B, TVGA9200CXr, TGUI9400CXi, TGUI9420, TGUI9430DGi. The remaining - listed chipsets are supported in 4.0.2. + listed chipsets are supported in 4.1.0. 34. Tseng Labs @@ -594,13 +594,13 @@ architectures known to work on (e.g., Alpha, PPC), etc. driver. Support (accelerated) for the ET4000/W32 series and the ET6000 is also provided by the deprecated XF86_W32 server. - 4.0.2: + 4.1.0: Support for the ET4000AX, and accelerated support for the ET4000/W32, ET4000/W32i, ET4000/W32p, ET6000 and ET6100 is pro- vided by the "tseng" driver. Summary: - All cards supported by 3.3.6 are also supported by 4.0.2 except + All cards supported by 3.3.6 are also supported by 4.1.0 except for the old ET3000. 35. Video 7 @@ -611,12 +611,12 @@ architectures known to work on (e.g., Alpha, PPC), etc. unknown because we don't have any recent test reports, and this driver has no maintainer. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old driver has not been ported. Summary: - No Video 7 chips are supported in 4.0.2. + No Video 7 chips are supported in 4.1.0. 36. Weitek @@ -625,14 +625,14 @@ architectures known to work on (e.g., Alpha, PPC), etc. server and accelerated support for the P9100 is provided by the XF86_SVGA server with the p9x00 driver. - 4.0.2: + 4.1.0: No native support for these chipsets, because the old drivers have not been ported. Summary: - No Weitek chips are supported in 4.0.2. + No Weitek chips are supported in 4.1.0. - Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml,v 1.29 2001/04/04 01:34:18 dawes Exp $ + Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml,v 1.29.2.2 2001/06/01 18:09:49 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/Status,v 1.23 2001/04/10 16:44:32 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/Status,v 1.23.2.2 2001/06/01 18:26:45 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/Versions b/xc/programs/Xserver/hw/xfree86/doc/Versions index d681c5f75..feedad8e3 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/Versions +++ b/xc/programs/Xserver/hw/xfree86/doc/Versions @@ -298,4 +298,4 @@ and any other 4.0.x releases will continue with the Mmnn scheme. Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Versions.sgml,v 1.1 2001/02/07 18:49:31 dawes Exp $ -$XFree86: xc/programs/Xserver/hw/xfree86/doc/Versions,v 1.1 2001/02/07 18:52:28 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/Versions,v 1.1.4.1 2001/06/01 18:26:46 dawes Exp $ diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml index a9ca6d546..b4d541442 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml @@ -27,7 +27,7 @@ <title>XFree86 X server ``New Design'' (DRAFT) <author>The XFree86 Project, Inc -<date>Last modified 2 December 2000 +<date>Last modified 1 May 2001 @@ -36,7 +36,7 @@ <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml,v 1.40 2000/12/27 04:57:08 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DESIGN.sgml,v 1.44 2001/05/19 00:40:30 dawes Exp $ </ident> @@ -2561,7 +2561,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;OptionInfoPtr xf86TokenToOptinfo(OptionInfoPtr table, int token)&e.code; + &s.code;OptionInfoPtr xf86TokenToOptinfo(const OptionInfoRec *table, int token)&e.code; <quote><p> Returns a pointer to the &s.code;OptionInfoRec&e.code; in &s.code;table&e.code; with a token field matching @@ -2570,7 +2570,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86IsOptionSet(OptionInfoPtr table, int token)&e.code; + &s.code;Bool xf86IsOptionSet(const OptionInfoRec *table, int token)&e.code; <quote><p> Returns the &s.code;found&e.code; field of the &s.code;OptionInfoRec&e.code; in &s.code;table&e.code; with a @@ -2582,7 +2582,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;char *xf86GetOptValString(OptionInfoPtr table, int token)&e.code; + &s.code;char *xf86GetOptValString(const OptionInfoRec *table, int token)&e.code; <quote><p> Returns the &s.code;value.str&e.code; field of the &s.code;OptionInfoRec&e.code; in &s.code;table&e.code; with a @@ -2591,7 +2591,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86GetOptValInteger(OptionInfoPtr table, int token, + &s.code;Bool xf86GetOptValInteger(const OptionInfoRec *table, int token, &f.indent;int *value)&e.code; <quote><p> Returns via &s.code;*value&e.code; the &s.code;value.num&e.code; @@ -2604,7 +2604,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86GetOptValULong(OptionInfoPtr table, int token, + &s.code;Bool xf86GetOptValULong(const OptionInfoRec *table, int token, &f.indent;unsigned long *value)&e.code; <quote><p> Like &s.code;xf86GetOptValInteger()&e.code;, except the value is @@ -2612,7 +2612,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86GetOptValReal(OptionInfoPtr table, int token, + &s.code;Bool xf86GetOptValReal(const OptionInfoRec *table, int token, &f.indent;double *value)&e.code; <quote><p> Like &s.code;xf86GetOptValInteger()&e.code;, except that @@ -2620,7 +2620,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86GetOptValFreq(OptionInfoPtr table, int token, + &s.code;Bool xf86GetOptValFreq(const OptionInfoRec *table, int token, &f.indent;OptFreqUnits expectedUnits, double *value)&e.code; <quote><p> Like &s.code;xf86GetOptValInteger()&e.code;, except that the @@ -2636,7 +2636,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86GetOptValBool(OptionInfoPtr table, int token, Bool *value)&e.code; + &s.code;Bool xf86GetOptValBool(const OptionInfoRec *table, int token, Bool *value)&e.code; <quote><p> This function is used to check boolean options (&s.code;OPTV_BOOLEAN&e.code;). If the function return value is @@ -2654,7 +2654,7 @@ Next, the higher level functions that most drivers would use. </quote> - &s.code;Bool xf86ReturnOptValBool(OptionInfoPtr table, int token, Bool def)&e.code; + &s.code;Bool xf86ReturnOptValBool(const OptionInfoRec *table, int token, Bool def)&e.code; <quote><p> This function is used to check boolean options (&s.code;OPTV_BOOLEAN&e.code;). If the option is set, its value @@ -5774,7 +5774,15 @@ programming the standard VGA registers, and for handling VGA colourmaps. &s.code;hwp&e.code; with the standard VGA set of functions. This is called by &s.code;vgaHWGetHWRec()&e.code;, so there is usually no need to call this explicitly. The register access functions - are described below. + are described below. If the registers are shadowed in some other + port I/O space (for example a PCI I/O region), these functions + can be used to access the shadowed registers if + &s.code;hwp->PIOOffset&e.code; is initialised with + &s.code;offset&e.code;, calculated in such a way that when the + standard VGA I/O port value is added to it the correct offset into + the PIO area results. This value is initialised to zero in + &s.code;vgaHWGetHWRec()&e.code;. (Note: the PIOOffset functionality + is present in XFree86 4.1.0 and later.) </quote> @@ -5861,6 +5869,20 @@ programming the standard VGA registers, and for handling VGA colourmaps. </quote> + &s.code;void vgaHWEnable(vgaHWPtr hwp)&e.code; + <quote><p> + This function enables the VGA subsystem. (Note, this function is + present in XFree86 4.1.0 and later.). + + </quote> + + &s.code;void vgaHWDisable(vgaHWPtr hwp)&e.code; + <quote><p> + This function disables the VGA subsystem. (Note, this function is + present in XFree86 4.1.0 and later.). + + </quote> + &s.code;void vgaHWSave(ScrnInfoPtr pScrn, vgaRegPtr save, int flags)&e.code; <quote><p> This function saves the VGA state. The state is written to the @@ -6188,6 +6210,20 @@ programming the standard VGA registers, and for handling VGA colourmaps. Return the value read from the DAC Data register. </quote> + + &s.code;CARD8 readEnable(vgaHWptr hwp)&e.code; + <quote><p> + Return the value read from the VGA Enable register. (Note: This + function is present in XFree86 4.1.0 and later.) + + </quote> + + &s.code;void writeEnable(vgaHWPtr hwp, CARD8 value)&e.code; + <quote><p> + Write &s.code;value&e.code; to the VGA Enable register. (Note: This + function is present in XFree86 4.1.0 and later.) + + </quote> </quote> <sect>Some notes about writing a driver<label id="sample"> @@ -6409,6 +6445,7 @@ typedef struct { Bool noAccel; Bool hwCursor; CloseScreenProcPtr CloseScreen; + OptionInfoPtr Options; ... } ZZZRec, *ZZZPtr; </code> @@ -6425,15 +6462,13 @@ typedef enum { OPTION_NOACCEL } ZZZOpts; -static OptionInfoRec ZZZOptions[] = { +static const OptionInfoRec ZZZOptions[] = { { OPTION_FOO_HACK, "FooHack", OPTV_INTEGER, {0}, FALSE }, { OPTION_PCI_RETRY, "PciRetry", OPTV_BOOLEAN, {0}, FALSE }, { OPTION_HW_CURSOR, "HWcursor", OPTV_BOOLEAN, {0}, FALSE }, { OPTION_NOACCEL, "NoAccel", OPTV_BOOLEAN, {0}, FALSE }, { -1, NULL, OPTV_NONE, {0}, FALSE } }; - -#define nZZZOptions (sizeof(ZZZOptions) / sizeof(ZZZOptions[0])) </code> <p> </itemize> @@ -6721,8 +6756,6 @@ ZZZProbe(DriverPtr drv, int flags) static Bool ZZZPreInit(ScrnInfoPtr pScrn, int flags) { - OptionInfoRec options[nZZZOptions]; - /* Fill in the monitor field */ pScrn->monitor = pScrn->confScreen->monitor; @@ -6801,10 +6834,14 @@ ZZZPreInit(ScrnInfoPtr pScrn, int flags) /* * Process the options based on the information in ZZZOptions. - * The results are written to options. + * The results are written to pZzz->Options. If all of the options + * processing is done within this function a local variable "options" + * can be used instead of pZzz->Options. */ - (void)memcpy(options, ZZZOptions, sizeof(ZZZOptions)); - xf86ProcessOptions(pScrn->scrnIndex, pScrn->options, options); + if (!(pZzz->Options = xalloc(sizeof(ZZZOptions)))) + return FALSE; + (void)memcpy(pZzz->Options, ZZZOptions, sizeof(ZZZOptions)); + xf86ProcessOptions(pScrn->scrnIndex, pScrn->options, pZzz->Options); /* * Set various fields of ScrnInfoRec and/or ZZZRec based on @@ -6812,25 +6849,25 @@ ZZZPreInit(ScrnInfoPtr pScrn, int flags) */ from = X_DEFAULT; pZzz->hwCursor = FALSE; - if (xf86IsOptionSet(options, OPTION_HW_CURSOR)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_HW_CURSOR)) { from = X_CONFIG; pZzz->hwCursor = TRUE; } xf86DrvMsg(pScrn->scrnIndex, from, "Using %s cursor\n", pZzz->hwCursor ? "HW" : "SW"); - if (xf86IsOptionSet(options, OPTION_NOACCEL)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_NOACCEL)) { pZzz->noAccel = TRUE; xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "Acceleration disabled\n"); } else { pZzz->noAccel = FALSE; } - if (xf86IsOptionSet(options, OPTION_PCI_RETRY)) { + if (xf86IsOptionSet(pZzz->Options, OPTION_PCI_RETRY)) { pZzz->UsePCIRetry = TRUE; xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "PCI retry enabled\n"); } pZzz->fooHack = 0; - if (xf86GetOptValInteger(options, OPTION_FOO_HACK, + if (xf86GetOptValInteger(pZzz->Options, OPTION_FOO_HACK, &pZzz->fooHack)) { xf86DrvMsg(pScrn->scrnIndex, X_CONFIG, "Foo Hack set to %d\n", pZzz->fooHack); diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml index 392439d35..9107b97ff 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml @@ -10,10 +10,10 @@ <author> <htmlurl url="http://www.valinux.com/" name="VA Linux Systems, Inc."> Professional Services - Graphics. - <date>15 March 2001 + <date>3 May 2001 <ident> - $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml,v 1.21 2001/04/10 16:07:58 dawes Exp $ + $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRI.sgml,v 1.24 2001/05/19 00:42:22 dawes Exp $ </ident> <toc> @@ -131,16 +131,15 @@ </itemize> <item>ATI Rage 128, supported on Intel x86 and AMD: <itemize> - <item>Rage Fury AGP - <item>Rage Magnum AGP - <item>XPERT 2000 AGP - <item>XPERT 128 AGP - <item>XPERT 99 AGP - <item>All-in-Wonder 128 AGP + <item>Rage Fury + <item>Rage Magnum + <item>XPERT 2000 + <item>XPERT 128 + <item>XPERT 99 + <item>All-in-Wonder 128 </itemize> - The PCI versions of these cards also have minimal support. - Note that there are Rage 128 Pro boards on the market but they're - not yet supported. + Note that both PCI and AGP versions of Rage 128 based cards + are supported at this time. <item>ATI Radeon, supported on Intel x86 and AMD: <itemize> <item>Radeon SDR AGP @@ -678,7 +677,7 @@ <sect1>3dfx Banshee, Voodoo3, Voodoo4 and Voodoo5 Series <p> - <sect2>Dependencies + <sect2>Requirements <p> The 3dfx DRI driver requires special versions of the 3dfx Glide library. @@ -792,7 +791,7 @@ 32bpp mode is fully 3D accelerated. </itemize> - <sect2>Performance + <sect2>Performance and Features <p> <itemize> <item> @@ -874,6 +873,9 @@ <item> The lowest mipmap level is sometimes miscolored in trilinear- sampled polygons. + <item> + The GL_EXT_texture_env_combine extension is supported on the + Voodoo4 and Voodoo5. </itemize> <sect2>Known Problems @@ -900,13 +902,10 @@ <sect1>Intel i810 <p> - <sect2>Dependencies + <sect2>Requirements +<p> + A kernel with AGP GART support (such as Linux 2.4.x) is needed. <p> - A Linux kernel with AGP GART support is required. - The 2.2.x kernel series does not have AGP GART support. - The 2.4.x test kernels have AGP GART and have been tested - with the i810. - <p> <sect2>Configuration <p> @@ -966,15 +965,29 @@ rendering will be disabled. </itemize> + <sect2>Performance and Features +<p> + Basically all of the i810 features which can be exposed through + OpenGL 1.2 are implemented. + However, the following OpenGL features are implemented in software + and will be slow: + <itemize> + <item>Stencil buffer and accumulation buffer operations + <item>Blend subtract, min/max and logic op blend modes + <item>glColorMask when any mask is set to false + <item>GL_SEPARATE_SPECULAR_COLOR lighting mode + <item>glDrawBuffer(GL_FRONT_AND_BACK) + <item>Using 1D or 3D textures + <item>Using texture borders + </itemize> <p> <sect1>Matrox G200 and G400 <p> - <sect2>Dependencies + <sect2>Requirements +<p> + A kernel with AGP GART support (such as Linux 2.4.x) is needed. <p> - A Linux kernel with AGP GART support (such as the 2.4.x test - kernels) is needed. - <p> <sect2>Configuration <p> Your XF86Config file's device section must specify the @@ -1028,7 +1041,7 @@ <tt>/usr/X11R6/lib/modules/dri/mga_dri.so</tt>. This will be automatically loaded by libGL.so. - <sect2>Performance + <sect2>Performance and Features <p> Software rendering will be used under any of the following conditions: @@ -1048,7 +1061,7 @@ on your motherboard. <p> - Compaq has funded the implementation of AGP acclerated + Compaq has funded the implementation of AGP accelerated ReadPixels and DrawPixels in this driver. With this implementation, on a G400 drawing directly from AGP memory (exported to the client), throughput of up to 1 GB/sec has @@ -1126,11 +1139,10 @@ <sect1>ATI Rage 128 <p> - <sect2>Dependencies + <sect2>Requirements +<p> + A kernel with AGP GART support (such as Linux 2.4.x) is needed. <p> - A Linux kernel with AGP GART support (such as the 2.4.x test - kernels) is needed. - <p> <sect2>Configuration <p> Your XF86Config file's device section must specify the @@ -1175,7 +1187,7 @@ You may also set your screen depth to 32 for 32bpp mode. <p> - <sect2>Performance + <sect2>Performance and Features <p> While PCI Rage 128 based cards are supported, they do not yet support PCI GART, so they will not perform as well as their @@ -1185,7 +1197,20 @@ used by default. Higher AGP speeds may result in unreliable performance depending on your motherboard. - +<p> + Note that even at 32bpp there is no alpha channel. +<p> + The following OpenGL features are implemented in software and + will be slow: + <itemize> + <item>Stencil buffer and accumulation buffer operations + <item>Blend subtract, min/max and logic op blend modes + <item>GL_SEPARATE_SPECULAR_COLOR lighting mode + <item>glDrawBuffer(GL_FRONT_AND_BACK) + <item>Using 1D or 3D textures + <item>Using texture borders + </itemize> +<p> <sect2>Known Problems <p> If you experience stability problems you may try setting the @@ -1197,11 +1222,10 @@ <sect1>ATI Radeon <p> - <sect2>Dependencies + <sect2>Requirements +<p> + A kernel with AGP GART support (such as Linux 2.4.x) is needed. <p> - A Linux kernel with AGP GART support (such as the 2.4.x test - kernels) is needed. - <p> <sect2>Configuration <p> Your XF86Config file's device section must specify the @@ -1245,7 +1269,7 @@ You may also set your screen depth to 32 for 32bpp mode. <p> - <sect2>Performance + <sect2>Performance and Features <p> While this driver supports many of the features of ATI Radeon cards, we do not <em/yet/ fully support the card's TCL @@ -1254,11 +1278,38 @@ The AGP mode may be set to 1, 2, or 4. One is used by default. Higher AGP speeds may result in unreliable performance depending on your motherboard. - +<p> + The following OpenGL features are implemented in software and will + be slow: + <itemize> + <item>Blend subtract, blend min/max and blend logicops + <item>Stencil and accumulation operations + <item>1D and 3D textures + <item>Texture borders + </itemize> +<p> + The GL_EXT_texture_env_combine, GL_EXT_texture_env_add and + GL_EXT_texture_env_dot3 extensions are supported (or will be + soon supported in the new driver based on Mesa 3.5). +<p> + We hope to implement support for the following features in the + future: + <itemize> + <item>Vertex transformation, clipping and lighting (TCL) + <item>Hardware stencil buffer + <item>Cube map textures + <item>3D textures + <item>Three texture units + </itemize> +<p> <sect2>Known Problems <p> - None. - + Certain (early?) revisions of the AMD Irongate chipset have + AGPGART problems which effect Radeon, and other graphics cards. + The card may work unreliably, or not work at all. If the DRM + kernel module is not loaded, the 2D Xserver may work. There's + hope that this can be fixed in the future. +<p> <sect1>3DLabs Oxygen GMX 2000 <p> @@ -1274,7 +1325,7 @@ overlays, stereo, hardware-accelerated indirect rendering. <p> OpenGL-like functionality is provided with the Mesa library. - XFree86 4.0.2 uses Mesa 3.4. + XFree86 4.1.0 uses Mesa 3.4.2. Subsequent releases of XFree86 will use newer versions of Mesa. When newer versions of Mesa are available, the 3D drivers can be updated without reinstalling XFree86 or libGL.so. @@ -1369,8 +1420,8 @@ <p> A collection of useful configuration files, libraries, headers, utilities and demo programs is available from - <htmlurl url="http://dri.sourceforge.net/resources/resources.html" - name="http://dri.sourceforge.net/resources/resources.html"> + <htmlurl url="http://dri.sourceforge.net/res.phtml" + name="http://dri.sourceforge.net/res.phtml"> <sect1>Documentation <p> @@ -1385,7 +1436,8 @@ <item>Visit the <htmlurl url="http://dri.sourceforge.net" name="DRI project on SourceForge.net"> for the latest development news about the DRI and 3D drivers. - <item>The <htmlurl url="http://dri.sourceforge.net/DRIcompile.html" + <item>The <htmlurl + url="http://dri.sourceforge.net/doc/DRIcompile.html" name="DRI Compilation Guide"> explains how to download, compile and install the DRI for yourself. </itemize> diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml index f77dce508..75dc89bd9 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml @@ -10,10 +10,10 @@ <author> <htmlurl url="http://www.valinux.com/" name="VA Linux Systems, Inc."> Professional Services - Graphics. - <date>15 March 2001 + <date>21 April 2001 <ident> - $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml,v 1.13 2001/04/05 19:29:42 dawes Exp $ + $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/DRIcomp.sgml,v 1.14 2001/05/02 15:06:08 dawes Exp $ </ident> <toc> @@ -175,7 +175,8 @@ <item>hit ESC to return to the top-level menu <item>Go to <em>Character devices</em> <item>Disable <em>Direct Rendering Manager (XFree86 DRI support)</em> - since we'll use the DRI module from the XFree86/DRI tree. + since we'll use the DRI code from the XFree86/DRI tree and will + compile it there. <item>Go to <em>/dev/agpgart (AGP Support) (EXPERIMENTAL) (NEW)</em> <item>Hit SPACE twice to build AGP support into the kernel <item>Enable all chipsets' support for AGP @@ -503,7 +504,7 @@ <tt>/usr/src/linux-2.4.x</tt>, <verb> cd ~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel - make TREE=/usr/src/linux-2.4 + make TREE=/usr/src/linux-2.4.x/include </verb> or alternatively, edit Makefile to include this change. <p> @@ -516,7 +517,7 @@ The DRI kernel modules are in <tt>~/DRI-CVS/build/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/</tt>. <p> - To load the appropriate DRI module in your running kernel you can + To load the appropriate DRM module in your running kernel you can either use ismod and restart your X server or copy the kernel module to <tt>/lib/modules/2.4.x/kernel/drivers/char/drm/</tt> then run depmod and restart your X server. @@ -524,6 +525,9 @@ Make sure you first unload any older DRI kernel modules that might be already loaded. <p> + Note that some DRM modules require that the <tt>agpgart</tt> module + be loaded first. + <p> <sect>Normal Installation and Configuration <p> diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml index 17003440d..1659fc89b 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml @@ -5,10 +5,10 @@ <article> <title>XFree86 on Darwin and Mac OS X <author>Torrey T. Lyons -<date>11 December 2000 +<date>25 May 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.4 2000/12/12 18:54:29 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.4.4.2 2001/06/02 04:44:37 torrey Exp $ </ident> <toc> @@ -19,8 +19,7 @@ $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Darwin.sgml,v 1.4 2000/12/12 1 implementation of X Windows, has been ported to <htmlurl url="http://www.publicsource.apple.com/projects/darwin/" name="Darwin"> and <htmlurl url="http://www.apple.com/macosx/" name="Mac OS X">. This -document is -a collection of information for anyone +document is a collection of information for anyone experimenting with running X Windows on Apple's next generation operating system. Please send any comments on this page to <email/torrey@mrcla.com/. If you are also @@ -28,21 +27,36 @@ working on modifications to the Darwin X server, please let me know. <sect>Hardware Support and Configuration <p> -The Darwin port of XFree86 uses the IOKit for device driver loading -and discovery, rather than the XFree86 module loader. Because of this, -the XFree86 configuration file is not used on Darwin systems. The -descriptions found elsewhere of devices supported by XFree86 for other -operating systems also do not apply. - -<p> -XFree86 for Darwin will work with any video card that you have an -IOKit driver for. If you are running Mac OS X, this typically means -any card that has been shipped by Apple. If a card works for you with -the Mac OS X GUI, it will work on the same machine with XFree86. If -you have a pure Darwin installation, your hardware support may be -somewhat limited because Apple does not include all its hardware -drivers with Darwin. IOKit drivers are typically found in -/System/Library/Extensions/ or /Library/Extensions/. +XFree86 can be run either from the console or side by side with +Mac OS X's Aqua desktop in a full screen mode. In full screen mode +with Aqua, when the X window system is active, it takes over the entire +screen. You can switch back to the Mac OS X desktop by holding down +Command-Option-A. This key combination can be changed in the user +preferences. From the Mac OS X desktop, just click on the XDarwin +icon in the floating switch window to switch back to the X window system. +You can change this behavior in the user preferences so that clicking on +the XDarwin icon in the Dock switches as well. The full screen cooperative +mode with Aqua is known as Quartz mode, named after the Quartz 2D +compositing engine used by Aqua. + +<p> +From the console, the Darwin port of XFree86 uses the IOKit for device +driver loading and discovery, rather than the XFree86 module loader. +Because of this, the XFree86 configuration file is not used on Darwin +or Mac OS X systems. The descriptions found elsewhere of devices +supported by XFree86 for other operating systems also do not apply. +Running XFree86 from the text console is known as IOKit mode. + +<p> +XFree86 for Darwin or Mac OS X will work with any video card that +you have an IOKit driver for. If you are running Mac OS X, this +typically means any card that has been shipped by Apple. If a card works +for you with the Mac OS X GUI, it will work on the same machine with +XFree86. If you have a pure Darwin installation, you may need to download +additional third-party drivers from +<htmlurl url="http://www.publicsource.apple.com/projects/darwin/" +name="Apple's Darwin site">. IOKit drivers are typically installed in +<tt>/System/Library/Extensions/</tt> or <tt>/Library/Extensions/</tt>. <p> Multi-button and scroll wheel mouse support works well with all @@ -53,42 +67,27 @@ mice. <p> Following are instructions for building and running your own copy of XFree86. The procedure for getting your X server up and running on -Darwin and Mac OS X are very similar, but it is actually somewhat more -difficult on Mac OS X. Where there are differences I have noted them -below. Both Mac OS X Developers' Preview 4 and Mac OS X -Public Beta are covered. Note that to build XFree86 for yourself on -Mac OS X Beta, you will need to have the Developers' Tools. If -you did not receive these as a member of ADC, they are available for -download from the <htmlurl url="http://www.apple.com/developer/" -name="Apple Developer Connection">. +Darwin and Mac OS X are very similar. Where there are differences +I have noted them below. Note that to build XFree86 for yourself on +Mac OS X, you will need to install the Developers' Tools. <p> -If you want to save some time, you can use the precompiled binaries -provided by the XFree86 server at <url +If you don't feel the need to live on the cutting edge, you can save +some time and effort by using the precompiled binaries available on +the XFree86 FTP server at <url url="ftp://ftp.xfree86.org/pub/XFree86/&relvers;/binaries/Darwin/">. Follow the instructions in the <htmlurl url="http://www.xfree86.org/&relvers;/Install.html" name="Install"> -document to install it. - -<p> -This will create two new directory trees, <tt>/usr/X11R6</tt> and -<tt>/private/etc/X11</tt>. If you have the developers' tools, you may -have to run ranlib on all the libraries in <tt>/usr/X11R6/lib/*</tt> -before trying to build other X applications. +document to install it. This will create two new directory trees, +<tt>/usr/X11R6</tt> and <tt>/etc/X11</tt> For Mac OS X Quartz +support, download the optional Xquartz.tgz tarball. <p> If you get the precompiled binaries you can skip ahead to the section -on <ref id="running" name="running X windows"> - -<p> -On the other hand, if you want to build things yourself from scratch, +on <ref id="running" name="running the X window system"> On the other hand, +if you want to build things yourself from scratch, follow the directions below. -<p> -If you want to recompile the X server on Mac OS X, you will have to -make the header files as described <ref id="makeHeaders" -name="below">. - <sect1> Get the Code <p> @@ -96,11 +95,11 @@ The first thing you need to do is to get the source code from the XFree86 project. <itemize> -<item> Setup CVS: Both Darwin and Mac OS X include CVS (Concurrent +<item> Setup CVS: Both Darwin and Mac OS X include CVS (Concurrent Versions System), which is an easy way to download and keep up to date with open source code released by XFree86 and others. You do have to setup CVS properly, however, to tell it where to look. Follow the -instructions <htmlurl url="http://www.xfree86.org/cvs/" name="here"> on +<htmlurl url="http://www.xfree86.org/cvs/" name="XFree86 instructions"> on how to do this either via ssh or via the cvs pserver. <item> Now make a directory in some convenient place which will serve @@ -117,24 +116,6 @@ Wait for all the files to complete downloading. </itemize> -<sect1>Make Header Files for Mac OS X<label id="makeHeaders"> -<p> - -These next steps are not necessary if you are building XFree86 on -Darwin. Mac OS X Beta or DP4 does not include many of the -"in-progress" header files that are needed to successfully -build XFree86. The general philosophy is that at any given time, Mac -OS X will include only headers files that are "ready for prime -time" while Darwin will include a snapshot of Apple's current -efforts. So if you have access to a Darwin system, I would suggest -using this instead of Mac OS X to build XFree86. If you don't, read -the appropriate page below for an outline of what you need to do: - -<itemize> -<item><ref id="headersXBeta" name="Mac OS X Public Beta"> -<item><ref id="headersXDP4" name="Mac OS X Developers' Preview 4"> -</itemize> - <sect1> Build XFree86 <p> Once you have everything ready it is easy to build and install @@ -146,47 +127,43 @@ make World >& world.log (wait for several hours) -su root -make install >& install.log -make install.man >& man.log +sudo make install >& install.log +sudo make install.man >& man.log </verb></tscreen> -<sect>Run X Windows<label id="running"> +<sect>Run the X Window System<label id="running"> <p> -You will want to add the X windows executables to your path. Your path +You will want to add the X window executables to your path. Your path is the list of directories to be searched when you type a command. You will also want to add the man pages from XFree86 to the list of pages to be searched when you are looking for documentation. The way to do this depends on the shell you are using. With tcsh or csh add the -following two lines to a file in your home directory called <tt/.cshrc/ -(create this file if you don't have one yet): +following two lines to a file named +<tt>~/Library/init/tcsh/path</tt>: (You may need to create this file and +directory path if it does not exist already.) + <tscreen><verb> -setenv MANPATH "${MANPATH}:/usr/X11R6/man:/usr/local/man" setenv PATH "${PATH}:/usr/X11R6/bin" +setenv MANPATH "${MANPATH}:/usr/X11R6/man" </verb></tscreen> -Now type ``<tt>source ~/.cshrc;rehash</tt>'' to -get these changes to take effect. On future logins, this file will be +The next time you login or open a Terminal window, this file will be executed automatically. <p> -You are now ready to go. On Mac OS X, you have to do a few extra steps -each time you want to run X windows. You can't run XFree86 with -CoreGraphics running since they both want to control the screen. So -for Mac OS X you first need to logout. Then for Mac OS X DP4, from the -login window type ``console'' as the user name and push -login. For Mac OS X Beta, type ``>console'' as the user -name. This should shutdown CoreGraphics and bring you up with a text -console. Login again. +You are now ready to go. On Mac OS X, you can run XFree86 from the +text console or in full screen mode with Aqua. To get to the text +console in Mac OS X you need to logout and type ``>console'' as +the user name. This will shutdown Core Graphics and +bring up the console login prompt. Login again as your user. <p> -Now from the text console you can start X Windows in either Darwin or -Mac OS X by typing ``startx''. After a brief wait at least one terminal -window should pop up for you. So far it probably isn't very impressive -as you might not even have a window manager running to allow you to -move windows around. +From the text console you can start the X Window System by typing ``startx''. +After a brief wait at least one terminal window should pop up for you. +So far it probably isn't very impressive as you might not even have a +window manager running to allow you to move windows around. <p> -When you are ready to quit X windows type ``exit'' in the main +When you are ready to quit XFree86 type ``exit'' in the main terminal window or quit with the window manager if you have one running. Unfortunately the X server won't shutdown correctly and you will get an apparently frozen screen with only a spinning beachball @@ -194,25 +171,36 @@ cursor on it. Nothing you type shows up on the screen, but in fact your keystrokes are being received by the console. Type ``logout'' to return to normalcy after a brief delay. With Darwin this should put you back at the text console login prompt. With -Mac OS X, CoreGraphics will restart and you should be given a login +Mac OS X, Core Graphics will restart and you should be given a login window. <p> +To start XFree86 in Quartz mode you can launch the XDarwin application +in the <tt>/Applications</tt> folder, or from the command line type +``startx -- -quartz''. When the X window system is active, it takes over +the entire screen. You can switch back to the Mac OS X desktop by +holding down Command-Option-A. This key combination can be changed in +the user preferences. From the Mac OS X desktop, just click on the +XDarwin icon in the floating switch window to switch back to the X window +system. You can change this behavior in the user preferences so that +clicking on the XDarwin icon in the Dock switches as well. + +<p> <bf/Customize X Windows/ <p> -X windows is very customizable and you will certainly want to change -some things. There is a lot you can do to control how your windows +The X window system is very customizable and you will certainly want to +change some things. There is a lot you can do to control how your windows look, how the windows are moved, resized, etc. You will likely want to get a better window manager than twm, which is included with XFree86. The <tt>.xinitrc</tt> file in your home directory controls what -programs are run when you start X windows. You can find a sample -<tt>.xinitrc</tt> file in <tt>/private/etc/X11/xinit/xinitrc</tt>. +programs are run when you start the X window system. You can find a sample +<tt>.xinitrc</tt> file in <tt>/etc/X11/xinit/xinitrc</tt>. <p> -There are several -window managers that have been ported to Darwin. The best collection -of window managers and other X windows applications is at <htmlurl +There are several window managers that have been ported to Darwin. +The best collection of window managers and other X window clients +is at <htmlurl url="http://www.darwinfo.org/ports.shtml#X Windows" name="Darwinfo's ports page">. Another good place to look for Darwin ports in general is at <htmlurl @@ -230,195 +218,21 @@ let me know if you are interested in working on any of these issues. <bf/Things that are broken:/ <itemize> -<item>The bell is broken. +<item>The bell does not work in IOKit mode. -<item>Server shutdown problem: After quitting the X server the colored -beachball cursor reappears, but the screen never returns to the +<item>Server shutdown problem: After quitting the X server in IOKit mode, +the colored beachball cursor reappears, but the screen never returns to the console display. The console is accepting input however, so typing ``logout'' will return you to the login prompt. <item>Only one display is currently supported. -<item>Screen saver not supported. +<item>The display mode can not be changed once the X server +has started. -<item>Key repeat rate can not be adjusted. -</itemize> +<item>A screen saver is not supported. -<bf/Things I am working on:/ -<itemize> -<item> Allowing rootless use on Mac OS X -<item> Correct wake from sleep behavior </itemize> -<sect>Appendix - -<sect1>Installing IOKit Header files on Mac OS X Beta<label - id="headersXBeta"> -<p> -Here is what you need to do to be able to build XFree86 (or other -clients of IOGraphics services) on Mac OS X Public Beta. -<enum> - -<item>You need to install some more build tools that aren't included -in Mac OS X Beta, but are included in Darwin. These are needed for the -next step. Go to your development directory and type: -<tscreen><verb> -cvs checkout bootstrap_cmds -cd bootstrap_cmds -make -</verb></tscreen> -Now su to root and do a ``make install'' from the bootstrap_cmds -directory. - -<item> -The IOKit framework included with Mac OS X Beta is a little on the -wimpy side, even after installing the Developer Tools. You'll need to -rebuild it, but to do so safely we'll take advantage of the cool -directory structure of Mac OS X and put the new version in -/Library/Frameworks/. This will override the version in -/System/Library/Frameworks/. Or at least, that's where you should put -it using the new Mac OS X Beta file structure, but in fact the -compiler doesn't know this and still looks in -/Local/Library/Frameworks. (I have already filed a developer's bug -report on this.) To start we make a copy of the original. Login as -root and do the following: -<tscreen><verb> -cd /Library -mkdir -p Frameworks -cp -R /System/Library/Frameworks/IOKit.framework Frameworks/IOKit.framework -cd / -mkdir -p Local -ln -s /Library /Local/Library -</verb></tscreen> - -<item>Now you need to get a full version of the IOKit framework from -the Darwin repository. This comes as part of the kernel. So, in your -development directory again: - -<tscreen><verb> -cvs checkout xnu -cd xnu -source SETUP/setup.csh -make exporthdrs -make install -</verb></tscreen> - -The "make install" will start by assembling all the headers you need, -but then will proceed to build a new kernel. You can Control-C out of -the build once it starts compiling things if you want. Otherwise, just -be patient. - -<item> -You also need to get the IOKitUser project, which contains the user -interface to the IOKit, and merge it into the IOKit framework. From -your development directory type: -<tscreen><verb> -cvs checkout IOKitUser -</verb></tscreen> -Then you need to change the Makefile so it builds on top of the new -IOKit framework you are building. Change to the IOKitUser project -directory and edit the Makefile. Change the following line: -<tscreen><verb> -NEXTSTEP_BUILD_OUTPUT_DIR = /$(USER)/build/$(NAME) -</verb></tscreen> -to: -<tscreen><verb> -NEXTSTEP_BUILD_OUTPUT_DIR = <your xnudir>/BUILD/dst/System/Library/Frameworks -</verb></tscreen> - -Now, run ``make'' while in the IOKitUser directory. It will likely not -finish building since the IOKitUser project relies on some stuff that -Apple hasn't really made public yet, but it should finish populating -the new IOKit framework with headers and start compiling. (Strangely -enough, the headers installed in your new IOKit framework don't contain -the real header files. They are just single line files with an #import -of the file in your IOKitUser project. This works fine as long as you -don't ever delete or move your IOKitUser project. I imagine that using -``make install'' would fix this up, but you can't do this as long as the -project doesn't build correctly. So for now you can either move the -header files by hand, or make sure you leave your IOKitUser project in -place.) - -<item> -Now put the new IOKit headers into our local copy. Change to the xnu -project directory and do the following as root: -<tscreen><verb> -cd BUILD/dst/System/Library/Frameworks/ -cp -R IOKit.framework/Versions/A/Headers/* \ - /Library/Frameworks/IOKit.framework/Versions/A/Headers -</verb></tscreen> - -<item> -The System framework needs touching up a bit too. You need to copy the -libkern header files from the new System.framework. As root, go to the -xnu project directory and type: (Of course you could make a local copy -of the System framework in /Library/Frameworks/, but the additions to -the System framework are small.) -<tscreen><verb> -cd BUILD/dst/System/Library/Frameworks/System.framework/Versions/B/Headers -cp -R libkern /System/Library/Frameworks/System.framework/Headers/libkern -</verb></tscreen> -</enum> - -<sect1>Installing IOKit Header files on Mac OS X DP4<label -id="headersXDP4"> -<p> -Here is an outline of what you need to do to be able to build XFree86 -(or other clients of IOGraphics services) on Mac OS X Developers' -Preview 4. - -<enum> - -<item>Checkout, build, and install bootstrap_cmds from the CVS -repository. -<item>Checkout xnu from the CVS repository. Go to sandbox/xnu and do -the following: -<tscreen><verb> -source SETUP/setup.csh -make exporthdrs -</verb></tscreen> -<item>su to root and do the following: -<tscreen><verb> -mkdir -p /Local/Library/Frameworks -cp -R /System/Library/Frameworks/IOKit.framework /Local/Library/Frameworks -</verb></tscreen> -This will create a new local version of the IOKit framework that will -override the System version without changing the original. - -<item>You now want to merge the IOKit headers from the xnu project -into your local IOKit framework. I did this fairly tediously by hand, -but I would suggest something like: -<tscreen><verb> -cp -R sandbox/xnu/BUILD/dst/System/Library/Frameworks/IOKit.framework/Versions/A/Headers \ -/Local/Library/Frameworks/IOKit.framework/Versions/A -</verb></tscreen> -The only problem with this is that there are a few stub header files -included that are just a single line with an #import to the -appropriate place in the xnu source on your disk. This is fine as long -as you don't move your xnu project. If you do, you can copy the -original file to replace the stub. There is probably an easier way to -automatically build a clean version of the IOKit framework, but I -didn't find it. (Let me know if you do.) - -<item>There are just a few more files you need in the IOKit -framework. Checkout the IO project from CVS. Get the necessary header -files from there and put them in your new local IOKit -framework. You'll get errors when you try to build XFree86 from which -you can tell which files are needed. I also needed to make the -following patch to IOLLEvent.h. Your mileage may vary. -<tscreen><verb> -47c47 -< #include <Kernel/libkern/OSTypes.h> ---- -> #include <libkern/OSTypes.h> -</verb></tscreen> - -<item>You'll also need a few extra CoreFoundation header -files. Checkout CoreFoundation. You can make a new local version of -the CoreFoundation framework as above, or just add to the existing -one. The files you need are CFMachPort.h and CFMessagePort.h in the -RunLoop.subproj and CFStorage.h in Collections.subproj. -</enum> - </article> diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile b/xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile index c9b0477bb..334b798a9 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile @@ -3,14 +3,23 @@ XCOMM $XConsortium: Imakefile /main/16 1996/10/28 05:13:04 kaleb $ -XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile,v 3.71 2001/03/02 02:45:37 dawes Exp $ +XCOMM $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Imakefile,v 3.71.2.1 2001/06/01 18:09:48 dawes Exp $ #include <Server.tmpl> #include <lnxdoc.rules> +/* Set this to YES if the RELNOTES file is up to date */ +#ifndef BuildRelnotes +#define BuildRelnotes NO +#endif + +#if BuildRelnotes +RELNOTES=RELNOTES.sgml +#endif + SGMLDEPENDS = defs.ent MANSGMLDEPENDS = mdefs.ent - INDEXLIST = README.sgml RELNOTES.sgml Status.sgml LICENSE.sgml Install.sgml \ + INDEXLIST = README.sgml $(RELNOTES) Status.sgml LICENSE.sgml Install.sgml \ DESIGN.sgml Versions.sgml \ mouse.sgml fonts.sgml DRI.sgml DRIcomp.sgml dps.sgml \ Darwin.sgml isc.sgml LynxOS.sgml NetBSD.sgml OpenBSD.sgml \ @@ -105,7 +114,9 @@ LinuxDocTarget(LICENSE) LinuxDocTargetLong(QStart.sgml,QuickStart.doc,QuickStart) #endif LinuxDocTarget(README) +#if BuildRelnotes LinuxDocTarget(RELNOTES) +#endif LinuxDocTarget(Status) /* Other docs */ @@ -149,6 +160,8 @@ clean:: FORMATTEDDIR = .. +#if BuildRelnotes /* Update RELNOTES at top level */ UpdateFormattedDoc(RELNOTES,$(TOP)) +#endif diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml index c4b02d73d..97b5da3e3 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml @@ -6,10 +6,10 @@ <title>Installation Details for XFree86™ &relvers; <author>The XFree86 Project, Inc -<date>15 December 2000 +<date>1 June 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml,v 1.11 2001/03/02 17:40:48 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Install.sgml,v 1.11.2.2 2001/06/01 18:09:48 dawes Exp $ </ident> <abstract> @@ -80,14 +80,31 @@ for you to download. If you are careful with this step you will save yourself a lot time and trouble from NOT downloading an incompatible distribution. -<bf>NOTE</bf>: the Xinstall.sh script must be downloaded in binary mode, -otherwise it won't run correctly. If you get lots of "command not found" -messages when you try to run it, then it is most likely because the -script wasn't downloaded in binary mode. Some web browsers won't do -this for files of that name, so we also have a copy of it called -"<tt>Xinstall.bin</tt>", and most browsers should download that correctly. -When downloading it under this name, select "save as" on your browser, -and save the file under the name "<tt>Xinstall.sh</tt>". +<bf>NOTES</bf>: + +<itemize> + <item>The Xinstall.sh script must be downloaded in binary mode, + otherwise it won't run correctly. If you get lots of "command + not found" messages when you try to run it, then it is most + likely because the script wasn't downloaded in binary mode. + Some web browsers won't do this for files of that name, so we + also have a copy of it called "<tt>Xinstall.bin</tt>", and most + browsers should download that correctly. When downloading it + under this name, select "save as" on your browser, and save the + file under the name "<tt>Xinstall.sh</tt>". + + <item>The Xinstall.sh script requires some system commands and + utilities to function correctly. While most systems will have + these, some Linux installations may not. If you find that the + script is failing because of some missing system command, you + will need to install it before you can continue. If you don't + know how to do this, then we recommend that you obtain this + version of XFree86 from your Operating System distributor. + + <item>Always use the version of the Xinstall.sh script that's provided + with the release you're installing. Older versions of the script + may not install newer releases correctly. +</itemize> Once you're run the <tt>Xinstall.sh</tt> script and found which binary <![ %updaterel; [update ]]>distribution is suitable for your system, @@ -98,27 +115,27 @@ will complain. <![ %fullrel [ <quote><verb> -1. Xinstall.sh The installer script -2. extract The utility for extracting tarballs -3. Xbin.tgz X clients/utilities and run-time libraries -4. Xlib.tgz Some data files required at run-time -5. Xman.tgz Manual pages -6. Xdoc.tgz XFree86 documentation -7. Xfnts.tgz Base set of fonts -8. Xfenc.tgz Base set of font encoding data -9. Xetc.tgz Run-time configuration files -10. Xvar.tgz Run-time data -11. Xxserv.tgz XFree86 X server -12. Xmod.tgz XFree86 X server modules +1. Xinstall.sh The installer script +2. extract The utility for extracting tarballs +3. Xbin.tgz X clients/utilities and run-time libraries +4. Xlib.tgz Some data files required at run-time +5. Xman.tgz Manual pages +6. Xdoc.tgz XFree86 documentation +7. Xfnts.tgz Base set of fonts +8. Xfenc.tgz Base set of font encoding data +9. Xetc.tgz Run-time configuration files +10. Xvar.tgz Run-time data +11. Xxserv.tgz XFree86 X server +12. Xmod.tgz XFree86 X server modules </verb></quote> ]]> <![ %updaterel [ <quote><verb> -1. Xinstall.sh The installer script -2. extract The utility for extracting tarballs -3. Xupdate.tgz Updated files except X server drivers -4. Xdrivers.tgz Updated X server drivers +1. Xinstall.sh The installer script +2. extract The utility for extracting tarballs +3. Xupdate.tgz Updated files except X server drivers +4. Xdrivers.tgz Updated X server drivers </verb></quote> ]]> @@ -145,23 +162,21 @@ NOTES: </itemize> <![ %fullrel [ -The following thirteen (13) tarballs are optional. You should download +The following eleven (11) tarballs are optional. You should download the ones you want to install. <quote><verb> -1. Xfsrv.tgz Font server -2. Xnest.tgz Nested X server -3. Xprog.tgz X header files, config files and compile-time libs -4. Xprt.tgz X Print server -5. Xvfb.tgz Virtual framebuffer X server -6. Xf100.tgz 100dpi fonts -7. Xfcyr.tgz Cyrillic fonts -8. Xflat2.tgz Latin-2 fonts -9. Xfnon.tgz Some large bitmap fonts -10. Xfscl.tgz Scalable fonts (Speedo and Type1) -11. Xhtml.tgz HTML version of the documentation -12. Xps.tgz PostScript version of the documentation -13. Xjdoc.tgz Documentation in Japanese +1. Xfsrv.tgz Font server +2. Xnest.tgz Nested X server +3. Xprog.tgz X header files, config files and compile-time libs +4. Xprt.tgz X Print server +5. Xvfb.tgz Virtual framebuffer X server +6. Xf100.tgz 100dpi fonts +7. Xfcyr.tgz Cyrillic fonts +8. Xfscl.tgz Scalable fonts (Speedo and Type1) +9. Xhtml.tgz HTML version of the documentation +10. Xps.tgz PostScript version of the documentation +11. Xjdoc.tgz Documentation in Japanese </verb></quote> NOTES: @@ -383,6 +398,7 @@ ln -s /etc/X11/xdm /usr/X11R6/lib/X11 ln -s /etc/X11/xinit /usr/X11R6/lib/X11 ln -s /etc/X11/xsm /usr/X11R6/lib/X11 ln -s /etc/X11/xserver /usr/X11R6/lib/X11 +chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK /sbin/ldconfig /usr/X11R6/lib # For Linux /sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD /usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc @@ -461,6 +477,7 @@ Once that's done, the main part of the installation can be done: ./extract -C /usr/X11R6 `pwd`/X[a-df-uw-z]*.tgz ./extract -C /usr/X11R6 Xvfb.tgz # If you are installing Xvfb ./extract -C /var Xvar.tgz +chmod ug-w /usr/X11R6/lib # Make sure the permissions are OK /sbin/ldconfig /usr/X11R6/lib # For Linux /sbin/ldconfig -m /usr/X11R6/lib # For FreeBSD, NetBSD, OpenBSD /usr/X11R6/bin/mkfontdir /usr/X11R6/lib/X11/fonts/misc diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml index 47f9d66d4..08618a679 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml @@ -12,7 +12,7 @@ Matthieu Herrb <Date>Last modified on: 3 March 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml,v 3.60 2001/03/04 09:47:34 herrb Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/NetBSD.sgml,v 3.60.2.1 2001/06/01 18:09:48 dawes Exp $ </ident> <toc> @@ -56,8 +56,10 @@ this file and we'll revise it. <sect>New OS dependent features <p> +<![ %haverelnotes [ See the <htmlurl url="RELNOTES.html" name="Release Notes"> for non-OS dependent new features in XFree86 &relvers;. +]]> <sect1>New OS dependent features in 4.0.2 <p> diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml index 55b0f8198..c476cedf1 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml @@ -5,6 +5,7 @@ <!ENTITY % threediffs 'IGNORE'> <!-- patch is split into three diff files --> <!ENTITY % fourdiffs 'INCLUDE'> <!-- patch is split into four diff files --> <!ENTITY % difftar 'INCLUDE'> <!-- patch also contains a tarball --> +<!ENTITY % removefiles 'INCLUDE'> <!-- patching requires removing some files --> ]> @@ -12,10 +13,10 @@ <title>README for XFree86&tm; &relvers; <author>The XFree86 Project, Inc -<date>15 December 2000 +<date>2 June 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.113 2001/03/16 22:13:19 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.113.2.3 2001/06/02 16:17:40 dawes Exp $ </ident> <abstract> @@ -33,8 +34,9 @@ operating systems on Intel and other platforms. <![ %updaterel [ XFree86 &relvers; is the &whichupdaterel; update to &fullrelvers;, -the &whichfullrel; full release in the <![ %earlyrel; [new]]> XFree86 -4 series. +the &whichfullrel; full release in the +<![ %earlyrel; [new]]> +XFree86 4 series. Update releases are taken from a stable/maintenance branch. They are designed to be installed on top of the full release that they are @@ -44,8 +46,9 @@ stability. ]]> <![ %fullrel [ -XFree86 &relvers; is the &whichfullrel; full release in the <![ %earlyrel; -[new]]> XFree86 4 series. +XFree86 &relvers; is the &whichfullrel; full release in the +<![ %earlyrel; [new]]> +XFree86 4 series. ]]> <p> @@ -77,8 +80,10 @@ video hardware are available. Please check the <htmlurl name="Driver Status document" url="Status.html"> first to see whether your hardware is supported before upgrading to the 4.x series. +<![ %haverelnotes [ Specific release enhancements can be viewed in the <htmlurl name="Release Notes" url="RELNOTES.html">. +]]> The XFree86 version numbering system has had some changes as of the 4.0.2 release. Information about this can be found in the @@ -238,7 +243,7 @@ The source for version &fullrelvers; is split into three tarballs: <tt>X&fullsrcvers;src-1.tgz</tt>, <tt>X&fullsrcvers;src-2.tgz</tt>, <tt>X&fullsrcvers;src-3.tgz</tt>. The first contains everything except the fonts and general X11 documentation. It is sufficient for building -XFree86 is you already have a set of fonts. The second contains the +XFree86 if you already have a set of fonts. The second contains the fonts and the source for the general X11 documentation. The third contains the general X11 documentation in hardcopy format. @@ -339,14 +344,28 @@ gzip -d < &prevfullrelvers;-&fullrelvers;.diff3.gz | patch -p0 -E gzip -d < &prevfullrelvers;-&fullrelvers;.diff4.gz | patch -p0 -E </verb></tscreen> <![ %difftar; [ +<![ %removefiles; [ +<tscreen><verb> +rm -f xc/programs/xieperf/images/image.012 +rm -fr xc/fonts/bdf/latin2 +rm -fr xc/fonts/bdf/100dpi +rm -fr xc/fonts/bdf/75dpi +</verb></tscreen> +]]> <tscreen><verb> gzip -d < &fullrelvers;.tgz | tar vxf - </verb></tscreen> ]]> ]]> -The contrib part of the distribution has been folded into the main -source tree, so a separate contrib tarball is no longer required. +<![ %prevrelwasupdate; [ +Patches might also be available relative to &prevrelvers;. If so, the +instructions for applying them are the same, except that you should start +with a clean &prevrelvers; source tree. +]]> + +The contrib part of the distribution was folded into the main source +tree a while ago, so a separate contrib tarball is not required. To format the XFree86 documentation use the latest version of our doctools package available as <tt>doctools-&doctoolsvers;.tgz</tt>. diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml index dbc5d5bd4..3c041e23d 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml @@ -9,7 +9,7 @@ <date>17 December 2000 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.60 2001/03/02 17:40:48 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.60.2.1 2001/06/02 16:28:25 torrey Exp $ </ident> <abstract> @@ -92,9 +92,10 @@ don't have enough space to cover them all here. <sect1>X server <p> <itemize> - <item>Darwin/Mac OS X is now supported and the X server runs on PowerPC. - The X server for this platform is called "Xdarwin", and its - installation and configuration is different from the "XFree86" + <item>Darwin/Mac OS X is now supported on PowerPC and Intel/x86. The X + server runs from the console or in cooperation with the Mac OS X + Aqua GUI. The X server for this platform is called "XDarwin", and + its installation and configuration is different from the "XFree86" server used on other platforms. Please read the <htmlurl url="Darwin.html" name="XFree86 on Darwin and Mac OS X"> document for further information. diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml index 61b42d3c2..6f91321b3 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml @@ -6,10 +6,10 @@ <title>Driver Status for XFree86™ &relvers; <author>The XFree86 Project, Inc -<date>4 December 2000 +<date>1 June 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml,v 1.29 2001/04/04 01:34:18 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/Status.sgml,v 1.29.2.2 2001/06/01 18:09:49 dawes Exp $ </ident> <abstract> @@ -18,7 +18,7 @@ This document provides information about the status of the driver and hardware support in XFree86 &relvers; compared with that in XFree86 &legacyvers;. Please send updates for this document to <email>fixes@xfree86.org</email>. Please do not send requests for -information or support to that address. +information or support to that address (they will not be answered). </abstract> @@ -157,7 +157,7 @@ other architectures known to work on (e.g., Alpha, PPC), etc. All chips supported in &legacyvers; are supported in &relvers; except for Mach8 and some old Mach32 chips. The support in &relvers; is, however, unaccelerated for all chips except the - Mach64, Rage and Rage 128 variants. + Mach64, Rage, Rage 128 and Radeon variants. </descrip> diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml b/xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml index 2cdc21479..3e10a52a6 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml @@ -8,10 +8,10 @@ <title> Information for Chips and Technologies Users <author> David Bateman (<email>dbateman@club-internet.fr</email>), Egbert Eich (<email>eich@xfree86.org</email>) -<date> 14th June 2000 +<date> 1st January 2001 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml,v 3.33 2000/12/02 21:52:22 dbateman Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/chips.sgml,v 3.36 2001/05/19 00:35:42 dawes Exp $ </ident> <!-- Table of contents --> @@ -276,15 +276,6 @@ Option "HWclocks" programmable clock makes this option obsolete and so it's use isn't recommended. It is completely ignored for HiQV chipsets. <tag> -Option "UseVclk1" -</tag> - The HiQV series of chips have three programmable clocks. The - first two are usually loaded with 25.175 and 28.322MHz for - VGA backward compatibility, and the third is used as a fully - programmable clock. On at least one system (the Inside 686 LCD/S - single board computer) the third clock is unusable. This option - forces the use of VClk1 as the programmable clock. -<tag> TextClockFreq 25.175 </tag> Except for the HiQV chipsets, it is impossible for the server to read @@ -311,6 +302,16 @@ Option "FPClock32" "65.0MHz" less, 16, 24 or 32bpp LCD panel clocks, where the options above set the clocks to 65MHz. <tag> +Option "CRTClkIndx" "2" +Option "FPClkIndx" "1" +</tag> + The HiQV series of chips have three programmable clocks. The + first two are usually loaded with 25.175 and 28.322MHz for + VGA backward compatibility, and the third is used as a fully + programmable clock. On at least one system (the Inside 686 LCD/S + single board computer) the third clock is unusable. These options + can be used to force a particular clock index to be used +<tag> Option "MMIO" </tag> This has a different effect depending on the hardware on which it @@ -318,12 +319,14 @@ Option "MMIO" BitBLT engine and is only usable with PCI buses. It is enabled by default for 65545 machines since the blitter can not be used otherwise. The HiQV series of chipsets must use MMIO with their - BitBLT engines, and so this is enabled by default. However the - 690xx chipsets can use MMIO for all communications with the video - processor. So using this option on a 690xx chipset forces them - to use MMIO for all communications. This only makes sense when - the 690xx is on a PCI bus so that normal PIO can be disabled. - (WARNING!! 690xx MMIO is untested) + BitBLT engines, and so this is enabled by default. +<tag> +Option "FullMMIO" +</tag> + The 690xx chipsets can use MMIO for all communications with the + video processor. So using this option on a 690xx chipset forces + them to use MMIO for all communications. This only makes sense + when the 690xx is on a PCI bus so that normal PIO can be disabled. <tag> Option "SuspendHack" </tag> @@ -442,6 +445,22 @@ Option "VideoKey" "255" 8bit depth, 0 to 32,767 for 15bit depth, etc. This option might be used if the default video overlay key causes problems. <tag> +Option "DualRefresh" +</tag> + The 69030 chipset has independent display channels, that can be + configured to support independent refresh rates on the flat panel + and on the CRT. The default behaviour is to have both the flat panel + and the CRT use the same display channel and thus the same refresh + rate. This option forces the two display channels to be used, giving + independent refresh rates. +<tag> +Option "Crt2Memory" "2048" +</tag> + The ct69030 supports dual-head display. By default the two display + share equally the available memory. This option forces the second + display to take a particular amount of memory. Please read the + section below about dual-head display. +<tag> Option "XaaNoScreenToScreenCopy", Option "XaaNoSolidFillRect", Option "XaaNoSolidHorVertLine", @@ -532,6 +551,12 @@ driver you'll needed to considered several points they specified after a suspend/resume or LCD/CRT switch. For a complete discussion on the dot clock limitations, see the next section. +<tag> * Dual-head display </tag> + Dual-head display has two effects on the modelines. Firstly, + the memory requirements of both heads must fit in the available + memory. Secondly, the memory bandwidth of the video processor is + shared between the two heads. Hence the maximum dot-clock might + need to be limited. </descrip> The driver is capable of driving both a CRT and a flat panel @@ -572,6 +597,105 @@ The NEC Versa 4080 just needs the "FixPanelSize" option. To the best of my knowledge no machine with a HiQV needs the "UseModeline" or "FixPanelSize" options. +<sect> Dual Display Channel<p> + +XFree86 releases later than 4.1.0 support dual-channel display on the ct69030. +This support can be used to give a single display image on two screen with +different refresh rates, or entirely different images on the two displays. + +Dual refresh rate display can be selected with the "<tt>DualRefresh</tt>" +option described above. However to use the dual-head support is slightly +more complex. Firstly, the ct69030 chipset must be installed on a PCI bus. This +is a driver limitation that might be relaxed in the future. In addition the +device, screen and layout sections of the "<tt>XF86Config</tt>" must be +correctly configured. A sample of an incomplete "<tt>XF86Config</tt>" is +given below + +<quote><verb> +Section "Device" + Identifier "Chips and Technologies - Pipe A" + Driver "chips" + BusID "PCI:0:20:0" + Screen 0 +EndSection + +Section "Device" + Identifier "Chips and Technologies - Pipe B" + Driver "chips" + BusID "PCI:0:20:0" + Screen 1 +EndSection + +Section "Screen" + Identifier "Screen 0" + Device "Chips and Technologies - Pipe A" + Monitor "generic LCD" + + SubSection "Display" + Depth 16 + Modes "1024x768" + EndSubsection +EndSection + +Section "Screen" + Identifier "Screen 1" + Device "Chips and Technologies - Pipe B" + Monitor "generic CRT" + + SubSection "Display" + Depth 16 + Modes "1024x768" + EndSubsection +EndSection + +Section "ServerLayout" + Identifier "Main Layout" + Screen "Screen 0" + Screen "Screen 1" RightOf "Screen 0" + InputDevice "Mouse1" "CorePointer" + InputDevice "Keyboard1" "CoreKeyboard" +EndSection +</verb></quote> + +The device section must include the PCI BusID. This can be found from the +log file of a working single-head installation. For instance, the line + +<quote><verb> +(--) PCI:*(0:20:0) C&T 69030 rev 97, Mem @ 0xed000000/24 +</verb></quote> + +appears for the case above. Additionally, the "<tt>Screen</tt>" option +must appear in the device section. It should be noted that if a flat +panel is used, this it must be allocated to "<tt>Screen 0</tt>". + +The server can then be started with the "<tt>+xinerama</tt>" option +as follows + +<quote><verb> +startx -- +xinerama +</verb></quote> + +For more information, read the Xinerama documentation. + +It should be noted that the dual channel display options of the 69030 +require the use of additional memory bandwidth, as each display channel +independently accesses the video memory. For this reason, the maximum +colour depth and resolution that can be supported in a dual channel mode +will be reduced compared to a single display channel mode. However, as +the driver does not prevent you from using a mode that will exceed the +memory bandwidth of the 69030, but a warning like + +<quote><verb> +(WW) Memory bandwidth requirements exceeded by dual-channel +(WW) mode. Display might be corrupted!!! +</verb></quote> + +If you see such display corruption, and you have this warning, your choices +are to reduce the refresh rate, colour depth or resolution, or increase the +speed of the memory clock with the the "<tt>SetMClk</tt>" option described +above. Note that increasing the memory clock also has its own problems as +described above. + <sect> The Full Story on Clock Limitations <p> There has been much confusion about exactly what the clock limitations @@ -623,19 +747,29 @@ resulting in drawing errors on the screen. The formula to determine the maximum usable dotclock on the HiQV series of chips is <verb> +Max dotclock = min(MaxDClk, 0.70 * 8 * MemoryClk / (BytesPerPixel + + (isDSTN == TRUE ? 1 : 0))) +</verb> + +if you chips is a 69030 or 69000 or + +<verb> Max dotclock = min(MaxDClk, 0.70 * 4 * MemoryClk / (BytesPerPixel + (isDSTN == TRUE ? 1 : 0))) </verb> -which says that there are two limits on the dotclock. One the overall -maximum, and another due to the available memory bandwidth of the chip. -For the memory bandwidth 4 bytes are transfered every clock cycle (Hence -the 4), but after accounting for the RAS/CAS signaling only about 70% -of the bandwidth is available. The whole thing is divided by the bytes -per pixel, plus an extra byte if you are using a DSTN. The extra byte -with DSTN screens is used for the frame buffering/acceleration in these -screens. So for the various Chips and Technologies chips the maximum -specifications are + +otherwise. This effectively means that there are two limits on the +dotclock. One the overall maximum, and another due to the available +memory bandwidth of the chip. The 69030 and 69000 have a 64bit memory +bus and thus transfer 8 bytes every clock thus (hence the 8), while +the other HiQV chipsets are 32bit and transfer 4 bytes per clock cycle +(hence the 4). However, after accounting for the RAS/CAS signaling +only about 70% of the bandwidth is available. The whole thing is +divided by the bytes per pixel, plus an extra byte if you are using a +DSTN. The extra byte with DSTN screens is used for the frame +buffering/acceleration in these screens. So for the various Chips and +Technologies chips the maximum specifications are <verb> Max DClk MHz Max Mem Clk MHz @@ -666,8 +800,8 @@ clocks for the chips are 65554 94.5 77 51.33 77 51.33 38.5 65555 110 77 51.33 77 51.33 38.5 68554 110 77 51.33 77 51.33 38.5 -69000 135 116.2 77.47 116.2 77.47 58.1 -69030 170 140 93.33 140 93.33 70 +69000 135 135 135 135 135 116.2 +69030 170 170 170 170 170 140 </verb> If you exceed the maximum set by the memory clock, you'll get corruption @@ -841,9 +975,9 @@ video processor beyond it capabilities won't cause damage. However, 8 and 24 bit colour depths seem to work fine. <tag> My ct69030 machine locks up when starting XFree</tag> The ct69030 chipset introduced a new dual channel architecture. In its - current form, XFree can not take advantage of this second display + current form, XFree86 can not take advantage of this second display channel. In fact if the video BIOS on the machine sets the ct69030 - to a dual channel mode by default, XFree will lockup hard at this + to a dual channel mode by default, XFree86 will lockup hard at this point. The solution is to use the BIOS setup to change to a single display channel mode, ensuring that both the IOSS and MSS registers are set to a single channel mode. Work is underway to fix this. @@ -885,7 +1019,8 @@ video processor beyond it capabilities won't cause damage. 65.10MHz is not. So for unexplained problems not addressed above, please try to alter the clock you are using slightly, say in steps of 0.05MHz and see if the problem goes away. Alternatively, using the - "<tt>UseVClk1</tt>" option with HiQV chips might also help. + "<tt>CRTClkIndx</tt>" or "<tt>FPClkIndx</tt>" option with HiQV chips might + also help. For other screen drawing related problems, try the "<tt>NoAccel</tt>" or diff --git a/xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent b/xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent index f8a787438..cf77e69b0 100644 --- a/xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent +++ b/xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent @@ -1,17 +1,17 @@ -<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent,v 1.16 2001/02/09 04:15:36 dawes Exp $ --> +<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/defs.ent,v 1.16.2.3 2001/06/02 16:17:40 dawes Exp $ --> <!-- shared entity definitions for the XFree86 documentation --> <!-- XFree86 version string --> -<!ENTITY relvers CDATA "4.0.2"> -<!ENTITY prevrelvers CDATA "4.0.1"> -<!ENTITY fullrelvers CDATA "4.0.2"> -<!ENTITY prevfullrelvers CDATA "4.0.1"> -<!ENTITY srcvers CDATA "402"> -<!ENTITY prevsrcvers CDATA "401"> -<!ENTITY fullsrcvers CDATA "402"> -<!ENTITY prevfullsrcvers CDATA "401"> -<!ENTITY whichfullrel CDATA "third"> +<!ENTITY relvers CDATA "4.1.0"> +<!ENTITY prevrelvers CDATA "4.0.3"> +<!ENTITY fullrelvers CDATA "4.1.0"> +<!ENTITY prevfullrelvers CDATA "4.0.2"> +<!ENTITY srcvers CDATA "410"> +<!ENTITY prevsrcvers CDATA "403"> +<!ENTITY fullsrcvers CDATA "410"> +<!ENTITY prevfullsrcvers CDATA "402"> +<!ENTITY whichfullrel CDATA "fourth"> <!ENTITY whichupdaterel CDATA "none"> <!-- Version of the most recent 3.3.x release --> @@ -30,8 +30,12 @@ <!ENTITY % snapshot 'IGNORE'> <!ENTITY % release 'INCLUDE'> <!ENTITY % firstrel 'IGNORE'> -<!ENTITY % earlyrel 'INCLUDE'> +<!ENTITY % earlyrel 'IGNORE'> <!ENTITY % laterrel 'INCLUDE'> <!ENTITY % fullrel 'INCLUDE'> <!ENTITY % updaterel 'IGNORE'> +<!ENTITY % prevrelwasupdate 'INCLUDE'> + +<!-- Set this to INCLUDE when references to the RELNOTES are to be included --> +<!ENTITY % haverelnotes 'IGNORE'> |