RANDR V1.3 RRChangeOutputProperty() not working ?

2009-05-28 Thread Graeme Gill
Hi, A user is reporting to me that my code that attempts to set a property in an output using XRANDR is failing on their system. The code seems to work fine on other systems running (probably different versions) of XRANDR. I'm trying to figure out if it's: 1) A bug in XRANDR V1.3

Re: Is there the possibility to support EXA for legacy S3 chips?

2009-05-28 Thread Evgeny M. Zubok
> Looks like no dice for EXA. Fixed pitches, no offsets... ouch. Yes, I think the same. 'Solid' and 'Copy' is the only functionality that would be possible with this hardware. There is no reason to waste a time further. BTW, both 'Solid' and 'Copy' work fine only when operate on framebuffer beca

Re: Is there the possibility to support EXA for legacy S3 chips?

2009-05-28 Thread Evgeny M. Zubok
Ville Syrjälä writes: > Why wouldn't it work if you just allocate everything using the same > pitch? Or does the allocator make some assumptions about the pitches > the hardware can handle? The allocator make the assumption that hardware is able to copy offscreen pixmaps with any pitch and with

Re: Is there the possibility to support EXA for legacy S3 chips?

2009-05-28 Thread Ville Syrjälä
On Thu, May 28, 2009 at 12:00:26PM +0400, Evgeny M. Zubok wrote: > Ville Syrjälä writes: > > > Why wouldn't it work if you just allocate everything using the same > > pitch? Or does the allocator make some assumptions about the pitches > > the hardware can handle? > > The allocator make the assu

Re: Is there the possibility to support EXA for legacy S3 chips?

2009-05-28 Thread Evgeny M. Zubok
Ville Syrjälä writes: > Just set the alignment to your fixed pitch value and it should work, > shouldn't it? Great! Good idea! I have tried to set up pitch align pEXA->pixmapPitchAlign = pScrn->displayWidth * pS3->s3Bpp; and got almost normal working screen (with artefacts though) but not so

Re: Xorg resolution with VGA Switch

2009-05-28 Thread Barry Scott
Aaron Plattner wrote: > On Wed, May 27, 2009 at 07:49:18AM -0700, Aurélien PROVIN wrote: > >> Hi, >> >> I bought a VGA switch to switch some devices on one monitor. >> But resolution of my X session is limited to 1024x768 instead of 1920x1200. >> If I hotplug the switch when the X session is sta

upcoming xi2 and current XTest implementation

2009-05-28 Thread Christian Beier
Hi there, with the merge of xi2 coming next week, I wonder what the status of XTest with xi2 is. Right now, XTest still pretty much looks like XI 1.x, with Device*'s instead of devive ids (http://cgit.freedesktop.org/xorg/proto/xextproto/tree/XTest.h). Looking at the upcoming libXi in Peters repo,

Re: upcoming xi2 and current XTest implementation

2009-05-28 Thread Simon Thum
Christian Beier wrote: > Hi there, > with the merge of xi2 coming next week, I wonder what the status of > XTest with xi2 is. Right now, XTest still pretty much looks like XI > 1.x, with Device*'s instead of devive ids > (http://cgit.freedesktop.org/xorg/proto/xextproto/tree/XTest.h). > Looking at

Re: upcoming xi2 and current XTest implementation

2009-05-28 Thread Simon Thum
Ooops, forget hat mail; I didn't switch branches. Simon Thum wrote: > Christian Beier wrote: >> Hi there, >> with the merge of xi2 coming next week, I wonder what the status of >> XTest with xi2 is. Right now, XTest still pretty much looks like XI >> 1.x, with Device*'s instead of devive ids >> (

Re: upcoming xi2 and current XTest implementation

2009-05-28 Thread Alan Coopersmith
Simon Thum wrote: > The fact that xextproto contains a library header seems somewhat odd to > me, I guess it's historical. In the monolith, many of the extensions mixed wire protocol, client library, and server internal definitions in the same header files, and we didn't untangle the mess when m

Re: XI2 pull warning

2009-05-28 Thread Thomas Jaeger
Hi Peter, Sorry for replying off-list first. Thanks for the work you've put into this. I haven't spent a lot of time testing the new code, but here are my first impressions. You're probably aware of most of the issues below already, but I'll mention them just in case. * The biggest issue for

Re: [PATCH 1/2] kdrive: add protocol mouse option

2009-05-28 Thread Olivier Blin
Peter Hutterer writes: > On Wed, May 27, 2009 at 07:04:16PM +0200, Olivier Blin wrote: >> Peter Hutterer writes: >> >> > On Tue, May 26, 2009 at 03:30:08PM +0200, Olivier Blin wrote: >> >> kdrive probes a lot of PS/2 protocols for the mouse device, which >> >> makes the mouse unusable for some

[PATCH 1/2] kdrive: add protocol mouse option

2009-05-28 Thread Olivier Blin
kdrive probes a lot of PS/2 protocols for the mouse device, which makes the mouse unusable for some seconds after X startup. This new "protocol" option allows forcing the mouse protocol. It can be used this way: Xfbdev -mouse mouse,,protocol=ps/2 -keybd keyboard Signed-off-by: Olivier Blin --- h

Re: Xorg resolution with VGA Switch

2009-05-28 Thread Aurélien PROVIN
Le mercredi 27 mai 2009 à 08:30 -0700, Aaron Plattner a écrit : > On Wed, May 27, 2009 at 07:49:18AM -0700, Aurélien PROVIN wrote: > > Hi, > > > > I bought a VGA switch to switch some devices on one monitor. > > But resolution of my X session is limited to 1024x768 instead of 1920x1200. > > If I h

[PATCH] Make RANDR 'set' timestamps follow client specified time. Bug 21987.

2009-05-28 Thread Keith Packard
The lastSetTime value which indicates when the configuration within the server was last changed was not getting set in the appropriate RandR requests. Signed-off-by: Keith Packard --- randr/rrcrtc.c |5 - randr/rrscreen.c |4 +++- 2 files changed, 7 insertions(+), 2 deletions(-) d

Re: upcoming xi2 and current XTest implementation

2009-05-28 Thread Peter Hutterer
On Thu, May 28, 2009 at 03:27:17PM +0200, Christian Beier wrote: > > Hi there, > with the merge of xi2 coming next week, I wonder what the status of > XTest with xi2 is. Right now, XTest still pretty much looks like XI > 1.x, with Device*'s instead of devive ids > (http://cgit.freedesktop.org/xorg/

Re: [PATCH 1/2] kdrive: add protocol mouse option

2009-05-28 Thread Peter Hutterer
On Thu, May 28, 2009 at 08:57:36PM +0200, Olivier Blin wrote: > kdrive probes a lot of PS/2 protocols for the mouse device, which > makes the mouse unusable for some seconds after X startup. > This new "protocol" option allows forcing the mouse protocol. > It can be used this way: > Xfbdev -mouse m

Re: XI2 pull warning

2009-05-28 Thread Peter Hutterer
On Thu, May 28, 2009 at 02:54:22PM -0400, Thomas Jaeger wrote: > Thanks for the work you've put into this. I haven't spent a lot of time > testing the new code, but here are my first impressions. You're > probably aware of most of the issues below already, but I'll mention > them just in case. >