diff options
Diffstat (limited to 'sgml/RELNOTES.sgml')
| -rw-r--r-- | sgml/RELNOTES.sgml | 569 |
1 files changed, 87 insertions, 482 deletions
diff --git a/sgml/RELNOTES.sgml b/sgml/RELNOTES.sgml index 2b8dafd..c80f3f5 100644 --- a/sgml/RELNOTES.sgml +++ b/sgml/RELNOTES.sgml @@ -6,10 +6,10 @@ <title>Release Notes for XFree86™ &relvers; <author>The XFree86 Project, Inc -<date>23 November 2003 +<date>18 December 2003 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.87 2003/12/03 02:12:19 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.89 2003/12/19 04:26:12 dawes Exp $ </ident> <abstract> @@ -115,17 +115,10 @@ don't have enough space to cover them all here. <p> <itemize> -<item>[OLD] ATI Radeon 9x00 2D support added, and 3D support added for the - Radeon 8500, 9000, 9100, and M9. The 3D support for the Radeon - now includes hardware TCL. - -<item>[OLD] Support added to the i810 driver for Intel 845G, 852GM, 855GM - and 865G integrated graphics chipsets, including 2D, 3D (DRI) - and XVideo. Support for the 830M has been improved, and XVideo - support added. - -<item>[OLD] National Semiconductor SC1x00, GX1, and GX2 chipset support added - with the "nsc" driver. +<item>Several stability issues with the support for the Intel 830M, + 845G, 852GM, 855GM and 865G integrated graphics chipsets have been + fixed. Some limitations related to the driver's use of the video + BIOS remain, especially for some laptops. <item>The nv driver for NVIDIA cards has been updated as follows: @@ -160,16 +153,7 @@ don't have enough space to cover them all here. </itemize> -<item>[OLD] The s3virge driver now has support for double scan modes on the DX - (with XVideo disabled). - -<item>[OLD] Updates to the savage driver, including fixing problems with the - TwisterK, and problems with incorrect memory size detection. - -<item>[OLD] 2D acceleration added for the Trident CyberBladeXP/Ai1 chipsets. - -<item>[OLD] Support for big endian architectures has been added to the C&T - driver. +<item>A new driver for several VIA integrated graphics chipsets has been added. <item>Various updates and bug fixes have been made to most other drivers. @@ -183,9 +167,6 @@ don't have enough space to cover them all here. auto-detecting the device node to use, making it unnecessary to supply this information in the XF86Config file in most cases. -<item>[OLD] Several new input drivers have been added, including tek4957, - jamstudio (js_x), fpit, palmax, and ur98 (Linux only). - </itemize> <sect1>IPv6 support @@ -393,19 +374,11 @@ scroll-back(1, page-2) <itemize> <item>FreeType2 updated to version 2.1.4. -<item>[OLD] The "freetype" X server font backend has undergone a partial rewrite. - The new version is based on FreeType 2, and handles TrueType - (including OpenType/TTF), OpenType/CFF and Type 1 fonts. The old - "type1" backend is now deprecated, and is only used for CIDFonts - by default. - -<item>[OLD] A new utility called "mkfontscale", which builds fonts.scale files, - has been added. - -<item>[OLD] There has been a significant reworking of the XKB support to allow - multi-layout configurations. Multi-layout configurations provide - a flexible way of supporting multiple language layouts and switching - between them. +<item>The "freetype" X server font backend has been updated by the + <url name="After X-TT Project" url="http://x-tt.sourceforge.jp/"> to + include the functionality previously provided by the "xtt" backend, + and to fix some bugs. The "xtt" backend will be dropped in the + next release in favour of the updated unified "freetype" backend. </itemize> @@ -413,36 +386,25 @@ scroll-back(1, page-2) <p> <itemize> -<item>[OLD] Updates for Darwin/Mac OS X, including: +<item>On Mac OS X, the appropriate backend drawing code is now dynamically + loaded at runtime. This reduces the X server's memory footprint. + In rootless mode, Apple's Xplugin library is used where available. + (Xplugin is included as part of Mac OS X on Panther.) With Xplugin, + XDarwin provides identical performance to Apple's X11, including + the following improvements over 4.3: <itemize> - <item>Indirect GLX acceleration added. - <item>Smaller memory footprint and faster 2-D drawing in rootless - mode. - <item>Full screen mode now uses shadowfb for much faster 2-D drawing. - <item>Native fonts can be used on MacOS X. + <item>Added direct GLX rendering with thread support. + <item>Faster 2-D drawing. + <item>Added support for the Apple-WM extension so XDarwin interoperates + with quartz-wm. </itemize> +<item>On Darwin, IOKit mode now uses shadowfb for much faster drawing. + <item>Various GNU/Hurd support updates. <item>Experimental support added for GNU/KFreeBSD and GNU/KNetBSD systems. -<item>[OLD] Various Cygwin support updates, including an experimental rootless - X server for Cygwin/XFree86. - -<item>[OLD] AMD AMD64 support (primarily for Linux so far) has been added. - -<item>[OLD] Support added for OpenBSD/sparc64. - -<item>[OLD] Major OS/2 support updates. - -<item>[OLD] Major SCO OpenServer updates. - -<item>[OLD] Multi-head support has been added for 460GX-based Itanium systems, - and for ZX1-based Itanium2 systems. - -<item>[OLD] Experimental support for SunOS/Solaris on UltraSPARC systems. - - </itemize> A more complete list of changes can be found in the CHANGELOG that is @@ -535,6 +497,8 @@ XFree86 &relvers; includes the following video drivers: <tabrow><tt>trident</tt><colsep>Trident<colsep><htmlurl name="trident(4)" url="trident.4.html"></tabrow> <tabrow><tt>tseng</tt><colsep>Tseng Labs<colsep> </tabrow> + <tabrow><tt>via</tt><colsep>VIA<colsep><htmlurl + name="via(4)" url="via.4.html"></tabrow> <tabrow><tt>vesa</tt><colsep>VESA<colsep><htmlurl name="vesa(4)" url="vesa.4.html"></tabrow> <tabrow><tt>vga</tt><colsep>Generic VGA<colsep><htmlurl @@ -570,6 +534,8 @@ XFree86 &relvers; includes the following input drivers: <!-- <tabrow><tt>acecad</tt><colsep>AceCad<colsep> </tabrow> --> + <tabrow><tt>aiptek(*)</tt><colsep>Aiptek USB tablet<colsep><htmlurl + name="aiptek(4)" url="aiptek.4.html"></tabrow> <tabrow><tt>calcomp</tt><colsep>Calcomp<colsep> </tabrow> <tabrow><tt>citron</tt><colsep>Citron<colsep><htmlurl name="citron(4)" url="citron.4.html"></tabrow> @@ -578,10 +544,9 @@ XFree86 &relvers; includes the following input drivers: name="dmc(4)" url="dmc.4.html"></tabrow> <tabrow><tt>dynapro</tt><colsep>Dynapro<colsep> </tabrow> <tabrow><tt>elographics</tt><colsep>EloGraphics<colsep> </tabrow> - <tabrow><tt>elographics</tt><colsep>EloGraphics<colsep> </tabrow> <tabrow><tt>fpit</tt><colsep>Fujitsu Stylistic Tablet PCs<colsep><htmlurl name="fpit(4)" url="fpit.4.html"></tabrow> - <tabrow><tt>hyperpen</tt><colsep>HyperPen<colsep> </tabrow> + <tabrow><tt>hyperpen</tt><colsep>Aiptek HyperPen 6000<colsep> </tabrow> <tabrow><tt>js_x</tt><colsep>JamStudio pentablet<colsep><htmlurl name="js_x(4)" url="js_x.4.html"></tabrow> <tabrow><tt>kbd</tt><colsep>generic keyboards (alternate)<colsep><htmlurl @@ -612,35 +577,32 @@ Drivers marked with (*) are available for Linux only. <sect>Overview of XFree86 4.x. <p> -Unlike XFree86 3.3.x where there are multiple X server binaries, each -of which drive different hardware, XFree86 &relvers; has a single X -server binary called <tt>XFree86</tt>. 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.x has a single X server binary called <tt>XFree86</tt>. This +binary can either have one or more video and input drivers linked in +statically, or, more usually, dynamically load the video drivers, input +drivers, and other modules that are needed. XFree86 &relvers; has X server support for most UNIX® 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 planned for future releases. +operating systems on Intel/x86 platforms, plus support for Linux and +some BSD OSs on Alpha, PowerPC, IA-64, AMD64, Sparc, and Mips platforms, +and for Darwin on PowerPC. Work on support for additional architectures +and operating systems is in progress, and is planned for future releases. <sect1>Loader and Modules <p> -The XFree86 X server has a built-in run-time loader, donated by <url -name="Metro Link" url="http://www.metrolink.com">. This loader can load -normal object files and libraries in most of the commonly used formats. -Since the loader doesn't rely on an operating system's native dynamic -loader support, it works on platforms that don't provide this feature, -and makes it possible for the modules to be operating system independent -(although not, of course, independent of CPU architecture). This means -that a module compiled on Linux/x86 can be loaded by an -X server running on Solaris/x86, or FreeBSD, or even OS/2. -<p> -One of the -main benefits of this loader is that when modules are updated, 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 XFree86 X server has a built-in run-time loader developed from code +donated by <url name="Metro Link" url="http://www.metrolink.com">. This +loader can load normal object files and libraries in most of the commonly +used formats. Since the loader doesn't rely on an operating system's +native dynamic loader support, it works on platforms that don't provide +this feature, and makes it possible for the modules to be operating +system independent (although not, of course, independent of CPU +architecture). This means that a module compiled on Linux/x86 can be +loaded by an X server running on Solaris/x86, or FreeBSD, or even OS/2. + +One of the main benefits of this loader is that when modules are +updated, they do not need to be recompiled for every different operating +system. The loader in version &relvers; has support for Intel (x86), Alpha and PowerPC platforms. It also has preliminary support for Sparc platforms. @@ -649,11 +611,13 @@ The X server makes use of modules for video drivers, X server extensions, font rasterisers, input device drivers, framebuffer layers (like mfb, cfb, etc), and internal components used by some drivers (like XAA), -The module interfaces (API and ABI) used in this release is still subject +The module interfaces (API and ABI) used in this release is subject to change without notice. While we will attempt to provide backward compatibility for the module interfaces as of the 4.0 release (meaning that 4.0 modules will work with future core X server binaries), we cannot -guarantee this. +guarantee this. Compatibility in the other direction is explicitly +not guaranteed because new modules may rely on interfaces added in new +releases. <bf>Note about module security</bf> <quote><p> @@ -661,373 +625,44 @@ guarantee this. the X server loadable modules also run with these privileges. For this reason we recommend that all users be careful to only use loadable modules from reliable sources, otherwise the - introduction of viruses and contaminated code can occur and wreak - havoc on your system. We hope to have a - mechanism for signing/verifying the modules that we provide - available in a future release. + introduction of viruses and contaminated code can occur and + wreak havoc on your system. We hope to have a mechanism for + signing/verifying the modules that we provide available in a + future release. </quote> <sect1>Configuration File <label id="config"> <p> -The X server configuration file format has been extended to handle some -of the new functionality. The <tt>xf86config</tt> utility can be used -to generate a basic config file, that may require some manual editing. -The X server also has preliminary support for generating a basic config -file. This is done by running (as root) "<tt>XFree86 -configure</tt>". -Alternatively, the sample config file <tt>XF86Config.eg</tt> that is -installed in <tt>/usr/X11R6/lib/X11</tt> may be used as a starting point. -The <tt>xf86cfg</tt> utility can also be used to create a new configuration -file or to edit an existing one. -The <tt>XF86Setup</tt> utility is currently not usable, but work is -continuing in this area. - -The main changes are covered here, but please refer to the <htmlurl -name="XF86Config(5)" url="XF86Config.5.html"> -manual page for more comprehensive information: - -<itemize> - <item>The Module section is used to load server extension modules and - font modules, but not XInput drivers. The <tt>.so</tt> suffix - should no longer be specified with module names. Options may - be supplied for modules by loading the module via a SubSection - instead of the usual Load keyword. The <tt>bitmap</tt> module - is the only font module that is loaded by default. No server - extensions are loaded by default, but some are built-in to the - server. It is strongly recommended that the extension module - containing a range of small miscellaneous extensions (<tt>extmod</tt>) - be loaded because some commonly used things won't work correctly - without it. The following example shows how to load all the server - extensions plus the Type1 and TrueType fonts support, and a - commented example that shows how to pass options to an extension - (this one is for loading the misc extensions (<tt>extmod</tt>) - with the XFree86-VidModeExtension disabled): - -<quote><verb> -Section "Module" - - Load "dbe" - Load "record" - Load "glx" - Load "extmod" - - Load "type1" - Load "freetype" - - # SubSection "extmod" - # Option "Omit XFree86-VidModeExtension" - # EndSubSection - -EndSection -</verb></quote> - - <item>Option flags have been extended and are now used more widely in the - config file. Options flags come in two main types. The first type - is exactly like the old form: - -<quote><verb> - Option "name" -</verb></quote> - - where the option just has a name specified. The name is case - insensitive, and white space and underscore characters are ignored. - The second type consists of a name and a value: - -<quote><verb> - Option "name" "value" -</verb></quote> - - The value is passed transparently as a string to the code that - uses the option. Common value formats are integer, boolean, - real, string and frequency. The following boolean option values - are recognised as meaning TRUE: <tt>"true"</tt>, <tt>"yes"</tt>, - <tt>"on"</tt>, <tt>"1"</tt>, and no value. The values recognised - as FALSE are <tt>"false"</tt>, <tt>"no"</tt>, <tt>"off"</tt>, - <tt>"0"</tt>. In addition to this, <tt>"no"</tt> may be prepended - to the <em>name</em> of a boolean option to indicate that it is - false. Frequency options can have the strings <tt>Hz</tt>, - <tt>kHz</tt>, or <tt>MHz</tt> appended to the numerical value - specified. - - Note: the value must always be enclosed in double quotes - (<tt>"</tt>), even when it is numerical. - - <item>The ServerFlags section now accepts its parameters as Options - instead of as special keywords. The older keyword format is - still recognised for compatibility purposes, but is deprecated - and support for it will likely be dropped in a future release. - The DPMS and screen save timeout values are now specified in the - ServerFlags section rather than elsewhere (because they are global - parameters, not screen-specific). This example shows the defaults - for these: - -<quote><verb> - Option "blank time" "10" - Option "standby time" "20" - Option "suspend time" "30" - Option "off time" "40" -</verb></quote> - - The new option <tt>AllowDeactivateGrabs</tt> allows deactivating - any active grab with the key sequence <tt>Ctrl+Alt+Keypad-Divide</tt> - and the new option <tt>AllowClosedownGrabs</tt> allows closing the - connection to the grabbing client with the key sequence - <tt>Ctrl+Alt+Keypad-Multiply</tt>. Note that these options are off - by default as they allow users to remove the grab used by screen - saver/locker programs. - - <item>The Keyboard, Pointer and XInput sections have been replaced by a - more general InputDevice section. The old Keyboard and Pointer - sections are still recognised for compatibility purposes, but - they are discommended and support for them may be dropped in future - releases. The old XInput sections are no longer recognised. - The keywords from the old sections are expressed as Options in - the InputDevice sections. The following example shows typical - InputDevice sections for the core mouse and keyboard. - -<quote><verb> -Section "InputDevice" - Identifier "Keyboard 1" - Driver "keyboard" - Option "AutoRepeat" "500 5" - Option "XkbModel" "pc104" - Option "XkbLayout" "us" -EndSection - -Section "InputDevice" - Identifier "Mouse 1" - Driver "mouse" - Option "Protocol" "PS/2" - Option "Device" "/dev/mouse" - Option "SampleRate" "80" -EndSection -</verb></quote> - - <item>The Monitor section is mostly unchanged. The main difference is - that a set of VESA modes is defined internally in the server, - and so for most monitors, it isn't necessary to specify any modes - explicitly in the Monitor section. There is also a new Modes section - that can be used to define a set of modes separately from the - Monitor section, and the Monitor section may "include" them - with the "<tt>UseModes</tt>" keyword. The Monitor section may also - include Options. Options that are monitor-specific, like the - <tt>"DPMS"</tt> and <tt>"Sync on Green"</tt> options are best - specified in the Monitor sections. - - <item>The Device sections are mostly unchanged. The main difference - is the new (and mandatory) Driver keyword that specifies which - video driver should be loaded to drive the video card. Another - difference is the BusID keyword that is used to specify which of - possibly multiple video cards the Device section is for. The - following is an example for a Matrox card: - -<quote><verb> -Section "Device" - Identifier "MGA 1" - Driver "mga" - BusID "PCI:1:0:0" -EndSection -</verb></quote> - - <item>The Screen sections are mostly unchanged. The old Driver keyword - is no longer used, and a mandatory Identifier keyword has been - added. The DefaultColorDepth keyword has been renamed to - DefaultDepth. - - <item>A new section called ServerLayout has been added to allow the - layout of the screens and the selection of input devices to be - specified. The ServerLayout sections may also include options - that are normally found in the ServerFlags section. Multiple - ServerLayout sections may be present, and selected from the command - line. The following example shows a ServerLayout section for a - dual-headed configuration with two Matrox cards, and two mice: - -<quote><verb> -Section "ServerLayout" - Identifier "Layout 1" - Screen "MGA 1" - Screen "MGA 2" RightOf "MGA 1" - InputDevice "Keyboard 1" "CoreKeyboard" - InputDevice "Mouse 1" "CorePointer" - InputDevice "Mouse 2" "SendCoreEvents" - Option "BlankTime" "5" -EndSection -</verb></quote> - -See the <htmlurl name="XF86Config(5)" url="XF86Config.5.html"> man page -for a more detailed explanation of the format of the new ServerLayout -section. - - -</itemize> - -The config file search patch has been extended, with the directories -<tt>/etc/X11</tt> and <tt>/usr/X11R6/etc/X11</tt> being added. The full -search path details are documented in the XF86Config manual page. +The XFree86 server uses a configuration file as the primary mechanism +for providing configuration and run-time parameters. The configuration +file format is described in detail in the <htmlurl name="XF86Config(5)" +url="XF86Config.5.html"> manual page. +The XFree86 server has support for automatically determining an initial +configuration on most platforms, as well as support or generating a basic +initial configuration file. <sect1>Command Line Options <p> -The following new X server command line options have been added: - -<quote><p> - -<tt>-depth</tt> <it>n</it> -<quote><p> - This specifies the colour depth that the server is running at. - The default is 8 for most drivers. Most drivers support the - values 8, 15, 16 and 24. Some drivers also support the values - 1 and 4. Some drivers may also support other depths. Note that - the depth is different from the ``bpp'' that was specified with - previous versions. The depth is the number of bits in each - pixel that are significant in determining the pixel's value. - The bpp is the total size occupied by each pixel, including bits - that are not used. The old <tt>-bpp</tt> option is no longer - recognised because it isn't a good way of specifying the server - behaviour. - -</quote> - -<tt>-fbbpp</tt> <it>n</it> -<quote><p> - This specifies the bpp format to use for the framebuffer. This - may be used in 24-bit mode to force a framebuffer format that is - different from what the driver chooses by default. In most cases - there should be no need to use this option. - -</quote> - -<tt>-pixmap24</tt> -<quote><p> - This specifies that the client-side pixmap format should be the - packed 24-bit format that was often used by the 3.3.x servers. - The default is the more common 32-bit format. There should normally - be no need to use this option. - -</quote> - -<tt>-pixmap32</tt> -<quote><p> - This specifies that the client-side pixmap format should be the - sparse 32-bit format. This is the default, so there should - normally be no need to use this option. - -</quote> - -<tt>-layout</tt> <it>name</it> -<quote><p> - This specifies which ServerLayout section in the config file to - use. When this option is not specified, the first ServerLayout - section is used. When there is no ServerLayout section, the - first Screen section is used. - -</quote> - -<tt>-screen</tt> <it>name</it> -<quote><p> - This specifies which Screen section in the config file to - use. When this option is not specified, the first ServerLayout - section is used. When there is no ServerLayout section, the - first Screen section is used. - -</quote> - -<tt>-keyboard</tt> <it>name</it> -<quote><p> - This specifies which InputDevice section in the config file to - use for the core keyboard. This option may be used in conjunction - with the <tt>-screen</tt> option. - -</quote> - -<tt>-pointer</tt> <it>name</it> -<quote><p> - This specifies which InputDevice section in the config file to - use for the core pointer. This option may be used in conjunction - with the <tt>-screen</tt> option. - -</quote> - -<tt>-modulepath</tt> <it>path</it> -<quote><p> - This specifies the module search path. The path should be a - comma-separated list of absolute directory paths to search for - server modules. When specified here, it overrides the value - specified in the config file. This option is only available - when the server is started by the <tt>root</tt> user. - -</quote> - -<tt>-logfile</tt> <it>file</it> -<quote><p> - This specifies the log file name. When specified here, it - overrides the default value. This option is only available when - the server is started by the <tt>root</tt> user. - -</quote> - -<tt>-scanpci</tt> -<quote><p> - This specifies that the <tt>scanpci</tt> module should be loaded and - executed. This does a scan of the PCI bus. - -</quote> - -<tt>-logverbose</tt> [<it>n</it>] -<quote><p> - This options specifies the verbosity level to use for the log file. - The default is 3. - -</quote> - -</quote> - -The following X server command line options have been changed since 3.3.x: - -<quote><p> - -<tt>-verbose</tt> [<it>n</it>] -<quote><p> - This option specifies the verbosity level to use for the server - messages that get written to stderr. It may be specified multiple - times to increase the verbosity level (as with 3.3.x), or the - verbosity level may be specified explicitly as a number. The - default verbosity level is 0. - -</quote> - -<tt>-xf86config</tt> <it>filename</it> -<quote><p> - This option has been extended to allow non-root users to specify - a relative config file name. The config file search path will be - used to locate the file in this case. This makes it possible for - users to choose from multiple config files that the the sysadmin - has provided. - -</quote> - - -</quote> - -A more complete list of XFree86 X server command line options can be found -in the <htmlurl name="XFree86(1)" url="XFree86.1.html"> manual page. - +Command line options can be used to override some default parameters and +parameters provided in the configuration file. These command line options +are described in the <htmlurl name="XFree86(1)" +url="XFree86.1.html"> manual page. + <sect1>XAA <p> -The XFree86 Acceleration Architecture (XAA) has been completely rewritten +The XFree86 Acceleration Architecture (XAA) was completely rewritten from scratch for XFree86 4.x. Most drivers implement acceleration by making use of the XAA module. <sect1>Multi-head <p> Some multi-head configurations are supported in XFree86 4.x, primarily -with multiple PCI/AGP cards. However, this is an area that is still -being worked on, and we expect that the range of configurations for which -it works well will increase in future releases. A configuration that -is known to work well in most cases is multiple (supported) Matrox cards. +with multiple PCI/AGP cards. One of the main problems is with drivers not sufficiently initialising cards that were not initialised at boot time. This has been improved @@ -1085,10 +720,9 @@ and 2; these can be disabled independently with <tt>Option "NoDDC1"</tt> and <tt>Option "NoDDC2"</tt>. At startup the server prints out DDC information from the display, and -can use this information to set or warn about monitor sync limits (but -not modelines yet). For some drivers, the X server's new -<tt>-configure</tt> option uses the DDC information when generating the -config file. +can use this information to set the default monitor parameters, or to +warn about monitor sync limits if those provided in the configuration file +don't match those that are detected. <sect2>Changed behavior caused by DDC. <p> @@ -1103,27 +737,11 @@ of the config file. <sect1>GLX and the Direct Rendering Infrastructure (DRI) <p> -<url name="Precision Insight" url="http://www.precisioninsight.com"> -was provided with funding and support from <url name="Red Hat" -url="http://www.redhat.com">, <url name="SGI" url="http://www.sgi.com">, -<url name="3Dfx" url="http://www.3dfx.com">, <url name="Intel" -url="http://www.intel.com">, <url name="ATI" url="http://www.ati.com">, -and <url name="Matrox" url="http://www.matrox.com"> to integrate the GLX -extension for 3D rendering in an X11 window. The 3D core rendering -component is the <url name="Mesa" url="http://www.mesa3d.org"> library. -SGI has released the sources to the GLX extension framework under an -open license, which essentially provides the glue between the 3D -library and this windowing system. Precision Insight has integrated -these components into the XFree86 X Server and added a Direct Rendering -Infrastructure (DRI). Direct Rendering provides a highly optimized -path for sending 3D data directly to the graphics hardware. This -release provides a complete implementation of direct rendering support -for the 3Dfx Banshee, Voodoo3 and Voodoo5 graphics cards, as well as -the Intel i810/i815 cards, ATI Rage 128, and Matrox G400. -Updated information on DRI -compatible drivers can be found at the <url name="DRI Project" -url="http://dri.sourceforge.net"> on <url name="SourceForge" -url="http://www.sourceforge.net">. +Direct rendered OpenGL® support is provided for several hardware +platforms by the Direct Rendering Infrastructure (DRI). Further information +about DRI can be found at the <url name="DRI Project's web site" +url="http://dri.sf.net/">. The 3D core rendering component is provided by +<url name="Mesa" url="http://www.mesa3d.org">. <sect1>XVideo Extension (Xv) <p> @@ -1194,7 +812,7 @@ file is included in the <htmlurl name="Xft(3)" url="Xft.3.man"> man page. <sect2>FreeType support in Xft <p> -XFree86 &relvers; includes sources for FreeType version 2.1.1, and, by +XFree86 &relvers; includes sources for FreeType version 2.1.4, and, by default, they are built and installed automatically. </sect2> @@ -1272,9 +890,12 @@ in the <htmlurl name="README.fonts" url="fonts.html"> document. <p> XFree86 4.x comes with two TrueType backends, known as -`xfsft' (the <tt>"freetype"</tt> module) and `X-TrueType' (the -<tt>"xtt"</tt> module). Both of these backends are based on the FreeType -library. +"FreeType" backend (the <tt>"freetype"</tt> module) and `X-TrueType' +(the <tt>"xtt"</tt> module). Both of these backends are based on the +FreeType library. The functionality of X-TrueType has been merged into +the FreeType backend by the After X-TT Project for XFree86 4.4. +Consequently, the old X-TrueType backend will be dropped as of XFree86 +4.5. <sect1>CID font support <p> @@ -1385,22 +1006,6 @@ please contact <p> --> -<sect1>Directory rearrangements -<p> - -Some changes to the installed XFree86 directory structure have been -implemented for 4.x. -One important -change is a modified search path for the X -server's <tt>XF86Config</tt> file. The details of this can be found -in the XF86Config manual page. The other main change is moving -most of the run-time configuration files to <tt>/etc/X11</tt>, with -symbolic links in the old <tt>/usr/X11R6/lib/X11</tt> location pointing -to the new location. Some run-time generated files are now located -under the appropriate subdirectories of <tt>/var</tt>, again with the -relevant symbolic links in the old location. - - </article> |