A new pixman release 0.13.2 is now available
tar.gz:
http://cairographics.org/releases/pixman-0.13.2.tar.gz
http://xorg.freedesktop.org/archive/individual/lib/pixman-0.13.2.tar.gz
tar.bz2:
http://xorg.freedesktop.org/archive/individual/lib/pixman-0.13.2.tar.bz2
Hashes:
Le 25/11/2008 02:09, Peter Hutterer a écrit :
Ajax,
Please pull a few input fixes for server-1.5-branch:
What about this patch from you? We've had it in our branch for a while
and it helped quite a few users.
On Monday 24 November 2008 16:29:12 Tobias Kaminsky wrote:
Hello,
I have 2 TFTs with each 1280x1024.
Normally I work alone on the pc - Xinerama.
But sometimes my girlfriend wants to work on the pc, too. But I do not want
to log out, change KDM and log in again.
So I need something that
Hi,
I have a XO Laptop which is a nice machine machine with a high res display
of 1200x900 pixels. The problem with this is that the laptop isn't powerful
enugh to handle fullscreen applications at this resolution. If only the
display could switch to a lower resolution things would be much better
On Tuesday 25 November 2008 13:11:24 you wrote:
Kārlis Repsons wrote:
One more sad thing: Xephyr doesn't support GLX, which means, most likely
no 3D for it's users... I would like to ask someone better informed here,
if that is going to be addressed in near future?
From an earlier post by
Adam Jackson wrote:
On Sat, 2008-11-22 at 13:07 +0100, Matthieu Herrb wrote:
Matthieu Herrb wrote:
Hi,
using OpenBSD's memory allocator (which has an option to fill free()'d
memory with a specific pattern) I found out that xserver 1.5.3 is
dumping core on exit.
Same problem on git's
On Tue, Nov 25, 2008 at 12:52 PM, [EMAIL PROTECTED] wrote:
On Tue, Nov 25, 2008 at 11:57:17AM +0100, Strider wrote:
The problem with this is that the laptop isn't powerful enugh
to handle fullscreen applications at this resolution.
All those I have tried have worked fine at this
Dear list,
in the past, our company got a siliconmotion driver update to release 1.4.9 of
the siliconmotion driver. But it seems that the features of the 1.4.9 release
have not been given back to the xorg developer community. I have the source
code for this release, and it can be compiled
Gerhart, Bjoern wrote:
Dear list,
Hi,
in the past, our company got a siliconmotion driver update to release
1.4.9 of the siliconmotion driver. But it seems that the features of
the 1.4.9 release have not been given back to the xorg developer
community. I have the source code for this
Keith Packard [EMAIL PROTECTED] writes:
So, we'll see if we can't get a bit of pixman review and perhaps a
pixman release done tomorrow so that the X server beta can head out.
Here are some comments on the matrix code. I didn't review all the
numericals, but nothing jumped out at me either.
-
On Tue, 2008-11-25 at 17:58 +0100, Soeren Sandmann wrote:
Keith Packard [EMAIL PROTECTED] writes:
So, we'll see if we can't get a bit of pixman review and perhaps a
pixman release done tomorrow so that the X server beta can head out.
Here are some comments on the matrix code. I didn't
Keith Packard [EMAIL PROTECTED] writes:
- Pixman's version numbering scheme is similar to cairo's: The git
master version has an odd micro number, released versions have even
micro numbers.
What version would you like?
Before releasing, bump to 0.13.2, after releasing, bump to
On Tue, Nov 25, 2008 at 09:46:38AM +1000, Peter Hutterer wrote:
On Sun, Nov 23, 2008 at 08:46:14PM +0100, Batchty wrote:
Hello, I have a Dell Inspiron 1520 with a Synaptics touchpad. This touchpad
for
a unknown reason loves to send event like these after every finger release
:
Alex Villacís Lasso wrote:
- driver/xf86-video-via generates an error about expected
specifier-qualifier-list before 'uint32_t' when including drm.h. I
skipped this one since my chipset is a radeon.
That's rotted alright - I've pushed a build.sh change to stop building it.
(The replacement,
Well if you let me decide between software rendering on client or
software rendering on server, I would prefer the latter.
It's not that clear cut. At least some of the motivation behind Render is
about moving time-consuming operations into the client, notably font
rasterisation.
There are
That's not 'strong vocabulary' but simply baseless flamebait.
Would it make sence to implement some fallback-optimizations like:
- Copy pictures without drawables (gradients) to a temporary surface,
if the driver supports composition?
- Support solid write-only operations (X11 core drawing) for
Apparently, the current incarnation of EXA is built on the assumption that
everything should be accelerated, and that when it isn't, it's a bug. Hence,
it pays no attention whatsoever to the performance of software rendering.
That's not 'strong vocabulary' but simply baseless flamebait.
Wasn't the reason to do font rasterization primiary to give applications
more control over font rendering?
If memory serves, Keith was trying to find a design to solve both issues
with core fonts -- lack of flexibility and latency. There was an extended
brain-storming session on the old
On Tue, Nov 25, 2008 at 10:10 PM, Soeren Sandmann [EMAIL PROTECTED] wrote:
- When mask is 0, there is no reason to read the source.
- There is no reason to read the destination if the inverse
combined src/mask is 0
Don't compilers take care of that?
The code looks better to me if
On Wed, Nov 19, 2008 at 10:07:59PM +, Magnus Kessler wrote:
With the latest server and synaptics driver from git I can reliably crash
the server by starting
xinput test SynPS2/2 Synaptics Touchpad
and then clicking the any of the physical buttons or tapping the pad to
simulate a
Hi All,
Hi,
Is it possible to use i810 driver in Xorg7.3 without agpgart kernel module
?
I use kernel 2.4.31. And It's OK for XFree86 4.6.
I think it should work with older versions of the i810 driver, as
long the driver recognizes your hardware.
Some months ago I worked on something
There are a number of minor issues w/ I830GetRec:
- pI830 is local, and therefore never gets used
- it only ever returns TRUE (no need to check the result)
- it's only ever called once, so there's not much point in protecting
against multple calls
So, this drops I830GetRec and instead just
There aren't as many issues with I810GetRec, but there's not much point
for its existence, either. Since it's only ever called once, drop it
and simply call xnfcalloc directly. Since xnfcalloc will never fail,
there's no point in checking the result.
Signed-off-by: Andres Salomon [EMAIL
We can be assured that a DCON device has an OLPC panel that's 152x114 mm.
This adds fields to GeodeRec to allow other panels to potentially
override physical width/height fields, and also allows xorg.conf to
override the values.
Signed-off-by: Andres Salomon [EMAIL PROTECTED]
---
src/geode.h
24 matches
Mail list logo
