On Thu, 6 Nov 2003, Boris wrote:
Date: Thu, 6 Nov 2003 10:28:37 -0600
From: Boris [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Content-Type: multipart/alternative;
boundary==_NextPart_000_0005_01C3A450.BD38C8A0
Subject: Upgrade fontconfig in cvs.
It seems the
Alexander Stohr writes:
Hello,
i stumbled across the above mentioned define and
related code in the XFree86 sources (lnx_video.c).
comparing X4.1.0 and X4.3.0 i found that the
condtitnal coding of if (base % size) has
vanished at some point in time and the handling
is now
On Thu, Nov 06, 2003 at 12:27:44PM -0500, David Dawes wrote:
On Thu, Nov 06, 2003 at 10:28:37AM -0600, Boris wrote:
It seems the fontconfig in cvs is very old (1.0.2) and needs to be upgraded to
2.2.0. Reading varios emails and posts, it seems the older fontconfig has problems
with some TrueType
Hi,
I posted this on dri-users and have been suggested to post here...
Everything starts fine with no errors (as you can see from the logs).
The problem I have is that I don't think I have 2D acceleration.
The simple test I do is to just drag a window on the screen... the
redraw is extremely
The latest fontconfig in cvs is old and has
problems. After reading posts in reguard to the fontconfig in cvs, It has
problems with some truetype fonts and fc-cache segmentation faults during
startup on systems. Fontconfig in cvs is 1.0.2 while the latest is 2.2.0. Could
we please update
I'm curious about some of the obscurity in the nv driver. In
particular, almost everywhere in the driver, registers are
addressed numerically, and not by symbolic names. That on it's
own is obscure enough to make things difficult to tell what's
going on, but we know the deal with Nvidia
On Fri, Nov 07, 2003 at 07:48:35PM -0600, Boris wrote:
The latest fontconfig in cvs is old and has problems. After reading posts in reguard
to the fontconfig in cvs, It has problems with some truetype fonts and fc-cache
segmentation faults during startup on systems. Fontconfig in cvs is 1.0.2
On Fri, Nov 07, 2003 at 04:39:43PM -, jassi brar wrote:
Hi all,
I m building kdrive/Xfbdev,Xipaq (XFree86-4.3.99.14) server. I just amaze why its
size is so big(Xfbdev-3.2MB, Xipaq-3.3MB)... when it is supposed to be light-weight.
Does your target platform have shared libraries? I find
On Fri, 7 Nov 2003, Mike A. Harris wrote:
Everywhere
in the driver hex values are given premultiplied by 4 it seems,
and specified as VALUE/4.
The register pointers are dword pointers. The register offsets
are byte offsets. They are written as VALUE/4 so that I can grep
for VALUE.
try removing the videoram line from your config. the driver will
detect videoram fine.
Alex
--- Salvio Sergi [EMAIL PROTECTED] wrote:
Hi,
I posted this on dri-users and have been suggested to post here...
Everything starts fine with no errors (as you can see from the logs).
The
10 matches
Mail list logo
