[ANNOUNCE] xf86-video-geode 2.11.19

Adam Jackson (1): Adapt Block/WakeupHandler signature for ABI 23 Martin-Éric Racine (1): Geode 2.11.19 git tag: xf86-video-geode-2.11.19 https://xorg.freedesktop.org/archive/individual/driver/xf86-video-geode-2.11.19.tar.bz2 MD5: 015f7111e41441324be2decca3bdb389

Re: Multiplexing general windows similar to terminator

I believe fluxbox has had tabbed windows for quite some time, and in i3 you can also put multiple windows in the same tile and tab between them. Maybe those could help you get what you want? Best, - Timo ___ xorg@lists.x.org: X.Org support Archives:

Fw: Xt / Motif C++ application hangs in the XtDispatchEvent call

Hope fully this should be posted on xorg@lists.x.org so that all can see.. Sorry I missed to post there.. Note: Forwarded message attached -- Original Message -- From: "Subrata Dasgupta"subrata_u...@rediffmail.com To: wha...@bfs.de,thomas.luebk...@gmx.de,alan.coopersm...@oracle.com Subject:

Re: Multiplexing general windows similar to terminator

Hi, It's been a while now, and deciding was hard (basically had other stuff on my mind lately), but I think I'll have some red pills. Probably will need more than one so they can act fast.If you could recommend some good documentation, it would be great! I will most likely not be able to start

Re: Fw: Xt / Motif C++ application hangs in the XtDispatchEvent call

On Mon, Dec 12, 2016 at 08:15:14AM -, Subrata Dasgupta wrote: > Hope fully this should be posted on xorg@lists.x.org so that all can see.. > Sorry I missed to post there.. > > Note: Forwarded message attached > > -- Original Message -- > > From: "Subrata

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 11:15 AM, Adam Jackson wrote: > On Fri, 2016-12-09 at 14:09 -0500, Long Vu wrote: >> Hi, >> >> We use Xvfb to avoid having to run an X server on our build machine. >> >> We got this error with Xvfb that we do not have when we were running a >> real VNC

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 12:08 PM, Long Vu wrote: > On Mon, Dec 12, 2016 at 11:15 AM, Adam Jackson wrote: >> On Fri, 2016-12-09 at 14:09 -0500, Long Vu wrote: >>> Hi, >>> >>> We use Xvfb to avoid having to run an X server on our build machine. >>> >>> We got

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, 2016-12-12 at 12:13 -0500, Long Vu wrote: > Would it be this xvfb-run option ? > > -s ARGS   --server-args=ARGSarguments (other than server number and > "-nolisten tcp") to pass to the Xvfb > server >

How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

Hi, We use Xvfb to avoid having to run an X server on our build machine. We got this error with Xvfb that we do not have when we were running a real VNC server just to provide X. ES2 Prism: Error - GLX extension is not supported GLX version 1.3 or higher is required Xlib: extension "RANDR"

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Fri, 2016-12-09 at 14:09 -0500, Long Vu wrote: > Hi, > > We use Xvfb to avoid having to run an X server on our build machine. > > We got this error with Xvfb that we do not have when we were running a > real VNC server just to provide X. > > ES2 Prism: Error - GLX extension is not supported

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 1:06 PM, Long Vu wrote: > On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson wrote: >> On Mon, 2016-12-12 at 12:13 -0500, Long Vu wrote: >> >>> Would it be this xvfb-run option ? >>> >>> -s ARGS --server-args=ARGSarguments

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, 2016-12-12 at 13:51 -0500, Long Vu wrote: > On Mon, Dec 12, 2016 at 1:06 PM, Long Vu > wrote: > > On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson > > wrote: > > > On Mon, 2016-12-12 at 12:13 -0500, Long Vu wrote: > > > > > > > Would it be this

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On 12/12/16 19:51, Long Vu wrote: > On Mon, Dec 12, 2016 at 1:06 PM, Long Vu wrote: >> On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson wrote: >>> On Mon, 2016-12-12 at 12:13 -0500, Long Vu wrote: >>> Would it be this xvfb-run option ? -s ARGS

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 8:27 PM, Antoine Martin wrote: > On 12/12/16 19:51, Long Vu wrote: >> On Mon, Dec 12, 2016 at 1:06 PM, Long Vu wrote: >>> On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson wrote: On Mon, 2016-12-12 at 12:13

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 2:34 PM, Eric Gunther wrote: > On Mon, 2016-12-12 at 13:51 -0500, Long Vu wrote: > > I don't know if this will help, but previously adam had said: > >> How are you launching Xvfb? I believe it defaults to 8bpp, but GLX > only >> works at 16 or 32bpp.

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson wrote: > On Mon, 2016-12-12 at 12:13 -0500, Long Vu wrote: > >> Would it be this xvfb-run option ? >> >> -s ARGS --server-args=ARGSarguments (other than server number and >> "-nolisten

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On 12/12/16 20:37, Roland Mainz wrote: > On Mon, Dec 12, 2016 at 8:27 PM, Antoine Martin wrote: >> On 12/12/16 19:51, Long Vu wrote: >>> On Mon, Dec 12, 2016 at 1:06 PM, Long Vu wrote: On Mon, Dec 12, 2016 at 12:20 PM, Adam Jackson

Re: How to avoid this Xvfb error: ES2 Prism: Error - GLX extension is not supported

On Mon, 2016-12-12 at 14:39 -0500, Long Vu wrote: > On Mon, Dec 12, 2016 at 2:34 PM, Eric Gunther > wrote: > > On Mon, 2016-12-12 at 13:51 -0500, Long Vu wrote: > > > > I don't know if this will help, but previously adam had said: > > > > > How are you launching Xvfb? I

[ANNOUNCE] xf86-video-geode 2.11.19

Adam Jackson (1): Adapt Block/WakeupHandler signature for ABI 23 Martin-Éric Racine (1): Geode 2.11.19 git tag: xf86-video-geode-2.11.19 https://xorg.freedesktop.org/archive/individual/driver/xf86-video-geode-2.11.19.tar.bz2 MD5: 015f7111e41441324be2decca3bdb389

[PATCH libX11] German Locale Updates

This commit adds the necessary changes to recognise the new de_IT locale present in GLIBC 2.24 onwards. It fixes also a small issue in the de_LI ISO8859-15 locale mapping. https://bugs.freedesktop.org/show_bug.cgi?id=98857 Signed-off-by: Matthias Dieter Wallnöfer ---

[Bug 99060] memory corruption after running INSIDE

https://bugs.freedesktop.org/show_bug.cgi?id=99060 Grazvydas Ignotas changed: What|Removed |Added CC|

Re: [PATCH xserver] tests: Build test programs only when testing

On Sun, Dec 11, 2016 at 07:45:44AM +0500, Mihail Konev wrote: > Signed-off-by: Mihail Konev > --- > In case it is the [exact] opposite of the effect intended > (test linking of test programs on every build), > should then this be conditioned as a ./configure option? NAK, there's a

[Xorg-driver-geode] [ANNOUNCE] xf86-video-geode 2.11.19

Adam Jackson (1): Adapt Block/WakeupHandler signature for ABI 23 Martin-Éric Racine (1): Geode 2.11.19 git tag: xf86-video-geode-2.11.19 https://xorg.freedesktop.org/archive/individual/driver/xf86-video-geode-2.11.19.tar.bz2 MD5: 015f7111e41441324be2decca3bdb389

[PATCH xserver 5/6] xfree86: Allow overriding primary GPU detection from an OutputClass section

Allow using: Option "PrimaryGPU" "yes" In an OutputClass section to override the default primary GPU device selection which selects the GPU used as output by the firmware. If multiple output devices match an OutputClass section with the PrimaryGPU option set, the first one enumerated becomes

[PATCH xserver 6/6] xfree86: Add ModulePath support for OutputClass config Sections

Allow OutputClass config snippets to modify the module-path. Note that any specified ModulePaths will be pre-pended to the normal ModulePath. The idea behind this is that any output hardware specific modules should have preference over the normal modules. One use-case for this is the nvidia

[PATCH xserver 3/6] xfree86: Add options support for OutputClass Options

Add support for setting options in OutputClass Sections and having these applied to any matching output devices. Signed-off-by: Hans de Goede --- hw/xfree86/common/xf86Option.c | 5 - hw/xfree86/common/xf86platformBus.c | 42 +

[PATCH xserver 0/6] xfree86: Extend OutputClass config sections

Hi All, This patch series main goal (*) is to allow the nvidia binary driver to install a xorg.conf snippet with the following contents: Section "OutputClass" Identifier "nvidia" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" Option

[PATCH xserver 4/6] xfree86: xf86platformProbe: split finding pci-info and setting primary GPU

This is a preparation patch for allowing an OutputClass section to override the default primary GPU device selection. Signed-off-by: Hans de Goede --- hw/xfree86/common/xf86platformBus.c | 23 +++ 1 file changed, 15 insertions(+), 8 deletions(-) diff

[PATCH xserver 2/6] xfree86: Make OutputClassMatches take a xf86_platform_device

Make OutputClassMatches directly take a xf86_platform_device as argument, rather then an index into xf86_platform_devices. This makes things easier for callers which already have a xf86_platform_device pointer. Signed-off-by: Hans de Goede ---

[PATCH xserver 1/6] xfree86: Free devlist returned by xf86MatchDevice

xf86MatchDevice returns a dynamically allocated list of GDevPtr-s, free this when we're done with it. Signed-off-by: Hans de Goede --- hw/xfree86/common/xf86platformBus.c | 4 1 file changed, 4 insertions(+) diff --git a/hw/xfree86/common/xf86platformBus.c

[PATCH xserver] xinerama: Swap the response in RRXineramaWriteMonitor.

diff --git a/randr/rrxinerama.c b/randr/rrxinerama.c index b6e9586..8f499df 100644 --- a/randr/rrxinerama.c +++ b/randr/rrxinerama.c @@ -260,6 +260,13 @@ RRXineramaWriteMonitor(ClientPtr client, RRMonitorPtr monitor) scratch.width = monitor->geometry.box.x2 - monitor->geometry.box.x1;

Re: [PATCH xserver 05/11] vfb: Remove -pixdepths option

On Sat, 2016-12-10 at 09:09 -0800, Keith Packard wrote: > > Adam Jackson writes: > > > This really isn't especially useful, and we'd rather not be in the > > business of supporting arbitrary pixel formats. > > I recall playing with this when I heard of a strange piece of

Re: [edid-decode] [PATCH 2/2] Calculate DisplayID checksums. Refactor do_checksum.

Am 10.12.2016 20:44, schrieb Mark Ferry: > --- > edid-decode.c | 40 +--- > 1 file changed, 25 insertions(+), 15 deletions(-) > > diff --git a/edid-decode.c b/edid-decode.c > index c18697f..6df2b6e 100644 > --- a/edid-decode.c > +++ b/edid-decode.c > @@

Re: [PATCH xserver 08/11] shadow: Lift 32->24 conversion from modesetting to dix

On Sat, 2016-12-10 at 09:24 -0800, Keith Packard wrote: > Adam Jackson writes: > > > Signed-off-by: Adam Jackson > > Seems like a bunch of the other logic in msUpdatePacked might want to > move someday too? It might be cool to move that feature up, yeah. I

Re: [PATCH xserver 11/11] shadow: Remove unused shadowAlloc

On Sat, 2016-12-10 at 09:27 -0800, Keith Packard wrote: > Adam Jackson writes: > > > Signed-off-by: Adam Jackson > > Reviewed-by: Keith Packard Merged the reviewed bits, thanks: remote: I: patch #126653 updated using rev

Re: [PATCH xserver 05/11] vfb: Remove -pixdepths option

Adam Jackson writes: > I'm thinking we could just make the pixmap format list constant: depths > 1, 4, 8, 12, 15, 16, 18, 24, 30, 32. (Yes 18, apparently r6g6b6 is a > thing.) Why leave anything out, after all. Sounds good. It almost does that already... -- -keith

[PATCH xserver] Revert "damage: Make damageRegionProcessPending take a damage not a drawable"

The commit message makes the assertion that the code below damage is not allowed to change whether there's a damage monitor for the drawable. That turns out not to be the case! exa's mixed code, at least, will create and destroy a damage in PrepareAccess. The destroy path can then be catastrophic,