Matthieu Herrb pronounced:
> I need those 2 fixes to run the vesa driver with xserver 1.7. ok?
>
> commit 9829de7a1b2a9734d20a239d3ed84a73ddaf70f1
> Author: Matthieu Herrb
> Date: Mon Sep 28 23:00:27 2009 +0200
>
> fix vesa for xserver 1.7 branch.
>
> - convert slowbcopy_frombus()
On Mon, Sep 28, 2009 at 9:19 AM, Alan Coopersmith
wrote:
> Mikhail Gusarov wrote:
>> Twas brillig at 04:39:20 26.09.2009 UTC+07 when dotted...@dottedmag.net did
>> gyre and gimble:
>>
>> MG> This fixes configuration in cross-compilation mode:
>>
>> Whoops. This was a patch for libxt, sorry for n
Checking just for root is insufficient since that does not guarantee write/read
permissions in XKM_OUTPUT_DIR (for example with sandbox).
Check if we can write a file, as well as read it later. Otherwise, invoke the
fallback to /tmp
Signed-off-by: Nirbheek Chauhan
---
xkb/ddxLoad.c |5 ++---
Removing DGA ended up breaking any drivers calling into the old
xf86DiDGAInit function as it tried to see if DGA was already enabled
and ended up crashing if the VT wasn't completely initialized. Oops.
Also, if the driver initializes DGA itself, have the DiDGA
initialization overwrite that informa
On Mon, 28 Sep 2009 20:59:52 +0200, Kim Woelders wrote:
Ok, here is a "good" one, I hope. After starting and killing attached
program twice I get:
Program received signal SIGSEGV, Segmentation fault.
0x08070cc4 in LoadGlyphs (data=,
item_size=, nchars=,
pfont=0xc1a5288,
client=0xc15
If libudev is found, we use that for hotplug and disable the hal and
dbus backends.
We look for event devices with an "x11_driver" property. XKB
configuration happens using xkb.{rules,model,layout,variant,options}
properties, and arbitrary options can be set with "x11_options.foo"
(this is similar
This patch fixes two bugs:
size is calculated as glyph height * padded_width. If the client submits
garbage, this may get above INT_MAX, resulting in a negative size if size is
unsigned. The sanity checks don't trigger for negative sizes and the server
goes and writes into random memory locations.
Excerpts from Kim Woelders's message of Tue Sep 29 11:58:36 -0700 2009:
>From 2da355de4f0c0a9a4ca52b1253afed9486481411 Mon Sep 17 00:00:00 2001
From: Kim Woelders
Date: Tue, 29 Sep 2009 20:31:45 +0200
Subject: [PATCH] dix: Fix potential memory corruption in doListFontsWithInfo.
Signed-off-by: K
On Tue, Sep 29, 2009 at 11:49:09AM +1000, Dave Airlie wrote:
> The previous code was copied and in both cases incorrectly fixed
> up the colormaps after resizing the visuals, this patch consolidates
> the visual resize + colormaps fixups in one place. This version
> also consolidates the vid alloca
Good news everyone!
It is with great pleasure that I can announce a new driver in our happy
family: xf86-input-wacom.
xf86-input-wacom is a fork of the linuxwacom driver and the credit goes to
Ping Cheng for forking it, cleaning out pre-server-1.6 cruft and adding the
initial device property su
On Wed, Sep 30, 2009 at 09:06:42 +1000, Peter Hutterer wrote:
> On Tue, Sep 29, 2009 at 11:49:09AM +1000, Dave Airlie wrote:
> > diff --git a/include/colormap.h b/include/colormap.h
> > index a3467c9..eb0f670 100644
> > --- a/include/colormap.h
> > +++ b/include/colormap.h
> > @@ -179,4 +179,9 @@
Excerpts from Peter Hutterer's message of Tue Sep 29 15:20:33 -0700 2009:
> Tested with Xvfb, Xephyr and Xorg.
It looks to me like miGlyphs will crash when it sees 0 sized glyphs.
Also, I'd also suggest memset'ing the Picture pointers after the
glyph.
-keith
signature.asc
Description: PGP sig
On Tue, Sep 29, 2009 at 04:49:57PM -0700, Ian Romanick wrote:
> glx/glxcmds.c| 11 ---
> glx/glxdri2.c| 14 ++
> glx/glxext.c |8 +++-
> glx/glxscreens.c |7 ---
> glx/glxscreens.h |2 ++
> glx/glxserver.h |3 +++
> 6 files changed, 38 i
On Tue, Sep 29, 2009 at 01:44:24PM -0700, Keith Packard wrote:
> Excerpts from Kim Woelders's message of Tue Sep 29 11:58:36 -0700 2009:
>
> >From 2da355de4f0c0a9a4ca52b1253afed9486481411 Mon Sep 17 00:00:00 2001
> From: Kim Woelders
> Date: Tue, 29 Sep 2009 20:31:45 +0200
> Subject: [PATCH] dix:
Ugh, GPL, So we can't have this for OpenSolaris or any of the *BSD's then?
What a shame/wast of IP..
2009/9/30 Peter Hutterer :
> Good news everyone!
>
> It is with great pleasure that I can announce a new driver in our happy
> family: xf86-input-wacom.
>
> xf86-input-wacom is a fork of the linuxw
From: Dave Airlie
I think this is what the original author wanted.
Signed-off-by: Dave Airlie
---
glx/glxext.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/glx/glxext.c b/glx/glxext.c
index 2de8b84..0737420 100644
--- a/glx/glxext.c
+++ b/glx/glxext.c
@@ -364,14
On Wed, Sep 30, 2009 at 02:32:56AM +0100, Edward O'Callaghan wrote:
> Ugh, GPL, So we can't have this for OpenSolaris or any of the *BSD's then?
> What a shame/wast of IP..
Does the BSDs not ship any GPL software? Last I looked, that was not
true.
thanks,
greg k-h
__
On Wed, Sep 30, 2009 at 02:32:56AM +0100, Edward O'Callaghan wrote:
> Ugh, GPL, So we can't have this for OpenSolaris or any of the *BSD's then?
> What a shame/wast of IP..
linuxwacom is already GPL, unsurprisingly the fork is GPL too.
Cheers,
Peter
_
The X server cannot deal with devices that have both relative and absolute
axes. Evdev tries to guess wich axes to ignore given the device type and
disables absolute axes for mice and relative axes for tablets, touchscreens
and touchpad. This guess is sometimes wrong and causes exitus felis
domesti
Well, we may have a surprise for you someday on OpenSolaris. As far as I
know, linuxwacom has been running on FreeBSD for a while (
http://www.freshports.org/x11-drivers/input-wacom). Maybe you can help us
deploy it on other *BSDs. Let me know if you don't have a Wacom tablet to
play with.
Ping
This patch fixes two bugs:
size is calculated as glyph height * padded_width. If the client submits
garbage, this may get above INT_MAX, resulting in a negative size if size is
unsigned. The sanity checks don't trigger for negative sizes and the server
goes and writes into random memory locations.
On Tue, Sep 29, 2009 at 11:34:24AM -0700, Keith Packard wrote:
> Removing DGA ended up breaking any drivers calling into the old
> xf86DiDGAInit function as it tried to see if DGA was already enabled
> and ended up crashing if the VT wasn't completely initialized. Oops.
>
> Also, if the driver ini
Excerpts from Peter Hutterer's message of Tue Sep 29 22:15:21 -0700 2009:
> miGlyphs seems to deal with 0-width glyphs just fine
I guess I don't understand how this can be --
ProcRenderCompositeGlyphs passes all of the glyphs to CompositeGlyphs
which just calls down to the Glyphs function. If tha
On Tue, Sep 29, 2009 at 10:29:31PM -0700, Keith Packard wrote:
> Excerpts from Peter Hutterer's message of Tue Sep 29 22:15:21 -0700 2009:
>
> > miGlyphs seems to deal with 0-width glyphs just fine
>
> I guess I don't understand how this can be --
> ProcRenderCompositeGlyphs passes all of the gly
Hi Julien,
Le mardi 29 septembre 2009 à 23:54 +0200, Julien Cristau a écrit :
> If libudev is found, we use that for hotplug and disable the hal and
> dbus backends.
Why disable dbus? I see udev being in conflict with HAL, but not with
the dbus code. Not that it matters much, I don't think any to
25 matches
Mail list logo
