Re: s3savage drivers and Xv

2002-08-28 Thread Chris Halls
On Sat, Aug 17, 2002 at 10:30:51PM -0500, Branden Robinson wrote: > On Mon, Aug 12, 2002 at 08:39:11AM -0700, Bill Moseley wrote: > > Is it possible to get that updated driver into the debian release of > > xfree86, or is that something that has to be done upstream? > > If someone preps a patch t

Re: s3savage drivers and Xv

2002-08-28 Thread Chris Halls
On Wed, Aug 28, 2002 at 10:04:09AM +0200, Chris Halls wrote: > Here's a patch which replaces the files in Ahem, I was so busy thinking about the docs that I forgot the patch /me blushes Chris This patch generated from http://www.probo.com/timr/savage40.html, version 1.1.23t diff -Nurd xc/progr

Re: a small C program to test xdm's /dev/mem reading on your architecture

2002-08-28 Thread Michael Schmitz
> I and the other folks at the X Strike Force need to know the following > things: > > 1) whether or not this program works when you run it without arguments Runs without any problem ("read of /dev/mem returned 1") on PPC Powerbook 1999 "Lombard" (ran it multiple times, before and after sleep mode

Re: i810 in X 4.1/2

2002-08-28 Thread Jim McCloskey
Branden Robinson <[EMAIL PROTECTED]> wrote: |> Well, that would explain it. Some people are very sensitive to refresh |> rates of 60 Hertz, and this can be exacerbated by fluorescent lights in |> North America which cycle at the frequency of wall current, which is |> also 60 Hz. I've also seen

missing header files in source package xfree86 4.2.0-0pre1v3

2002-08-28 Thread Yves Salathe
Hi Yesterday I compiled the xfree86 source package on Debian GNU/Linux 2.4 stable i386. Unfortunatly I received the following error messages from gcc: In file included from GLwDrawA.c:43: GLwDrawAP.h:53: X11/IntrinsicP.h: No such file or directory GLwDrawA.c:44: X11/IntrinsicP.h: No s

Re: gcc2.95, libttf2, xfree86, and Alpha

2002-08-28 Thread Doug Larrick
On Sat, 17 Aug 2002 22:28:50 -0500, Branden Robinson wrote: On Tue, Aug 13, 2002 at 04:53:34PM +0200, Juliusz Chroboczek wrote: > Branden, I suggest you take this approach. Unfortunately, this will > significantly slow down the speed of the rasteriser. > > I guess something like the following (u