public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Subject: [ANNOUNCEMENT] Updated: xorg-server-1.9.0-1 (TEST) Date: Thu, 30 Sep 2010 15:33:00 -0000 [thread overview] Message-ID: <announce.4CA4AC19.8030608@dronecode.org.uk> (raw) The following packages have been updated in the Cygwin distribution: *** xorg-server-1.9.0-1 *** xorg-server-dmx-1.9.0-1 This package contains XWin and the other X.Org X11 servers. This is the first official release of the xserver 1.9 series. It is currently available as a test release, and will be made stable in approximately one week if no major regressions are reported. In addition to the usual upstream fixes and improvements, this contains the following cygwin-specific changes: * fix a drawing crash, which could occur after moving a window in multiwindow mode, caused by incorrect initialization of composite position data * fix a clipboard-related crash which could occur during XDMCP session startup (thanks to Michel Hummel for the patch) * added Turkish keyboard layout detection * add -displayfd option (experimental), which may be useful in Terminal Server environments, see [1] for a discussion of how and why you might want to use this * various crash fixes for -resize. Also fix -resize from turning itself on in multiwindow mode even when not asked for. -resize will be enabled by default in multiwindow mode after more testing. * enable WGL AIGLX code and -wgl option which has been merged upstream, and various GLX fixes Server-side Hardware Accelerated OpenGL (AIGLX) =============================================== This release adds experimental support for hardware accelerated OpenGL rendering in the X server using the native WGL interface. * You need to provide the command line option '-wgl' to the X server to turn on the use of native Windows OpenGL to implement GLX. If you don't use this option, the server will carry on using software rendering. * The currently shipped cygwin mesa libGL is built in such a way that it does not support indirect rendering (rendering takes place on the server), only client-side rendering. ONLY REMOTE CLIENTS FROM UNIX SYSTEMS WILL WORK CURRENTLY. An updated libGL will be made available at some point in the future. * mesa's libGL prefers to use client-side rendering and transfer the image to the server using xlib. To force the use of GLX, so rendering is indirect (takes place on the server), and thus can be accelerated, you must export the environment variable LIBGL_ALWAYS_INDIRECT with a non-zero value before starting the client application. * If you have set things up successfully, 'glxinfo | grep OpenGL' should return something mentioning your graphics card vendor. If it mentions Mesa, you still have software rendering * As before, only multiwindow/mwextwm modes are supported. Software rendering is always used on screens which do not have 1 native window per X window. Removing this restriction requires a way to tell the native OpenGL to transform/clip to the portion of the native window occupied by the X window in the single native window modes. [1] http://cygwin.com/ml/cygwin-xfree/2010-09/msg00040.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next reply other threads:[~2010-09-30 15:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-30 15:33 Jon TURNEY [this message] 2010-09-30 19:03 ` michel hummel 2010-10-06 14:11 ` Jon TURNEY 2010-10-02 20:37 ` R: " Marco Atzeri 2010-10-02 20:54 ` Christopher Faylor 2010-10-02 21:16 ` Christopher Faylor 2010-10-02 21:22 ` Marco Atzeri 2010-10-02 21:42 ` Marco Atzeri
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=announce.4CA4AC19.8030608@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).