[BACK]Return to RELNOTES CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / xsrc / xfree / xc

Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.

Diff for /xsrc/xfree/xc/Attic/RELNOTES between version 1.1.1.6 and 1.1.1.7

version 1.1.1.6, 2003/02/28 13:18:41 version 1.1.1.7, 2004/03/05 14:23:50
Line 1 
Line 1 
                      Release Notes for XFree86[tm] 4.3.0                       Release Notes for XFree86[tm] 4.4.0
   
                           The XFree86 Project, Inc                            The XFree86 Project, Inc
   
                               26 February 2003                                29 February 2004
   
                                   Abstract                                    Abstract
   
      This document contains some information about features present in       This document contains information about features and their status
      XFree86 4.3.0 and their status.       in XFree86 4.4.0.
   
 1.  Introduction to the 4.x Release Series  1.  Introduction to the 4.x Release Series
   
 XFree86 4.0 was the first official release of the new XFree86 4 series.  The  XFree86 4.0 was the first official release of the new XFree86 4 series.  The
 current release (4.3.0) is the latest in that series.  XFree86 4 represents a  current release (4.4.0) is the latest in that series.  XFree86 4 represents a
 significant redesign of the XFree86 X server.  Not all of the hardware  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 sup-  drivers from 3.3.x have been ported to 4.x yet, but conversely, 4.x has sup-
 port for a lot of hardware that is not supported in 3.3.x.  Our Driver Status  port for a lot of hardware that is not supported in 3.3.x.  Our Driver Status
 document summarizes how the hardware driver support compares between 3.3.6  document summarizes how the hardware driver support compares between 3.3.6
 and 4.3.0.  Please check there first before downloading 4.3.0.  and 4.4.0.
   
 The 4.0.1 release introduced a new graphical configuration tool, "xf86cfg",  XFree86 4.4 introduces an automatic configuration mechanism for the XFree86
 and a text mode interface was added to it for the 4.0.2 release.  It is the  server which makes it now possible to start XFree86 without first creating a
 preferred configuration tool provided by with XFree86.  The trusty old text-  configuration file.  The initial automatic configuration support is targeted
 based tool "xf86config" can also be used for generating X server config  towards Linux and FreeBSD and it is hoped that automatic configuration will
 files.  In addition to these tools, the XFree86 server has some built in  be supported on other platforms in future releases.
 capabilities for generating a base config file.  This works well for most  
 hardware, and in most cases is the easiest way to get an initial config file.  If you are running either  Linux or FreeBSD, try it out if you do not already
 To try it out, just run (as root):  have a working XF86Config file.  If you want to customise things afterwards,
   you can cut and paste the automatically generated configuration from the
   /var/log/XFree86.0.log file into an XF86Config file and make your customisa-
   tions there.
   
   If you do not have any luck with automatic configuration, or you are using a
   platform that is not currently supported, try one of the older methods for
   getting started.
   
   XFree86 comes with a graphical configuration tool called "xf86cfg", which
   also has a text mode interface and can be used to create an initial configu-
   ration file. It can also be used to customise existing configurations.
   
   Next in the order of configuration preferences is to use the XFree86 server's
   ability to create a starting configuration file.  Run as root:
   
      XFree86 -configure       XFree86 -configure
   
 Each of these configuration options will give you a reasonable starting point  and follow the instructions.
 for a suitable configuration file.  We've put some effort into documenting  
 the 4.3.0 config file format, and you can find that information in the  Finally, if all else fails, the trusty old standby text-based tool "xf86con-
 XF86Config manual page.  Check there and the driver-specific manual pages and  fig" can also be used for generating X server config files.
 the related documentation for further information.  References to this  
 driver-specific information can be found in the tables below (section 3.,  At least one, and hopefully, all of these configuration options will give you
 page 1).  a reasonable starting point for a suitable configuration file.  With the
   automatic mechanism you might even find that you don't need one!
 We have plans to make the configuration file optional in a future release.  
 The XFree86 server is close to being able to automatically determine a com-  If you do need to customise the configuration file, see the XF86Config manual
 plete base configuration for most popular hardware configurations.  page.  You can also check the driver-specific manual pages and the related
   documentation (found at tables below (section 3., page 1) also.
 Before you go to download and install the binary distributions for this  
 release, please have a quick read through the Installation Document.  It may  Before downloading  the binary distributions for this release, please have a
 save you some time and help you figure out which of the binary releases you  quick read through the Installation Document.  It may save you some time and
 need.  also help you figure out which of the binary releases you need.
   
 The next section describes what is new in the latest version (4.3.0) compared  The next section describes what is new in the latest version (4.4.0) compared
 with the previous full release (4.2.0).  The other sections below describe  with the previous full release (4.3.0).  The other sections below describe
 some of the new features and changes between 3.3.x and 4.0.  There are lot's  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  of new features, and we definitely don't have enough space to cover them all
 here.  here.
   
 2.  Summary of new features in 4.3.0.  2.  Summary of new features in 4.4.0.
   
   This is a sampling of the new features in XFree86 4.4.0.  A more complete
   list of changes can be found in the CHANGELOG that is part of the XFree86
   source tree.  It can also be viewed online at our CVSweb server
   <URL:http://cvsweb.xfree86.org/cvsweb/xc/pro-
   grams/Xserver/hw/xfree86/CHANGELOG?rev=HEAD>.
   
 2.1  Video Driver Enhancements  2.1  Video Driver Enhancements
   
    o  ATI Radeon 9x00 2D support added, and 3D support added for the Radeon     o Several stability issues with the support for the Intel 830M, 845G,
      8500, 9000, 9100, and M9.  The 3D support for the Radeon now includes       852GM, 855GM and 865G integrated graphics chipsets have been fixed.
      hardware TCL.       Some limitations related to the driver's use of the video BIOS remain,
        especially for some laptops.
   
      o The nv driver for NVIDIA cards has been updated as follows:
   
    o  Support added to the i810 driver for Intel 845G, 852GM, 855GM and 865G          o Support added to the nv driver for the GeForce FX 5700, which
      integrated graphics chipsets, including 2D, 3D (DRI) and XVideo.  Sup-            didn't work with XFree86 4.3.
      port for the 830M has been improved, and XVideo support added.  
   
    o  National Semiconductor SC1x00, GX1, and GX2 chipset support added with          o The driver now does a much better job of auto-detecting which con-
      the "nsc" driver.            nector of dual output cards the monitor is attached to, and this
             should reduce or eliminate the need for manual XF86Config over-
             rides.
   
    o  Support added for the NVIDIA nForce2 integrated graphics, GeForce 4,          o The 2D acceleration for TNT and GeForce has been completely rewrit-
      and GeForce FX.            ten and its performance should be substantially improved.
   
    o  Major SiS driver updates for some of the latest chipsets.  Unfortu-          o TNT and GeForce cards have a new Xv PutImage adaptor which does
      nately the SiS 3D driver has had to be disabled because no one has yet            scaled YUV bit blits.
      taken up the challenge to port it to Mesa 4.x.  
   
    o  The s3virge driver now has support for double scan modes on the DX     o The SiS driver has seen major updates, including:
      (with XVideo disabled).  
   
    o  Updates to the savage driver, including fixing problems with the          o Support for 661/741/760 and support for 330 (Xabre).
      TwisterK, and problems with incorrect memory size detection.  
   
    o  2D acceleration added for the Trident CyberBladeXP/Ai1 chipsets.          o Merged Framebuffer mode.
   
    o  Support for big endian architectures has been added to the C&T driver.          o Support for DVI, and much more.
   
    o  Various updates and bug fixes have been made to most other drivers.          o DRI for 300 series (300/305, 540, 630, 730) is supported again.
   
      o A new driver for several VIA integrated graphics chipsets has been
        added.
   
      o Various updates and bug fixes have been made to most other drivers.
   
 2.2  Input Driver Enhancements  2.2  Input Driver Enhancements
   
    o  The mouse driver now has automatic protocol detection for PS/2 mice.     o The mouse driver has some support on Linux and FreeBSD for auto-detect-
        ing which device node to use. This makes it unnecessary to supply this
        information in the XF86Config file in most cases.
   
    o  Several new input drivers have been added, including tek4957, jamstudio  2.3  IPv6 support
      (js_x), fpit, palmax, and ur98 (Linux only).  
   
 2.3  X Server and Extension Updates  XFree86 4.4 supports IPv6, based on the code contributed by Sun Microsystems,
   Inc. to X.Org. See X.org's document <URL:http://www.x.org/IPV6_Spe-
   cific_Changes.html> for a detailed list of what these changes are and how
   your system is affected by them.
   
    o  Support for the RandR extension has been partially integrated into the  2.3.1  Protocol names and aliases.
      XFree86 server, providing support for resizing the root window at run-  
      time.  
   
    o  The Mesa version used for OpenGL1.3 and DRI driver support has been     o tcp is an alias for both IPv6 and IPv4 transports.
      updated to 4.0.4.  
   
    o  The XFree86 server's hot keys (including those for switching modes and     o inet specifies IPv4 only.
      virtual terminals) can now be configured via XKB.  Previously they were  
      hard coded.  An X server configuration option has been added to allow  
      the VT switching hot keys to be disabled.  
   
 2.4  Client and Library Updates     o inet6 specifies IPv6 only.
   
    o  An Xcursor library providing support for alpha blended (ARGB) and ani-  You can force the X server to only listen to IPv4 connections with the X
      mated cursors.  Two Xcursor themes are provided (redglass and white-  -nolisten inet6  command or you can force a IPv6 connection by setting DIS-
      glass), as well as the default "core" theme (the traditional cursors).  PLAY to inet6/host:0.
   
    o  Xterm updated to patch level 173, including the following bugfixes:  2.3.2  XDM
   
         o  Fix two infinite loops (special cases of mouse hilite tracking,  The IPv6 XDMCP code is not enabled by default on platforms that don't support
           DECUDK parsing).  binding a IPv6 socket to a IPv4 address.
   
         o  Make repainting of the 256-color example work properly.  The XDM-AUTHORIZATION-1 authentication scheme does not support IPv6 addresses
   but a new release of the protocol, XDM-AUTHORIZATION-2 has been designed;
   this though is yet to be  implemented.  By default XFree86 builds do not
   enable the XDM-AUTHORIZATION-1 code.
   
         o  Modify parser tables to improve detection of malformed control  2.4  X Server and Extension Updates
           sequences, making xterm behave more like a real DEC terminal.  
   
         o  Fix a problem with the blinking cursor which occasionally caused     o The Mesa version used for OpenGL1.3 and DRI driver support has been
           xterm to pause until a key was pressed.       updated to 5.0.2.
   
         o  Fix improper parsing of multiple items in the ttyModes resource.  2.5  Client and Library Updates
   
      and the following improvements:  2.5.1  Xterm
   
         o  Modify xterm to invoke luit.  The user-visible changes to xterm since XFree86 4.3 are:
   
         o  Add simple session management client capabilities.  Bug Fixes:
   
         o  Add a modifyCursorKeys resource to control how the shift- and sim-     o Make signalInhibit resource work, i.e., disable the menu entries that
           ilar modifiers are used to make a cursor escape sequence.       would send signals to, or exit xterm.
   
         o  Check if the printerCommand resource string is empty, and use this     o Make cursor definition in tek4014 emulation work as originally imple-
           to allow the user to disable printer function.       mented.
   
         o  Sort the options list which is displayed in help- and syntax-mes-     o Modify translations for scrollbar so that one can use shifted pageup,
           sages at runtime to simplify maintenance.       wheel mouse, etc., while the mouse pointer is over the scrollbar.
   
 2.5  I18N and Font Updates     o Correct initialization of G1 character set mapping.
   
    o  FreeType2 updated to version 2.1.1.  New Features:
   
    o  The "freetype" X server font backend has undergone a partial rewrite.     o Modify the predictable version of the generated logfile name to append
      The new version is based on FreeType 2, and handles TrueType (including       the process-id rather than a random value.
      OpenType/TTF), OpenType/CFF and Type 1 fonts.  The old "type1" backend  
      is now deprecated, and is only used for CIDFonts by default.  
   
    o  A new utility called "mkfontscale", which builds fonts.scale files, has     o Modify scroll-back and scroll-forw actions to accept an adjustment
      been added.       value, e.g.,
   
    o  The Xft library has undergone a major restructuring, and is now split            scroll-back(1, page-2)
      into fontconfig (which deals with font discovery and configuration and  
      is independent from X), and Xft itself (which uses fontconfig and deals  
      with font rasterisation and rendering.  The format of the Xft font con-  
      figuration files has changed in an incompatible manner.  
   
    o  Support has been added to the Xft library to do rendering with the core       to scroll back by 2 lines less than a page.
      X11 protocol.  This allows clients using this library to render to X  
      servers that don't have support for the RENDER extension.  
   
    o  There has been a significant reworking of the XKB support to allow     o Add visualBellDelay resource to modify the length of time used for
      multi-layout configurations.  Multi-layout configurations provide a       visual bell, for very slow displays or very fast computers.
      flexible way of supporting multiple language layouts and switching  
      between them.  
   
 2.6  OS Support Updates  Improved Locale Support:
   
    o  Updates for Darwin/Mac OS X, including:     o modify uxterm script to strip modifiers such as "@euro" from the locale
        setting before adding ".UTF-8".
   
         o  Indirect GLX acceleration added.     o Add logic to wide-character support which attempts to load fonts speci-
        fied by utf8Fonts subresources at startup.  The subresources have the
        same names as the fonts which they replace, e.g., font, font1, etc., so
        that the ISO-10646-1 fonts can be specified in the XTerm app-defaults
        file.
   
         o  Smaller memory footprint and faster 2-D drawing in rootless mode.     o Improved performance with chinput application.
   
         o  Full screen mode now uses shadowfb for much faster 2-D drawing.  Improved Font Handling:
   
         o  Native fonts can be used on MacOS X.     o Document in xterm's manual page how to use XFree86 ":unscaled" keyword
        to suppress scaling of bold fonts.
   
    o  Various Cygwin support updates, including an experimental rootless X     o Improved logic for deriving bold fontname from normal fontname.
      server for Cygwin/XFree86.  
   
    o  AMD x86-64 support (primarily for Linux so far) has been added.     o Make double-width characters work with -u8 option.
   
    o  Support added for OpenBSD/sparc64.     o Updated table of Unicode line-drawing characters.
   
    o  Major OS/2 support updates.     o Several fixes for rendering using Xft (option -fa):
   
    o  Major SCO OpenServer updates.          o Make height of TrueType fonts match ascent+descent.
   
    o  Multi-head support has been added for 460GX-based Itanium systems, and          o Translate Unicode values (from UTF-8 output to xterm) for line-
      for ZX1-based Itanium2 systems.            drawing to xterm's internal code, etc., since TrueType fonts gener-
             ally do not have either set of line-drawing glyphs.  xterm can draw
             these directly.
   
    o  Experimental support for SunOS/Solaris on UltraSPARC systems.          o Pass 16-bit values rather than 8-bit values to xtermXftDrawString()
             to allow for wide-characters.
   
 A more complete list of changes can be found in the CHANGELOG that is part of          o Use built-in line-drawing characters for Xft fonts.
 the XFree86 source tree.  It can also be viewed online at our CVSweb server  
 <URL:http://cvsweb.xfree86.org/cvsweb/xc/pro-          o Implement underlining.
 grams/Xserver/hw/xfree86/CHANGELOG?rev=HEAD>.  
      o Implement boldMode for wide-characters.
   
      o Modified to work with CJK double-width (bi-width/monospace) fonts.
   
   Workarounds for Special Applications:
   
      o Add option -k8 and resource allowC1Printable to allow users of non-VTxxx
        character sets such as KOI-8 to treat the C1 control area (character
        codes 128-159) as printable rather than control characters.
   
      o Add configure option --enable-broken-st and resource brokenStringTerm to
        allow user to revert one part of the parsing table corrections.
   
      o Add configure option --enable-broken-osc and resource brokenLinuxOSC to
        accommodate scripts which do not distinguish between running in the
        Linux console and running in X.  Linux console recognizes malformed con-
        trol strings which start with an OSC, but are fixed-length, with no ter-
        minator.
   
      o Add configure option --enable-pty-handshake to allow one to compile-in
        support for the pty handshaking logic, and resource ptyHandshake to
        enable or disable it.  This feature is normally enabled.
   
   Modified Resources:
   
      o Change color4 to "dodger blue", since this provides better contrast.
   
      o Remove color resources from XTerm.ad, leaving them only in XTerm-col.ad
   
      o Modify UXTerm.ad resource file to include "XTerm-color" rather than
        "XTerm", in case the latter file contains no color resource definitions.
   
      o Changed class of veryBoldColors to VeryBoldColors, since ColorMode is
        associated with boolean resources.
   
      o Changed classes of colorBDMode and similar resources that override col-
        ors when a video attribute is set to ColorAttrMode, to make them dis-
        tinct from ColorMode.  This avoids an unexpected rendering of reverse
        video, for example.
   
   Modified terminfo/termcap entries:
   
      o Add indp and rin to terminfo entry.
   
      o Add le to termcap xterm-basic entry.  Though missing from older termcaps
        for xterm, some applications check for it.
   
      o Correct AF/AB strings in termcap for xterm-256color and xterm-88color
        entries.
   
   2.6  I18N and Font Updates
   
      o FreeType2 updated to version 2.1.4.
   
      o The "freetype" X server font backend has been updated by the 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.
   
           o The new "freetype" backend has the improved "very lazy" metric cal-
             culation method which enables super-fast loading of proportional
             CJKV fonts.
   
           o All of the servers, including xfs, Xnest, Xprt, Xvfb, the Cygwin-
             XFree86 server (as well as the XFree86 server) can handle the per-
             fect TTCap options.
   
      o The Compose file processing mechanism has been improved and made more
        flexible.  See the Xlib Compose  file support and extensions section
        below (section 5.20, page 1).
   
      o The Bitstream Vera TrueType fonts that Bitstream, Inc donated to the
        GNOME Foundation have been included with this release.
   
   2.7  OS Support Updates
   
      o On Mac OS X, the appropriate backend drawing code is now dynamically
        loaded at runtime which reduces the X server's memory footprint.  In
        rootless mode, Apple's Xplugin library is used where available.  (Xplu-
        gin 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:
   
           o Added direct GLX rendering with thread support.
   
           o Faster 2-D drawing.
   
           o Added support for the Apple-WM extension so XDarwin interoperates
             with quartz-wm.
   
      o On Darwin, IOKit mode now uses shadowfb for much faster drawing.
   
      o Various GNU/Hurd support updates.
   
      o Experimental support added for GNU/KFreeBSD and GNU/KNetBSD systems.
   
      o SCO OpenServer support updates.  XFree86 4.4 now works on Release 5.0.7
        with Maintenance Pack 1, or on prior releases through Release 5.0.4.
        Please consult the README.SCO file for details.
   
 3.  Drivers  3.  Drivers
   
 3.1  Video Drivers  3.1  Video Drivers
   
 XFree86 4.3.0 includes the following video drivers:  XFree86 4.4.0 includes the following video drivers:
   
 +--------------+--------------------------+---------------------------------------------+  +--------------+--------------------------+---------------------------------------------+
 |Driver Name   | Description              | Further Information                         |  |Driver Name   | Description              | Further Information                         |
Line 248  XFree86 4.3.0 includes the following vid
Line 372  XFree86 4.3.0 includes the following vid
 |tga           | DEC TGA                  | README.DECtga                               |  |tga           | DEC TGA                  | README.DECtga                               |
 |trident       | Trident                  | trident(4)                                  |  |trident       | Trident                  | trident(4)                                  |
 |tseng         | Tseng Labs               |                                             |  |tseng         | Tseng Labs               |                                             |
   |via           | VIA                      | via(4)                                      |
 |vesa          | VESA                     | vesa(4)                                     |  |vesa          | VESA                     | vesa(4)                                     |
 |vga           | Generic VGA              | vga(4)                                      |  |vga           | Generic VGA              | vga(4)                                      |
 |vmware        | VMWare guest OS          | vmware(4)                                   |  |vmware        | VMWare guest OS          | vmware(4)                                   |
Line 263  Drivers marked with (-) are for Linux/mi
Line 388  Drivers marked with (-) are for Linux/mi
 Darwin/Mac OS X uses IOKit drivers and does not use the module loader drivers  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.  listed above. Further information can be found in README.Darwin.
   
 XFree86 4.3.0 includes the following input drivers:  XFree86 4.4.0 includes the following input drivers:
   
 3.2  Input Drivers  3.2  Input Drivers
   
    +------------+----------------------------------+---------------------+     +------------+----------------------------------+---------------------+
    |Driver Name | Description                      | Further Information |     |Driver Name | Description                      | Further Information |
    +------------+----------------------------------+---------------------+     +------------+----------------------------------+---------------------+
      |aiptek(*)   | Aiptek USB tablet                | aiptek(4)           |
    |calcomp     | Calcomp                          |                     |     |calcomp     | Calcomp                          |                     |
    |citron      | Citron                           | citron(4)           |     |citron      | Citron                           | citron(4)           |
    |digitaledge | DigitalEdge                      |                     |     |digitaledge | DigitalEdge                      |                     |
    |dmc         | DMC                              | dmc(4)              |     |dmc         | DMC                              | dmc(4)              |
    |dynapro     | Dynapro                          |                     |     |dynapro     | Dynapro                          |                     |
    |elographics | EloGraphics                      |                     |     |elographics | EloGraphics                      |                     |
    |elographics | EloGraphics                      |                     |  
    |fpit        | Fujitsu Stylistic Tablet PCs     | fpit(4)             |     |fpit        | Fujitsu Stylistic Tablet PCs     | fpit(4)             |
    |hyperpen    | HyperPen                         |                     |     |hyperpen    | Aiptek HyperPen 6000             |                     |
    |js_x        | JamStudio pentablet              | js_x(4)             |     |js_x        | JamStudio pentablet              | js_x(4)             |
    |kbd         | generic keyboards (alternate)    | kbd(4)              |     |kbd         | generic keyboards (alternate)    | kbd(4)              |
    |keyboard    | generic keyboards                | keyboard(4)         |     |keyboard    | generic keyboards                | keyboard(4)         |
Line 297  XFree86 4.3.0 includes the following inp
Line 422  XFree86 4.3.0 includes the following inp
   
 Drivers marked with (*) are available for Linux only.  Drivers marked with (*) are available for Linux only.
   
 4.  Overview of XFree86 4.x.  4.  Known Problems
   
 Unlike XFree86 3.3.x where there are multiple X server binaries, each of     o Known issues with this version of the SiS driver:
 which drive different hardware, XFree86 4.3.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.3.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  
 planned for future releases.  
   
 4.1  Loader and Modules  
   
 The XFree86 X server has a built-in run-time loader, donated by 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 mod-  
 ules 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.  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.3.0 has support for Intel (x86), Alpha and PowerPC          o The driver will not work with upcoming laptops/notebooks with
 platforms.  It also has preliminary support for Sparc platforms.            661/741/760 and 30xLV bridges as regards LCD output. This is due
             folks at SiS at the very moment writing an entirely new VBIOS for
             such machines whose data layout is not decided yet.  (This might
             affect machines with 650/740 as well within the next year.)
   
           o Xv does not work correctly in TV NTSC 1024x768 mode, if the overlay
             is very large (or full screen). The effect are flickering lines on
             the screen. This is a hardware problem. Do not use this mode for
             video.
   
           o YPbPr 720p output is blurry (at least at 1024x768; unknown for
             other modes). This is a driver problem; solution currently unknown.
   
      o We have received a late report that enabling DPMS support with the
        radeon driver can damage some Viewsonic monitors.  DPMS is usually dis-
        abled by default.  You can verify whether or not DPMS is enabled by run-
        ning 'xset q' from within your X session.
   
   5.  Overview of XFree86 4.x.
   
   XFree86 4.x has a single X server binary called XFree86.  This binary can
   either have one or more video and input drivers linked in statically, or more
   usually, dynamically, and in that manner load the video drivers, input
   drivers, and other modules that are needed.
   
   XFree86 4.4.0 has X server support for most UNIXand UNIX-like 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.  Support for additional architectures and operating systems is in
   progress and is planned for future releases.
   
   5.1  Loader and Modules
   
   The XFree86 X server has a built-in run-time loader, which can load normal
   object files and libraries in most of the commonly used formats.  The loader
   does not rely on an operating system's native dynamic loader support and it
   works on platforms that do not provide this feature.  This  allows  for the
   modules to be operating system independent (although not, of course, CPU
   architecture independent) which 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.
   
   A main benefit of this, is that when modules are updated, they do not need to
   be recompiled for every different operating system.  The loader in version
   4.4.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,  The X server makes use of modules for video drivers, X server extensions,
 font rasterisers, input device drivers, framebuffer layers (like mfb, cfb,  font rasterisers, input device drivers, framebuffer layers (like mfb, cfb,
 etc), and internal components used by some drivers (like XAA),  etc), and internal components used by some drivers (like XAA),
   
 The module interfaces (API and ABI) used in this release is still subject to  The module interfaces (both API and ABI) used in this release are subject to
 change without notice.  While we will attempt to provide backward compatibil-  change without notice.  While we will attempt to provide backward compatibil-
 ity for the module interfaces as of the 4.0 release (meaning that 4.0 modules  ity 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.  will work with future core X server binaries), we cannot guarantee this.
   Compatibility in the other direction is explicitly not guaranteed because new
   modules may rely on interfaces added in new releases.
   
 Note about module security  Note about module security
   
Line 349  Note about module security
Line 494  Note about module security
      hope to have a mechanism for signing/verifying the modules that we       hope to have a mechanism for signing/verifying the modules that we
      provide available in a future release.       provide available in a future release.
   
 4.2  Configuration File  5.2  Configuration File
   
   The XFree86 server uses a configuration file as the primary mechanism for
   providing configuration and run-time parameters.  The configuration file for-
   mat is described in detail in the XF86Config(5) manual page.
   
   The XFree86 server has support for automatically determining an initial con-
   figuration on most platforms, as well as support or generating a basic ini-
   tial configuration file.
   
 The X server configuration file format has been extended to handle some of  5.3  Command Line Options
 the new functionality.  The xf86config 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) "XFree86 -configure".  Alternatively, the sample config  
 file XF86Config.eg that is installed in /usr/X11R6/lib/X11 may be used as a  
 starting point.  The xf86cfg utility can also be used to create a new config-  
 uration file or to edit an existing one.  The XF86Setup utility is currently  
 not usable, but work is continuing in this area.  
   
 The main changes are covered here, but please refer to the XF86Config(5) man-  
 ual page for more comprehensive information:  
   
    o The Module section is used to load server extension modules and font  
      modules, but not XInput drivers.  The .so 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 bitmap 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 (extmod) be loaded because  
      some commonly used things won't work correctly without it.  The follow-  
      ing 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 exten-  
      sions (extmod) with the XFree86-VidModeExtension disabled):  
   
                Section "Module"  
   
                    Load "dbe"  
                    Load "record"  
                    Load "glx"  
                    Load "extmod"  
   
                    Load "type1"  
                    Load "freetype"  
   
                  # SubSection "extmod"  
                  #     Option "Omit XFree86-VidModeExtension"  
                  # EndSubSection  
   
                EndSection  
   
    o Option flags have been extended and are now used more widely in the con-  
      fig file.  Options flags come in two main types.  The first type is  
      exactly like the old form:  
   
                    Option "name"  
   
      where the option just has a name specified.  The name is case insensi-  
      tive, and white space and underscore characters are ignored.  The second  
      type consists of a name and a value:  
   
                    Option "name" "value"  
   
      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 mean-  
      ing TRUE: "true", "yes", "on", "1", and no value.  The values recognised  
      as FALSE are "false", "no", "off", "0".  In addition to this, "no" may  
      be prepended to the name of a boolean option to indicate that it is  
      false.  Frequency options can have the strings Hz, kHz, or MHz appended  
      to the numerical value specified.  
   
      Note: the value must always be enclosed in double quotes ("), even when  
      it is numerical.  
   
    o 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:  
   
                    Option "blank time"    "10"  
                    Option "standby time"  "20"  
                    Option "suspend time"  "30"  
                    Option "off time"      "40"  
   
      The new option AllowDeactivateGrabs allows deactivating any active grab  
      with the key sequence Ctrl+Alt+Keypad-Divide and the new option Allow-  
      ClosedownGrabs allows closing the connection to the grabbing client with  
      the key sequence Ctrl+Alt+Keypad-Multiply. Note that these options are  
      off by default as they allow users to remove the grab used by screen  
      saver/locker programs.  
   
    o 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 key-  
      board.  
   
                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  
   
    o 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 Mon-  
      itor 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 Moni-  
      tor section may "include" them with the "UseModes" keyword.  The Monitor  
      section may also include Options.  Options that are monitor-specific,  
      like the "DPMS" and "Sync on Green" options are best specified in the  
      Monitor sections.  
   
    o 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:  
   
                Section "Device"  
                    Identifier "MGA 1"  
                    Driver     "mga"  
                    BusID      "PCI:1:0:0"  
                EndSection  
   
    o 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.  
   
    o 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 pre-  
      sent, 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:  
   
                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  
   
      See the XF86Config(5) man page for a more detailed explanation of the  
      format of the new ServerLayout section.  
   
 The config file search patch has been extended, with the directories /etc/X11  
 and /usr/X11R6/etc/X11 being added.  The full search path details are docu-  
 mented in the XF86Config manual page.  
   
 4.3  Command Line Options  
   
 The following new X server command line options have been added:  
   
      -depth n  
   
           This specifies the colour depth that the server is run-  
           ning 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 previ-  
           ous 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 -bpp option is  
           no longer recognised because it isn't a good way of spec-  
           ifying the server behaviour.  
   
      -fbbpp n  
   
           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.  
   
      -pixmap24  
   
           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.  
   
      -pixmap32  
   
           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.  
   
      -layout name  
   
           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.  
   
      -screen name  
   
           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 Server-  
           Layout section, the first Screen section is used.  
   
      -keyboard name  
   
           This specifies which InputDevice section in the config  
           file to use for the core keyboard.  This option may be  
           used in conjunction with the -screen option.  
   
      -pointer name  
   
           This specifies which InputDevice section in the config  
           file to use for the core pointer.  This option may be  
           used in conjunction with the -screen option.  
   
      -modulepath path  
   
           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 over-  
           rides the value specified in the config file.  This  
           option is only available when the server is started by  
           the root user.  
   
      -logfile file  
   
           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 root user.  
   
      -scanpci  
   
           This specifies that the scanpci module should be loaded  
           and executed.  This does a scan of the PCI bus.  
   
      -logverbose [n]  
   
           This options specifies the verbosity level to use for the  
           log file.  The default is 3.  
   
 The following X server command line options have been changed since 3.3.x:  
   
      -verbose [n]  
   
           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.  
   
      -xf86config filename  
   
           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.  
   
 A more complete list of XFree86 X server command line options can be found in  
 the XFree86(1) manual page.  
   
 4.4  XAA  
   
 The XFree86 Acceleration Architecture (XAA) has been completely rewritten  
 from scratch for XFree86 4.x.  Most drivers implement acceleration by making  
 use of the XAA module.  
   
 4.5  Multi-head  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 XFree86(1) manual page.
   
   5.4  XAA
   
   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.
   
   5.5  Multi-head
   
 Some multi-head configurations are supported in XFree86 4.x, primarily with  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  multiple PCI/AGP cards.
 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.  
   
 One of the main problems is with drivers not sufficiently initialising cards  One of the main problems is with drivers not sufficiently initialising cards
 that were not initialised at boot time.  This has been improved somewhat with  that were not initialised at boot time.  This has been improved somewhat with
Line 651  to be resolved.  Some combinations can b
Line 529  to be resolved.  Some combinations can b
 which card is the primary card (either by using a different PCI slot, or by  which card is the primary card (either by using a different PCI slot, or by
 changing the system BIOS's preference for the primary card).  changing the system BIOS's preference for the primary card).
   
 4.6  Xinerama  5.6  Xinerama
   
 Xinerama is an X server extension that allows multiple physical screens to  Xinerama is an X server extension that allows multiple physical screens to
 behave as a single screen.  With traditional multi-head in X11, windows can-  behave as a single screen.  With traditional multi-head in X11, windows can-
Line 673  Known problems:
Line 551  Known problems:
      an issue that needs to be dealt with in the individual window managers,       an issue that needs to be dealt with in the individual window managers,
      and isn't specifically an XFree86 problem.       and isn't specifically an XFree86 problem.
   
 4.7  DGA version 2  5.7  DGA version 2
   
   DGA 2.0 is included in 4.4.0.  Documentation for the client libraries can be
   found in the XDGA(3) man page.  A good degree of backwards compatibility with
   version 1.0 is provided.
   
 DGA 2.0 is included in 4.3.0, but is not implemented by all drivers.  Prelim-  5.8  DDC
 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-  The VESADisplay Data Channel (DDC[tm]) standard allows the monitor to tell
 vided.  the video card (or on some cases the computer directly) about itself; partic-
   ularly the supported screen resolutions and refresh rates.
 4.8  DDC  
   
 The VESA(R) Display Data Channel (DDC[tm]) standard allows the monitor to  
 tell the video card (or on some cases the computer directly) about itself;  
 particularly the supported screen resolutions and refresh rates.  
   
 Partial or complete DDC support is available in most of the video drivers.  Partial or complete DDC support is available in most of the video drivers.
 DDC is enabled by default, but can be disabled with a "Device" section entry:  DDC is enabled by default, but can be disabled with a "Device" section entry:
Line 692  Option "NoDDC".  We have support for DDC
Line 569  Option "NoDDC".  We have support for DDC
 abled independently with Option "NoDDC1" and Option "NoDDC2".  abled independently with Option "NoDDC1" and Option "NoDDC2".
   
 At startup the server prints out DDC information from the display, and can  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 mode-  use this information to set the default monitor parameters, or to warn about
 lines yet).  For some drivers, the X server's new -configure option uses the  monitor sync limits if those provided in the configuration file don't match
 DDC information when generating the config file.  those that are detected.
   
 4.8.1  Changed behavior caused by DDC.  5.8.1  Changed behavior caused by DDC.
   
 Several drivers uses DDC information to set the screen size and pitch.  This  Several drivers uses DDC information to set the screen size and pitch.  This
 can be overridden by explicitly resetting it to the and non-DDC default value  can be overridden by explicitly resetting it to the and non-DDC default value
Line 704  can be overridden by explicitly resettin
Line 581  can be overridden by explicitly resettin
 appropriate screen dimensions with the "DisplaySize" keyword in the "Monitor"  appropriate screen dimensions with the "DisplaySize" keyword in the "Monitor"
 section of the config file.  section of the config file.
   
 4.9  GLX and the Direct Rendering Infrastructure (DRI)  5.9  GLX and the Direct Rendering Infrastructure (DRI)
   
 Precision Insight <URL:http://www.precisioninsight.com> was provided with  Direct rendered OpenGLsupport is provided for several hardware platforms by
 funding and support from Red Hat <URL:http://www.redhat.com>, SGI  the Direct Rendering Infrastructure (DRI).  Further information about DRI can
 <URL:http://www.sgi.com>, 3Dfx <URL:http://www.3dfx.com>, Intel  be found at the DRI Project's web site <URL:http://dri.sf.net/>.  The 3D core
 <URL:http://www.intel.com>, ATI <URL:http://www.ati.com>, and Matrox  rendering component is provided by Mesa <URL:http://www.mesa3d.org>.
 <URL:http://www.matrox.com> to integrate the GLX extension for 3D rendering  
 in an X11 window.  The 3D core rendering component is the 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 Ren-  
 dering 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 DRI Project <URL:http://dri.sourceforge.net> on  
 SourceForge <URL:http://www.sourceforge.net>.  
   
 4.10  XVideo Extension (Xv)  5.10  XVideo Extension (Xv)
   
 The XVideo extension is supported in XFree86 4.x.  An XvQueryPortAttributes  The XVideo extension is supported in XFree86 4.x.  An XvQueryPortAttributes
 function has been added as well as support for XvImages.  XvImages are XIm-  function has been added as well as support for XvImages.  XvImages are XIm-
Line 732  ages in alternate color spaces such as Y
Line 596  ages in alternate color spaces such as Y
 through shared memory segments.  This allows clients to display YUV data with  through shared memory segments.  This allows clients to display YUV data with
 high quality hardware scaling and filtering.  high quality hardware scaling and filtering.
   
 4.11  X Rendering Extension (Render)  5.11  X Rendering Extension (Render)
   
 The X Rendering extension provides a 2D rendering model that more closely  The X Rendering extension provides a 2D rendering model that more closely
 matches application demands and hardware capabilities.  It provides a render-  matches application demands and hardware capabilities.  It provides a render-
Line 744  anti-aliased text and geometric objects 
Line 608  anti-aliased text and geometric objects 
 overlays and other image operations not possible with the core X rendering  overlays and other image operations not possible with the core X rendering
 system.  system.
   
 XFree86 4.3.0 provides a partial implementation of Render sufficient for  XFree86 4.4.0 provides a partial implementation of Render sufficient for
 drawing anti-aliased text and image composition.  Still to be implemented are  drawing anti-aliased text and image composition.  Still to be implemented are
 geometric primitives and affine transformation of images.  geometric primitives and affine transformation of images.
   
Line 754  This allows the client greater control o
Line 618  This allows the client greater control o
 access to the available font information while still providing hardware  access to the available font information while still providing hardware
 acceleration.  The Xft library provides font access for Render applications.  acceleration.  The Xft library provides font access for Render applications.
   
 4.11.1  The Xft Library  5.11.1  The Xft Library
   
 On the client side, the Xft library provides access to fonts for applications  On the client side, the Xft library provides access to fonts for applications
 using the FreeType library, version 2.  FreeType currently supports Type1 and  using the FreeType library, version 2.  FreeType currently supports Type1 and
Line 777  tion about which directories contain fon
Line 641  tion about which directories contain fon
 cated font aliasing mechanism.  Documentation for that file is included in  cated font aliasing mechanism.  Documentation for that file is included in
 the Xft(3) man page.  the Xft(3) man page.
   
 4.11.2  FreeType support in Xft  5.11.2  FreeType support in Xft
   
 XFree86 4.3.0 includes sources for FreeType version 2.1.1, and, by default,  XFree86 4.4.0 includes sources for FreeType version 2.1.4, and, by default,
 they are built and installed automatically.  they are built and installed automatically.
   
 4.11.3  Application Support For Anti-Aliased Text  5.11.3  Application Support For Anti-Aliased Text
   
 Only three applications have been modified in XFree86 4.3.0 to work with the  Only three applications have been modified in XFree86 4.4.0 to work with the
 Render extension and the Xft and FreeType libraries to provide anti-aliased  Render extension and the Xft and FreeType libraries to provide anti-aliased
 text.  Xterm, xditview and x11perf.  Migration of other applications may  text.  Xterm, xditview and x11perf.  Migration of other applications may
 occur in future releases.  occur in future releases.
Line 800  aliased, anti-aliased with sub-pixel sam
Line 664  aliased, anti-aliased with sub-pixel sam
 through the Render extension, a path which is currently somewhat slower than  through the Render extension, a path which is currently somewhat slower than
 core text.  core text.
   
 4.12  Other extensions  5.12  Other extensions
   
 The XFree86-Misc extension has not been fully ported to the new server archi-  The XFree86-Misc extension has not been fully ported to the new server archi-
 tecture yet.  This should be completed in a future release.  tecture yet.  This should be completed in a future release.
Line 813  The xgamma utility makes use of this fea
Line 677  The xgamma utility makes use of this fea
 version of the extension is provided.  The missing parts of this extension  version of the extension is provided.  The missing parts of this extension
 and some new features should be completed in a future release.  and some new features should be completed in a future release.
   
 4.13  xedit  5.13  xedit
   
 Xedit has several new features, including:  Xedit has several new features, including:
   
Line 826  Xedit has several new features, includin
Line 690  Xedit has several new features, includin
   
    o Please refer to xedit(1) for more details.     o Please refer to xedit(1) for more details.
   
 4.14  Font support  5.14  Font support
   
 Details about the font support in XFree86 4.x can be found in the  Details about the font support in XFree86 4.x can be found in the
 README.fonts document.  README.fonts document.
   
 4.15  TrueType support  5.15  TrueType support
   
 XFree86 4.x comes with two TrueType backends, known as `xfsft' (the  XFree86 4.x comes with two TrueType backends, known as "FreeType" backend
 "freetype" module) and `X-TrueType' (the "xtt" module).  Both of these back-  (the "freetype" module) and `X-TrueType' (the "xtt" module).  Both of these
 ends are based on the FreeType library.  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.
   
 4.16  CID font support  5.16  CID font support
   
 Support for CID-keyed fonts is included in XFree86 4.x.  The CID-keyed font  Support for CID-keyed fonts is included in XFree86 4.x.  The CID-keyed font
 format was designed by Adobe Systems <URL:http://www.adobe.com> for fonts  format was designed by Adobe Systems <URL:http://www.adobe.com> for fonts
Line 845  with large character sets.  The CID-keye
Line 712  with large character sets.  The CID-keye
 by SGI <URL:http://www.sgi.com>.  See the LICENSE document for a copy of the  by SGI <URL:http://www.sgi.com>.  See the LICENSE document for a copy of the
 CID Font Code Public License.  CID Font Code Public License.
   
 4.17  Internationalisation of the scalable font backends  5.17  Internationalisation of the scalable font backends
   
 XFree86 4.x has a ``fontenc'' layer to allow the scalable font backends to  XFree86 4.x has a ``fontenc'' layer to allow the scalable font backends to
 use a common method of font re-encoding.  This re-encoding makes it possible  use a common method of font re-encoding.  This re-encoding makes it possible
Line 854  layer is used by the Type1 and Speedo ba
Line 721  layer is used by the Type1 and Speedo ba
 TrueType backend.  The `X-TrueType' version of the TrueType backend uses a  TrueType backend.  The `X-TrueType' version of the TrueType backend uses a
 different re-encoding method based on loadable encoding modules.  different re-encoding method based on loadable encoding modules.
   
 4.18  Large font optimisation  5.18  Large font optimisation
   
 The glyph metrics array, which all the X clients using a particular font have  The glyph metrics array, which all the X clients using a particular font have
 access to, is placed in shared memory, so as to reduce redundant memory con-  access to, is placed in shared memory, so as to reduce redundant memory con-
 sumption.  For non-local clients, the glyph metrics array is transmitted in a  sumption.  For non-local clients, the glyph metrics array is transmitted in a
 compressed format.  compressed format.
   
 4.19  Unicode/ISO 10646 support  5.19  Unicode/ISO 10646 support
   
 What is included in 4.x:  What is included in 4.x:
   
Line 894  What is included in 4.x:
Line 761  What is included in 4.x:
    o Both the xfsft (the "freetype" module) and the X-TrueType (the "xtt"     o Both the xfsft (the "freetype" module) and the X-TrueType (the "xtt"
      module) TrueType font backends support Unicode-encoded fonts.       module) TrueType font backends support Unicode-encoded fonts.
   
 4.20  Luxi fonts from Bigelow and Holmes  5.20  Xlib Compose file support and extensions
   
   A more flexible Compose file processing system was added to Xlib in XFree86
   4.4.0.  The compose file is searched for in the following order:
   
     1.  If the environment variable $XCOMPOSEFILE is set, its value is used as
         the name of the Compose file.
   
     2.  If the user's home directory has a file named ".XCompose", it is used
         as the Compose file.
   
     3.  The old method is used, and the compose file is "<xlocaledir>/<locale-
         name>/Compose".
   
   Compose files can now use an "include" instruction.  This allows local modi-
   fications to be made to existing compose files without including all of the
   content directly.  For example, the system's iso8859-1 compose file can be
   included with a line like this:
   
        include "/usr/X11R6/lib/X11/locale/iso8859-1/Compose"
   
   There are two substitutions that can be made in the file name of the include
   instruction.  %H expands to the user's home directory (the $HOME environment
   variable), and %L expands to the name of the locale specific Compose file
   (i.e., "<xlocaledir>/<localename>/Compose").
   
   For example, you can include in your compose file the default Compose file by
   using:
   
        include "%L"
   
   and then rewrite only the few rules that you need to change.  New compose
   rules can be added, and previous ones replaced.
   
   Finally, it is no longer necessary to specify in the right part of a rule a
   locale encoded string in addition to the keysym name.  If the string is omit-
   ted, Xlib figures it out from the keysym according to the current locale.
   I.e., if a rule looks like:
   
        <dead_grave> <A> : "\300" Agrave
   
   the result of the composition is always the letter with the "\300" code.  But
   if the rule is:
   
        <dead_grave> <A> : Agrave
   
   the result depends on how Agrave is mapped in the current locale.
   
   5.21  Luxi fonts from Bigelow and Holmes
   
 XFree86 now includes the ``Luxi'' family of Type 1 fonts and TrueType fonts.  XFree86 now includes the ``Luxi'' family of Type 1 fonts and TrueType fonts.
 This family consists of the fonts ``Luxi Serif'', ``Luxi Sans'' and  This family consists of the fonts ``Luxi Serif'', ``Luxi Sans'' and
Line 919  as well as in the License document.  For
Line 834  as well as in the License document.  For
 <design@bigelowandholmes.com> or <info@urwpp.de>, or consult the URW++ web  <design@bigelowandholmes.com> or <info@urwpp.de>, or consult the URW++ web
 site <URL:http://www.urwpp.de>.  site <URL:http://www.urwpp.de>.
   
 4.21  Directory rearrangements  6.  Credits
   
   This section lists the credits for the XFree86 4.4.0 release.  For a more
   detailed breakdown, refer to the CHANGELOG file in the XFree86 source tree,
   the cvs-commit archives <URL:http://www.mail-archive.com/cvs-com-
   mit@xfree86.org/maillist.html>, or the 'cvs log' information for individual
   source files.
   
         New Features, Enhancements and Updates:
   
                     IPv6 support:
                           Alan Coopersmith, Fabio Massimo Di Nitto, Marc Aurele
                           La France, Matthieu Herrb, David H. Dawes.
   
                     NVIDIA 'nv' driver rewrite:
                           Mark Vojkovich.
   
                     SiS driver development:
                           Thomas Winischhofer.
   
                     New VIA video driver:
                           VIA, Alan Cox, Luc Verhaegen, Thomas Hellstr.
   
                     Intel 'i810' driver fixes and stability improvements:
                           Egbert Eich, David H. Dawes, Christian Zietz
   
                     Improved and more flexible Compose system:
                           Ivan Pascal.
   
                     Automatic configuration for the XFree86 server:
                           David H. Dawes.
   
                     Reworked FreeType font backend module:
                           Chisato Yamauchi and the After X-TT Project.
   
                     Xterm fixes, maintenance and enhancements:
                           Thomas E. Dickey.
   
                     Mac OS X enhancements:
                           Torrey T. Lyons, John Harper.
   
                     GNU/Hurd updates and preliminary GNU/KFreeBSD and GNU/KNetBSD
                                support:" Robert Millan.
   
                     SCO support updates:
                           Kean Johnston.
   
                     Bitstream Vera fonts:
                           Bitstream, Inc, and the GNOME Foundation.
   
         Integration:
   
                     General Integration of Submissions:
                           Egbert Eich, David H. Dawes, Ivan Pascal, Alan Houri-
                           hane, Matthieu Herrb.
   
                     DRI Integration:
                           Alan Hourihane.
   
         Release Engineering:
               David H. Dawes.
   
         Patches and other submissions (in alphabetical order):
               Roi a Torkilsheyggi, Dave Airlie, Andrew Aitchison, Marco Antonio
               Alvarez, Alexandr Andreev, Jack Angel, Eric Anholt, Ani, Juuso
               erg, Sergey Babkin, Alexey Baj, Bang Jun-Young, Uberto Barbini,
               Matthew W. S. Bell, Vano Beridze, Hiroyuki Bessho, Andrew Bevitt,
               Christian Biere, Martin Birgmeier, Jakub Bogusz, Le Hong Boi,
               Paul Bolle, Charl Botha, Stanislav Brabec, Eric Branlund, Rob
               Braun, Peter Breitenlohner, Michael Breuer, Kevin Brosius, Fred-
               erick Bruckman, Oswald Buddenhagen, Nilg Belma Buger, Julian
               Cable, Yukun Chen, Ping Cheng, Juliusz Chroboczek, Fred Clift,
               Alan Coopersmith, Martin Costabel, Alan Cox, Michel Dzer, David
               Dawes, Leif Delgass, Richard Dengler, John Dennis, Thomas Dickey,
               Randy Dunlap, Chris Edgington, Paul Eggert, Paul Elliott,
               Emmanuel, Visanu Euarchukiati, Mike Fabian, Rik Faith, Brian
               Feldman, Wu Jian Feng, Kevin P. Fleming, Jose Fonseca, Hugues
               Fournier, Miguel Freitas, Quentin Garnier, Bre Gaup, Michael
               Geddes, Frank Giessler, Hansruedi Glauser, Wolfram Gloger,
               Alexander Gottwald, Guido Guenther, Ralf Habacker, Bruno Haible,
               Lindsay Haigh, John Harper, James Harris, Mike A. Harris, Bryan
               W. Headley, John Heasley, Thomas Hellstr, Matthieu Herrb,
               Jonathan Hough, Alan Hourihane, Joel Ray Holveck, Harold L Hunt
               II, Ricardo Y. Igarashi, Mutsumi ISHIKAWA , Tsuyoshi ITO, Kean
               Johnston, Nicolas JOLY, Phil Jones, Roman Kagan, Theppitak
               Karoonboonyanan, Etsushi Kato, Koike Kazuhiko, Aidan Kehoe, Juer-
               gen Keil, Andreas Kies, Thomas Klausner, Mario Klebsch, Egmont
               Koblinger, Vlatko Kosturjak, Kusanagi Kouichi, Mel Kravitz, Peter
               Kunzmann, Nick Kurshev, Mashrab Kuvatov, Marc La France, Radics
               Laszlo, Zarick Lau, Nolan Leake, Michel Lespinasse, Noah Levitt,
               Dave Love, H.J. Lu, Lubos Lunak, Sven Luther, Torrey T. Lyons,
               Calum Mackay, Paul Mackerras, Roland Mainz, Kevin Martin, Michal
               Maruska, Kensuke Matsuzaki, maxim, Stephen McCamant, Ferris
               McCormick, Luke Mewburn, Nicholas Miell, Robert Millan, Hisashi
               MIYASHITA, Gregory Mokhin, Patrik Montgomery, Joe Moss, Josselin
               Mouette, Frank Murphy, Reiko Nakajima, Paul Nasrat, Dan Nelson,
               Bastien Nocera, Alexandre Oliva, Hideki ONO, Peter Osterlund,
               Sergey V. Oudaltsov, Smus Ciardhun, Bob Paauwe, Paul
               Pacheco, Tom Pala, Ivan Pascal, T. M. Pederson, Earle F. Phil-
               hower III, Nils Philippsen, Manfred Pohler, Alexander Pohoyda,
               Alain Poirier, Arnaud Quette, Jim Radford, Dale Rahn, Lucas Cor-
               reia Villa Real, RenRebe, Tyler Retzlaff, Sebastian Rittau, Tim
               Roberts, Alastair M. Robinson, Branden Robinson, Daniel Rock, Ian
               Romanick, Bernhard Rosenkraenzer, Ms Rullgd, Andriy Rysin,
               Supphachoke Santiwichaya, Pablo Saratxaga, Matthias Scheler, Jens
               Schweikhardt, Danilo Segan, Shantonu Sen, Stas Sergeev, Jungshik
               Shin, Nikola Smolenski, Andreas Stenglein, Paul Stewart, Alexan-
               der Stohr, Alan Strohm, Will Styles, James Su, Mike Sulivan,
               Ville Syrjala, Slava Sysoltsev, Akira TAGOH, Toshimitsu Tanaka,
               Akira Taniguchi, Owen Taylor, Neil Terry, Jonathan Thambidurai,
               John Tillman, Adam Tlalka, Linus Torvalds, Christian Tosta, War-
               ren Turkal, Stephen J. Turnbull, Ted Unangst, Mike Urban, Simon
               Vallet, Thuraiappah Vaseeharan, Luc Verhaegen, Yann Vernier,
               Michail Vidiassov, Sebastiano Vigna, Mark Vojkovich, Stephane
               Voltz, Boris Weissman, Keith Whitwell, Thomas Winischhofer, Eric
               Wittry, Kim Woelders, Roy Wood, Jason L. Wright, Joerg Wunsch,
               Chisato Yamauchi, Hui Yu.
   
         Docbook/XML conversion:
               John Himpel and the XFree86 documentation team.
   
         Webmaster:
               Georgina O. Economou
   
         Hosting:
               Internet Systems Consortium, Inc <URL:http://www.isc.org/>.
   
   7.  Attributions/Acknowledgements
   
   This product includes software developed by The XFree86 Project, Inc
   (http://www.xfree86.org/) and its contributors.
   
   This produce includes software that is based in part of the work of the
   FreeType Team (http://www.freetype.org).
   
   This product includes software developed by the University of California,
   Berkeley and its contributors.
   
   This product includes software developed by Christopher G. Demetriou.
   
   This product includes software developed by the NetBSD Foundation, Inc. and
   its contributors
   
 Some changes to the installed XFree86 directory structure have been imple-  This product includes software developed by X-Oz Technologies (http://www.x-
 mented for 4.x.  One important change is a modified search path for the X  oz.com/).
 server's XF86Config file.  The details of this can be found in the XF86Config  
 manual page.  The other main change is moving most of the run-time configura-  
 tion files to /etc/X11, with symbolic links in the old /usr/X11R6/lib/X11  
 location pointing to the new location.  Some run-time generated files are now  
 located under the appropriate subdirectories of /var, again with the relevant  
 symbolic links in the old location.  
   
      Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.81 2003/02/27 00:45:05 dawes Exp $       Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.116 dawes Exp $
   
   
 $XFree86: xc/RELNOTES,v 1.17 2003/02/27 01:44:02 dawes Exp $  $XFree86: xc/RELNOTES,v 1.38 2004/02/28 16:37:58 dawes Exp $

Legend:
Removed from v.1.1.1.6  
changed lines
  Added in v.1.1.1.7

CVSweb <webmaster@jp.NetBSD.org>