Attachment 1474 Details for Bug 1800 – [FIXED_X11R68x] Juliens patch (from email), updated to 2004-12-04-trunk + Changelog entry

[patch] [FIXED_X11R68x] Juliens patch (from email), updated to 2004-12-04-trunk + Changelog entry

patch.gudiff (text/plain), 3.33 KB, created by Roland Mainz on 2004-12-04 20:37:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Roland Mainz

Created: 2004-12-04 20:37:53 UTC

Size: 3.33 KB

patch

obsolete

>Index: xc/ChangeLog
>===================================================================
>RCS file: /cvs/xorg/xc/ChangeLog,v
>retrieving revision 1.570
>diff -u -2 -0 -r1.570 ChangeLog
>--- xc/ChangeLog	4 Dec 2004 22:34:52 -0000	1.570
>+++ xc/ChangeLog	5 Dec 2004 04:33:40 -0000
>@@ -1,20 +1,27 @@
>+2004-12-04 Roland Mainz <roland.mainz@nrubsig.org>
>+	* xc/programs/Xserver/Xprint/ps/PsInit.c
>+	Bugzilla #1800 (https://freedesktop.org/bugzilla/show_bug.cgi?id=1800):
>+	Fix Postscript DDX's 1bit StaticGray visual to report only 1bit
>+	of significant bits in color specification (instead of 8bits).
>+	Patch by Julien Lafon <julien.lafon@gmail.com>
>+
> 2004-12-04  Daniel Stone  <daniel@freedesktop.org>
> 
> 	* programs/Xserver/hw/xfree86/drivers/ati/r128_accel.c:
> 	Retry CCE idle commands until the (higher) timeout is reached, and
> 	properly stop the engine if we totally fail -- gets rid of serious
> 	performance issues and lockups with r128 DRI (closes: #1889).
> 
> 	* programs/Xserver/hw/xfree86/drivers/ati/r128_dri.c:
> 	Disable interrupt handling after the DRM handler has been removed,
> 	preventing lockups (closes: #1886).
> 
> 	* programs/Xserver/hw/xfree86/drivers/ati/r128_driver.c:
> 	* programs/Xserver/hw/xfree86/drivers/ati/r128_video.c:
> 	Allow pitches with a granularity of 32, rather than 64, because some
> 	clamshell iBooks have 800-byte pitches.  Change Xv allocation
> 	granularity to 8 bytes, rather than 16 bytes, also (closes: #1888).
> 
> 2004-12-04  Alexander Gottwald  <ago at freedesktop dot org>
> 
> 	* doc/man/general/X.man:
>Index: xc/programs/Xserver/Xprint/ps/PsInit.c
>===================================================================
>RCS file: /cvs/xorg/xc/programs/Xserver/Xprint/ps/PsInit.c,v
>retrieving revision 1.6
>diff -u -2 -0 -r1.6 PsInit.c
>--- xc/programs/Xserver/Xprint/ps/PsInit.c	14 Oct 2004 02:20:52 -0000	1.6
>+++ xc/programs/Xserver/Xprint/ps/PsInit.c	5 Dec 2004 04:33:54 -0000
>@@ -245,41 +245,41 @@
>   nv++; nv_8bit++;
> 
>   /* StaticGray, 8bit */
>   visuals[nv].vid             = FakeClientID(0);
>   visuals[nv].class           = StaticGray;
>   visuals[nv].bitsPerRGBValue = 8;
>   visuals[nv].ColormapEntries = 256;
>   visuals[nv].nplanes         = 8;
>   visuals[nv].redMask         = 0x0;
>   visuals[nv].greenMask       = 0x0;
>   visuals[nv].blueMask        = 0x0;
>   visuals[nv].offsetRed       = 0x0;
>   visuals[nv].offsetGreen     = 0x0;
>   visuals[nv].offsetBlue      = 0x0;
>   vids_8bit[nv_8bit] = visuals[nv].vid;
>   nv++; nv_8bit++;
> 
>   /* StaticGray, 1bit */
>   visuals[nv].vid             = FakeClientID(0);
>   visuals[nv].class           = StaticGray;
>-  visuals[nv].bitsPerRGBValue = 8;
>+  visuals[nv].bitsPerRGBValue = 1;
>   visuals[nv].ColormapEntries = 2;
>   visuals[nv].nplanes         = 1;
>   visuals[nv].redMask         = 0x0;
>   visuals[nv].greenMask       = 0x0;
>   visuals[nv].blueMask        = 0x0;
>   visuals[nv].offsetRed       = 0x0;
>   visuals[nv].offsetGreen     = 0x0;
>   visuals[nv].offsetBlue      = 0x0;
>   vids_1bit[nv_1bit] = visuals[nv].vid;
>   nv++; nv_1bit++;
> 
> #ifdef PSOUT_USE_DEEPCOLOR
>   /* TrueColor, 30bit, 10bit per R-,G-,B-gun */
>   visuals[nv].vid             = FakeClientID(0);
>   visuals[nv].class           = TrueColor;
>   visuals[nv].bitsPerRGBValue = 10;
>   visuals[nv].ColormapEntries = 1024;
>   visuals[nv].nplanes         = 30;
>   visuals[nv].redMask         = 0X3FF00000;
>   visuals[nv].greenMask       = 0X000FFC00;

Flags:

roland.mainz: 6.8-branch+

Actions: View | Splinter Review

Attachments on bug 1800: 1474

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.