___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
On Wednesday 05 of November 2003 23:03, Gerhard W. Gruber wrote:
> On Wed, 5 Nov 2003 18:14:03 +0100, Rafa Rzepecki
>
> <[EMAIL PROTECTED]> wrote:
> >I hope that clears it up.
>
> Yes. Thanks. I hoped that the XFree part would have been open
> source, but of course that is a small hope. :)
Why wo
On Wed, 5 Nov 2003 18:14:03 +0100, Rafa³ Rzepecki
<[EMAIL PROTECTED]> wrote:
>I hope that clears it up.
Yes. Thanks. I hoped that the XFree part would have been open source, but of
course that is a small hope. :)
--
Gerhard Gruber
Für jedes menschliche Problem gibt es immer eine einfache Lösun
On Wed, Nov 05, 2003 at 11:45:42AM -0800, Torrey Lyons wrote:
>It appears that the Freetype library shipped with XFree86 4.2 is
>binary incompatible with what shipped with 4.3 and the top of tree.
>The problem is a bunch of renamed symbols, as described in
>xc/extras/freetype2/ChangeLog:
>
>2002
It appears that the Freetype library shipped with XFree86 4.2 is
binary incompatible with what shipped with 4.3 and the top of tree.
The problem is a bunch of renamed symbols, as described in
xc/extras/freetype2/ChangeLog:
2002-02-24 David Turner <[EMAIL PROTECTED]>
* Renaming stream
On Tue, 4 Nov 2003, Pavel Troller wrote:
> I'm hanging on CVS, making regular updates and runnig the latest versions of
> the code, at least on my experimental machines. I can see many improvements in
> comparison with the latest official release. But since about three weeks,
> a problem appeare
On Wednesday 05 of November 2003 00:30, Gerhard W. Gruber wrote:
> The module of XFree86 is nv for nVidia. The proprietary drivers are
> called nvidia. Apparently nVidia open sourced only that small part
> needed on the side of XFree86 and closed source on the kernel part.
AFAIK, NVidia's driver c
Am now making some progress on the mangled graphics:
When i have acceleration turned on, glyph drawing is a complete mess. it
looks like the bits are being expanded backwards and characters are being
read from the wrong place. I've gone through CPUToScreenColorExpandFill with
a fine tooth comb, but
