Re: XI2 pull warning
On Sat, May 30, 2009 at 9:29 AM, John Tapsell wrote: > 2009/5/29 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. > > Has anyone from wine had a look at the patch? Might it be good to get > someone from there to sign off on this, since they need the XI2 stuff > to have fairly specific behaviour? > > John Back in April Wine Weekly News mentioned Paul Hampson is working with XInput2: http://www.winehq.org/wwn/357#XInput 2 Spec http://www.winehq.org/pipermail/wine-devel/2009-April/074957.html Cheers, -Matt Helsley ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Is there the possibility to support EXA for legacy S3 chips?
Michel Dänzer writes: >> I think that it may be bug somewhere in EXA or driver bacause >> server's log is full of error messages. >> >> EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while >> it should have been (nil). > This may indeed be a bug, Maarten? Might be interesting to see gdb > backtraces for when these trigger. Specifying "EXAOptimizeMigration" "off" solves the problem, but sometimes two or three such messages appear in the log even with this option. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
Sorry, guys. :) But thanks again for the advice. It is a real pisser to comtemplate 1.5k on the scrapheap. Don't get me started as to why I'm using Linux on a nice mac in the first place ... gr. Robby On Thu, Jun 4, 2009 at 1:37 PM, David Gerard wrote: > 2009/6/4 Robby Findler : > >> That did it!! > > > So how many others reading this thread were just envious of his two > huge really really nice displays? :-) > > > - d. > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
2009/6/4 Robby Findler : > That did it!! So how many others reading this thread were just envious of his two huge really really nice displays? :-) - d. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Is there the possibility to support EXA for legacy S3 chips?
2009/6/4 Michel Dänzer : > On Thu, 2009-05-28 at 15:07 +0400, Evgeny M. Zubok wrote: >> 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 >> ugly as before. I think that it may be bug somewhere in EXA or driver >> bacause server's log is full of error messages. >> >> ... >> >> EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while it >> should have been (nil). > > This may indeed be a bug, Maarten? Might be interesting to see gdb > backtraces for when these trigger. I'm curious as to what triggers this. Can't think of anything from the top of my head. > > >> However the main problem with this method is that memory manager doesn't >> effectively use the offscreen in this case. > > Indeed, I'm afraid EXA just doesn't offer any advantages over XAA for > such limited hardware. > > > -- > Earthling Michel Dänzer | http://www.vmware.com > Libre software enthusiast | Debian, X and DRI developer > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Is there the possibility to support EXA for legacy S3 chips?
On Thu, Jun 4, 2009 at 11:54 AM, Evgeny M. Zubok wrote: > Michel Dänzer writes: > >>> EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while >>> it should have been (nil). >> >> This may indeed be a bug, Maarten? Might be interesting to see gdb >> backtraces for when these trigger. > > Is the https://bugs.freedesktop.org/show_bug.cgi?id=20212 relevant? > > >>> However the main problem with this method is that memory manager >>> doesn't effectively use the offscreen in this case. >> >> Indeed, I'm afraid EXA just doesn't offer any advantages over XAA for >> such limited hardware. > > I have the same thoughts now. In addition I discovered that S3 couldn't > copy pixmaps with different colour depth from offscreen. For example, > when using 16 bpp framebuffer. Some source pixmaps have 16 bpp, and > others have 32 bpp. This results to incorrect 32 bpp pixmaps copying > into frambuffer. So on S3 the EXA works fine only with 32 bpp fb but not > with 16 bpp fb. Other hardware with EXA support have not any problems > with different pixmap depths because their depth may be specified for > graphic processor. Also my tests showed that drawing speed with EXA on > very slow PC was the same as with shadow framebuffer (and less than > XAA). Currently I think that EXA support does not make sense for the > S3. Only the boards with 4/8 Mb video RAM may be the exception and only > for depth 24 / 32 bpp fb. EXA copy shouldn't ask for blits across color depths (need composite for that), however, it does store buffers of different color depths in offscreen memory, so you'd need to be to adjust the depth of the blitter on the fly. Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Is there the possibility to support EXA for legacy S3 chips?
Michel Dänzer writes: >> EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while >> it should have been (nil). > > This may indeed be a bug, Maarten? Might be interesting to see gdb > backtraces for when these trigger. Is the https://bugs.freedesktop.org/show_bug.cgi?id=20212 relevant? >> However the main problem with this method is that memory manager >> doesn't effectively use the offscreen in this case. > > Indeed, I'm afraid EXA just doesn't offer any advantages over XAA for > such limited hardware. I have the same thoughts now. In addition I discovered that S3 couldn't copy pixmaps with different colour depth from offscreen. For example, when using 16 bpp framebuffer. Some source pixmaps have 16 bpp, and others have 32 bpp. This results to incorrect 32 bpp pixmaps copying into frambuffer. So on S3 the EXA works fine only with 32 bpp fb but not with 16 bpp fb. Other hardware with EXA support have not any problems with different pixmap depths because their depth may be specified for graphic processor. Also my tests showed that drawing speed with EXA on very slow PC was the same as with shadow framebuffer (and less than XAA). Currently I think that EXA support does not make sense for the S3. Only the boards with 4/8 Mb video RAM may be the exception and only for depth 24 / 32 bpp fb. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
That did it!! Thanks, Robby On Thu, Jun 4, 2009 at 10:10 AM, Maarten Maathuis wrote: > xf86-video-nv which i guess you're using doesn't unconditionally > support dual link dvi. Some bios'es don't init it appearantly. > > There is an option to force it, but you could end up with a blank screen. > > Option "AllowDualLinkModes" > > Maarten. > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
xf86-video-nv which i guess you're using doesn't unconditionally support dual link dvi. Some bios'es don't init it appearantly. There is an option to force it, but you could end up with a blank screen. Option "AllowDualLinkModes" Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
On Thu, Jun 4, 2009 at 9:41 AM, Maarten Maathuis wrote: > You can only addmode after newmode. Right. I did them in the correct order (well, once I realized my mistake) to get the error message from my last message. > I would expect a monitor to have it's native resolution in edid. I'm not sure if this is helpful, but I put what appears to be the relevant output from xrandr --verbose below (after I got rid of my manually added 2560x1600 mode)...? > Maybe > you only have a single link dvi (which lacks the bandwith for your > native resolution)? On Thu, Jun 4, 2009 at 9:40 AM, Alex Deucher wrote: > What card are you using? 2560x1600 requires dual-link DVI which not > all cards support. I believe it is supported by the card because it works when I boot under mac os x. Here is the info from the mac os x side (I'm not sure how to get this info from X): NVIDIA GeForce 8800 GT: Chipset Model:NVIDIA GeForce 8800 GT Type: Display Bus: PCIe Slot: Slot-1 PCIe Lane Width: x16 VRAM (Total): 512 MB Vendor: NVIDIA (0x10de) Device ID:0x0602 Revision ID: 0x00a2 ROM Revision: 3233 Displays: Cinema HD Display: Resolution: 1920 x 1200 Depth:32-Bit Color Core Image: Hardware Accelerated Mirror: Off Online: Yes Quartz Extreme: Supported Rotation: Supported Cinema HD: Resolution: 2560 x 1600 Depth:32-Bit Color Core Image: Hardware Accelerated Main Display: Yes Mirror: Off Online: Yes Quartz Extreme: Supported Rotation: Supported Thanks, Robby --- DVI1 connected 1280x800+1920+0 (0x41) normal (normal) 641mm x 401mm Identifier: 0x3e Timestamp: 22656 Subpixel: unknown Clones: CRTC: 1 CRTCs: 0 1 Panning:0x0+0+0 Tracking: 0x0+0+0 Border: 0/0/0/0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID_DATA: 000006102192fee80102 2f1201038040287828fe85a3574a9c25 1350540001010101010101010101 010101010101bc1b00a0502017303020 36008191211ab06800a0a0402e60 302036008191211a00ff0043 59383437304c43584d500afc 0043696e656d612048440a000142 scale: aspect dither: 0 (0x) range: (0,1) 1280x800 (0x41) 71.0MHz +HSync -VSync *current h: width 1280 start 1328 end 1360 total 1440 skew0 clock 49.3KHz v: height 800 start 803 end 809 total 823 clock 59.9Hz ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
You can only addmode after newmode. I would expect a monitor to have it's native resolution in edid. Maybe you only have a single link dvi (which lacks the bandwith for your native resolution)? Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
On Thu, Jun 4, 2009 at 10:33 AM, Robby Findler wrote: > Ah! Well, I realized I missed something reading the man pages about > xrandr and what I need to do is this, but it also fails: > > $ xrandr --addmode DVI1 2560x1600 > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 149 (RANDR) > Minor opcode of failed request: 18 () > Serial number of failed request: 27 > Current serial number in output stream: 28 > > Any hints would be greatly appreciated. What card are you using? 2560x1600 requires dual-link DVI which not all cards support. Alex ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: help configuring a 30" apple cinema display
Ah! Well, I realized I missed something reading the man pages about xrandr and what I need to do is this, but it also fails: $ xrandr --addmode DVI1 2560x1600 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 149 (RANDR) Minor opcode of failed request: 18 () Serial number of failed request: 27 Current serial number in output stream: 28 Any hints would be greatly appreciated. tia, Robby On Tue, Jun 2, 2009 at 3:39 PM, Robby Findler wrote: > Hi all: I'm having some trouble getting my apple cinema displays to > run properly. I have two of them, a 23" one (DVI0) and a 30" one > (DVI1). here's the output from xrandr: > > > Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 4480 x 1600 > VGA1 disconnected > DVI0 connected 1920x1200+0+0 495mm x 310mm > 1920x1200 59.9*+ 60.0 > VGA2 disconnected > DVI1 connected 1280x800+1920+400 641mm x 401mm > 1280x800 59.9* > > > which I think means I need to add a mode to get the DVI1 one to > 2560x1600. So I did this: > > xrandr --output DVI1 --newmode 2560x1600 348.50 2560 2760 3032 3504 > 1600 1603 1609 1658 -hsync +vsync > > which seemed to succed, but then I get this: > > xrandr --output DVI1 --mode 2560x1600 > xrandr: cannot find mode 2560x1600 > > Any ideas what I'm doing wrong? > > Thanks, > Robby > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Is there the possibility to support EXA for legacy S3 chips?
On Thu, 2009-05-28 at 15:07 +0400, Evgeny M. Zubok wrote: > 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 > ugly as before. I think that it may be bug somewhere in EXA or driver > bacause server's log is full of error messages. > > ... > > EXA bug: Calling FinishAccess on pixmap 0x9278d68 with index 1 while it > should have been (nil). This may indeed be a bug, Maarten? Might be interesting to see gdb backtraces for when these trigger. > However the main problem with this method is that memory manager doesn't > effectively use the offscreen in this case. Indeed, I'm afraid EXA just doesn't offer any advantages over XAA for such limited hardware. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
