[PATCH xf86-video-amdgpu 2/2] Fix warnings for unused variables

Remove some unused variables to fix the compiling warnings. Signed-off-by: Jammy Zhou --- src/amdgpu_dri3.c | 2 -- src/amdgpu_glamor.c | 2 -- src/amdgpu_kms.c| 6 -- 3 files changed, 4 insertions(+), 6 deletions(-) diff --git a/src/amdgpu_dri3.c

[PATCH xf86-video-amdgpu 1/2] Fix crash in PCI probe path (v3)

The crash is caused by the NULL value returned by AMDGPUPTR(pScrn), because the driverPrivate is not allocated yet in PciProbe phase, and it is usually done in the PreInit phase. Use pAMDGPUEnt->fd instead of info->dri2.drm_fd to avoid AMDGPUInfoPtr related code in amdgpu_open_drm_master, so that

Re: [PATCH xf86-video-amdgpu 1/2] Fix crash in PCI probe path (v3)

On 28.10.2015 22:00, William Lewis wrote: > Would it not make more sense to set pAMDGPUEnt->fd to -1 beneath the > error_amdgpu tag? No: > On 10/28/15 08:24, Jammy Zhou wrote: >> +pAMDGPUEnt = pPriv->ptr; [...] >> @@ -266,7 +256,6 @@ static Bool amdgpu_get_scrninfo(int

Re: [PATCH xf86-video-amdgpu 1/2] Fix crash in PCI probe path (v3)

Would it not make more sense to set pAMDGPUEnt->fd to -1 beneath the error_amdgpu tag? On 10/28/15 08:24, Jammy Zhou wrote: > The crash is caused by the NULL value returned by AMDGPUPTR(pScrn), > because the driverPrivate is not allocated yet in PciProbe phase, > and it is usually done in the

Re: [PATCH:xorg-docs 3/4] X.man: document protocol/ syntax in display string

Should we also mention the extension that was added for launchd support where we DISPLAY=[.] > On Oct 27, 2015, at 19:45, Alan Coopersmith > wrote: > > See > http://www.x.org/releases/X11R7.7/doc/libX11/libX11/libX11.html#Opening_the_Display > > Signed-off-by:

Strange utf8/iso encoding problem with bitmap fonts

Hi, after upgrading from SLES 11 to SLES 12 one of my application that is using bitmap fonts (that I try to keep for all apps as I prefer them over antialised ttf fonts. etc) doesn't show certain characters. E.g. the signor certain characters with accents. After long debugging I figured out

[Xorg-driver-geode] [Bug 92542] Geode cannot be used with GNOME because it requires root priviledges

https://bugs.freedesktop.org/show_bug.cgi?id=92542 --- Comment #1 from Martin-Éric Racine --- Someone had started developing a KMS driver for the Geode LX: https://gitorious.org/lx This would at least cover the OLPC XO-1 and a fairly large number of recent thin

[PATCH] present: Execute right away if target_msc equals current_msc

It is according to the protocol: "If 'options' contains PresentOptionAsync, and the 'target-msc' is less than or equal to the current msc for 'window', then the operation will be performed as soon as possible, not necessarily waiting for the next vertical blank interval." Signed-off-by: Jammy

Re: [PATCH:xserver 1/3] Xorg.man: move XLOCAL details to X(7) man page instead

Series: Reviewed-by: Jeremy Huddleston Sequoia > On Oct 27, 2015, at 19:44, Alan Coopersmith > wrote: > > These settings affect clients, not server, so belong there, next to > the information about how to set $DISPLAY. > > Signed-off-by: Alan

[ANNOUNCE] xorg-server 1.17.4

Minor brown-bag release. The important fix here is Martin's clientsWritable change which fixes a crash when built against xproto 7.0.28. Adam Jackson (1):   xserver 1.17.4 Julien Cristau (1):   Xext: fix build with --disable-xace Martin Peres (1):   os: make sure the clientsWritable

[ANNOUNCE] xorg-server 1.17.4

Minor brown-bag release. The important fix here is Martin's clientsWritable change which fixes a crash when built against xproto 7.0.28. Adam Jackson (1):   xserver 1.17.4 Julien Cristau (1):   Xext: fix build with --disable-xace Martin Peres (1):   os: make sure the clientsWritable

Re: [PATCH:macros] XORG_MANPAGE_SECTIONS: limit SVR4 man page sections to Solaris 2.0-11

On 10/27/15 07:03 PM, Jeremy Huddleston Sequoia wrote: On Oct 27, 2015, at 16:06, Alan Coopersmith wrote: All others (including other SunOS/Solaris releases) use the traditional Bell Labs / BSD / Linux section numbering. Signed-off-by: Alan Coopersmith

Re: [PATCH:xorg-docs 3/4] X.man: document protocol/ syntax in display string

On 10/28/15 07:46 AM, Jeremy Huddleston Sequoia wrote: Should we also mention the extension that was added for launchd support where we DISPLAY=[.] That sounds like a good followup patch for you to submit, since I didn't even remember that existed, much less know how to describe it. --

Re: [PATCH:xorg-docs 3/4] X.man: document protocol/ syntax in display string

Sent from my iPhone... > On Oct 28, 2015, at 10:01, Alan Coopersmith > wrote: > >> On 10/28/15 07:46 AM, Jeremy Huddleston Sequoia wrote: >> Should we also mention the extension that was added for launchd support >> where we DISPLAY=[.] > > That sounds like a

Re: [PATCH xf86-video-amdgpu 2/2] Fix warnings for unused variables

On Wed, Oct 28, 2015 at 9:24 AM, Jammy Zhou wrote: > Remove some unused variables to fix the compiling warnings. > > Signed-off-by: Jammy Zhou For the series: Reviewed-by: Alex Deucher > --- > src/amdgpu_dri3.c | 2 -- >

Re: [PATCH:xserver 1/3] Xorg.man: move XLOCAL details to X(7) man page instead

On Wed, 2015-10-28 at 00:01 -0700, Jeremy Huddleston Sequoia wrote: > Series: > > Reviewed-by: Jeremy Huddleston Sequoia remote: I: patch #63024 updated using rev 75157b7dbf4ed4db0492328a44e4e67dda83f769. remote: I: patch #63025 updated using rev

Re: [PATCH xf86-video-amdgpu 1/2] Fix crash in PCI probe path (v3)

On 28.10.2015 22:24, Jammy Zhou wrote: > The crash is caused by the NULL value returned by AMDGPUPTR(pScrn), > because the driverPrivate is not allocated yet in PciProbe phase, > and it is usually done in the PreInit phase. > > Use pAMDGPUEnt->fd instead of info->dri2.drm_fd to avoid

[PATCH xf86-video-amdgpu] Call present_event_notify directly if target_msc <= crtc_msc (v2)

Do present immediately in this case. v2: fix the overflow Change-Id: I25b9212169ccbf572b88c033dc09c0ac5cfa4812 Signed-off-by: Jammy Zhou --- src/amdgpu_present.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/src/amdgpu_present.c b/src/amdgpu_present.c

Re: [PATCH] present: Execute right away if target_msc equals current_msc

On 28.10.2015 19:39, Jammy Zhou wrote: > It is according to the protocol: > > "If 'options' contains PresentOptionAsync, and the 'target-msc' > is less than or equal to the current msc for 'window', then > the operation will be performed as soon as possible, not > necessarily waiting for the next

[PATCH xf86-video-amdgpu] Call present_event_notify directly if target_msc <= crtc_msc

Do present immediately in this case. Signed-off-by: Jammy Zhou --- src/amdgpu_present.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/src/amdgpu_present.c b/src/amdgpu_present.c index 5e5ed72..82b22b7 100644 --- a/src/amdgpu_present.c +++