Re: Merging page flipping & triple buffering for i915tex driver
On Tue, 2007-03-06 at 10:52 -0800, Eric Anholt wrote: > On Tue, 2007-03-06 at 11:07 +0100, Michel Dänzer wrote: > > > > I developed and tested this on i945 hardware. I've had reports of it > > working on i915 as well but would be interested in hearing whether it > > works on i830 and above. Still haven't seen any reports about this unfortunately. I guess this will be more likely to get tested with the branches merged. :) The new functionality is disabled by default anyway. > > The only significant outstanding issue I'm aware of is that moving a > > page-flipped 3D window from being visible on pipe A only to being > > visible on pipes A+B can result in a lockup if the flips on pipe B are > > emitted 'too quickly'. I'm currently avoiding this by not syncing the > > pages between pipes immediately in that situation, so it only seems to > > happen with insane framerates such as glxgears', but this could probably > > cause issues of its own with apps that render to the front buffer. It > > doesn't seem to happen when moving from pipe B to pipes A+B, and the > > command stream always waits for previous asynchronous flips to complete > > before emitting a new flip, so I'm not sure what's up. Any ideas would > > be appreciated, especially from the Intel folks. > > > > Possibly related to this, it's been reported that there can be issues > > with outputs that aren't handled quite correctly by the modesetting > > driver (yet), e.g. LVDS on desktop boards. I should have nailed these hopefully. Big thanks to Todd Merrill for live testing feedback on IRC. > > If you have issues with page flipping and xrandr 1.2 shows outputs that > > shouldn't be there, try disabling them. > > Even better, file a bug with Xorg.0.log and the output of scanpci from > libpciaccess, and we can blacklist the LVDS on your board hopefully. Good point. > > If there are no objections, I'd like to merge these branches to the > > respective master branches by the end of this week. Of course, if the > > issues above can't be solved before the merge, I'll document them in the > > intel.4 manpage. There's nothing new to document, and I'm going to merge the branches now. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 7767] No hardware rendering for "SuperSavage/IXC 64" and "Xorg 7.2 RC3"
http://bugzilla.kernel.org/show_bug.cgi?id=7767 --- Additional Comments From [EMAIL PROTECTED] 2007-03-09 12:53 --- Reply-To: [EMAIL PROTECTED] I know what the problem is here. And bugzilla #5714 will cure it. So I'm getting inclined to pull the frontbuffer-removal branch into master and fix up the drivers on the fly. How does this sound to others. Alan. On Sat, 2007-02-24 at 15:00 -0800, [EMAIL PROTECTED] wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=7767 > > > > > > --- Additional Comments From [EMAIL PROTECTED] 2007-02-24 15:00 --- > did you test it though? > > As I said further up this bug, there are no "functional" difference between > the > savage in the drm tree and the one in the kernel tree, they are just either > whitespace or a difference caused by the device binding methods used... so > what > I did was bring over a bunch of drm core code that could affect the area you > are > seeing the problem in.. > > --- You are receiving this mail because: --- > You are the assignee for the bug, or are watching the assignee. > > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > -- > ___ > Dri-devel mailing list > Dri-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dri-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 10234] Renamed the unkXXX variables in R300 command buffer initialization.
http://bugs.freedesktop.org/show_bug.cgi?id=10234 --- Comment #1 from [EMAIL PROTECTED] 2007-03-09 10:47 PST --- Created an attachment (id=9056) --> (http://bugs.freedesktop.org/attachment.cgi?id=9056&action=view) Proposed patch -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 10234] New: Renamed the unkXXX variables in R300 command buffer initialization.
http://bugs.freedesktop.org/show_bug.cgi?id=10234 Summary: Renamed the unkXXX variables in R300 command buffer initialization. Product: Mesa Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: [EMAIL PROTECTED] I've made a patch to rename some of the unkXXX veriables in the command buffer initialization code to more descriptive names, based on the registers they use. There are still a few unknown variables left, but this is a start. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 10109] Invalid reads from intersect_rect in radeon_state.c of r300 driver.
http://bugs.freedesktop.org/show_bug.cgi?id=10109 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #2 from [EMAIL PROTECTED] 2007-03-09 05:51 PST --- Fixed by commit http://gitweb.freedesktop.org/?p=mesa/mesa.git;a=commit;h=4d9901a1cab8e0d55b1b2309cf3ffec235e53149 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]
On Fri, 2007-03-09 at 13:49 +0200, Panagiotis Papadakos wrote: > Yep, I think it is OK! Pushed, thanks. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]
Yep, I think it is OK! On Friday 09 March 2007 10:46, Michel Dänzer wrote: > On Thu, 2007-03-08 at 19:07 +0200, Panagiotis Papadakos wrote: > > On Thursday 08 March 2007 17:05, Michel Dänzer wrote: > > > Any idea what's going on? The only situation where radeonSetCliprects > > > doesn't get called from radeonMakeCurrent is if neither the drawable > > > nor its stamp has changed... > > > > We have to call radeonSetCliprects(radeon), before > > r300UpdateViewportOffset(radeon->glCtx). > > Ah right, like this? -- Papadakos Panagiotis - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Invalid reads from intersect_rect in radeon_state.c of r300 driver. [PATCH included]
On Thu, 2007-03-08 at 19:07 +0200, Panagiotis Papadakos wrote: > On Thursday 08 March 2007 17:05, Michel Dänzer wrote: > > > > Any idea what's going on? The only situation where radeonSetCliprects > > doesn't get called from radeonMakeCurrent is if neither the drawable nor > > its stamp has changed... > > We have to call radeonSetCliprects(radeon), before > r300UpdateViewportOffset(radeon->glCtx). Ah right, like this? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer 0001-r300-Also-update-window-state-when-it-s-already-bou.patch Description: application/mbox - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
