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 Cc: cygwin@tlinx.org Subject: Re: running openGL application remotely using ssh -X and cygwin/x ,extension "NV-GLX" missing on display "localhost:10.0 Date: Tue, 29 Apr 2014 12:34:00 -0000 [thread overview] Message-ID: <535F9C3E.5000204@dronecode.org.uk> (raw) In-Reply-To: <535EC1CC.6040502@tlinx.org> On 28/04/2014 22:02, Linda Walsh wrote: > Jon TURNEY wrote: >> Yes, this should work. > ---- > *But*, I'm pretty sure it doesn't anymore since the "Xgl" extension > that was used to transport the openGL commands between client/server > was removed from xorg's Xserver. You seem to be confusing Xgl (an X server implementation) and GLX (an X protocol extension). While they do contain the same letters in a different order, they are very different things. > AIGLX doesn't work with client's native openGL drives when the > DISPLAY isn't local. Instead, it sends full-frame-buffer updates to > simulate what would be happening -- something that "appears" to work > correctly for small OpenGL windows. But is entirely 'faked' (not > really remote openGL that used the Server's acceleration Hardware. > > Which would give you unaccelerated frame-buffer updates to simulate > the effect. Not quite what used to be available. This is also totally wrong. You are (more or less) describing how mesa's direct software rendering works (which is usually the default path for remote displays) which is completely different to AIGLX (where GL commands are sent via the GLX protocol to the X server and rendered using acceleration there) So, again, please stop spreading misinformation. I'm sure there are bugs in and limitations with OpenGL and the XWin server, but if you have a problem, please don't hijack someone else's thread, but report it in sufficient detail for me to try to reproduce it. -- 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/
prev parent reply other threads:[~2014-04-29 12:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-24 22:45 Biris, Octavian 2014-04-26 11:52 ` Jon TURNEY 2014-04-27 23:01 ` Biris, Octavian 2014-04-28 21:02 ` Linda Walsh 2014-04-29 12:34 ` Jon TURNEY [this message]
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=535F9C3E.5000204@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=cygwin@tlinx.org \ /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).