My bug is six months old and I don't even know if anyone's read it
At this point I am very annoyed at the fact that the composite extension still does not work on my laptop. I am still unable to use Beryl or Compiz. I submitted this bug over 6 months ago and as far as I can tell it's been completely ignored. I can't even have transparency never mind Beryl. -- Joseph Mulloy [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8732] GMA950, Composite breaks OpenGL
http://bugs.freedesktop.org/show_bug.cgi?id=8732 [EMAIL PROTECTED] changed: What|Removed |Added Component|General |Drivers/DRI/i915 Product|DRI |Mesa -- 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. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 8732] Composite breaks OpenGL
http://bugs.freedesktop.org/show_bug.cgi?id=8732 [EMAIL PROTECTED] changed: What|Removed |Added Component|Drivers/DRI/i915|General Product|Mesa|DRI Summary|GMA950, Composite breaks|Composite breaks OpenGL |OpenGL | --- Comment #4 from [EMAIL PROTECTED] 2007-05-13 23:42 PST --- Fixing this is far from trivial, see http://dri.freedesktop.org/wiki/DirectRenderingToRedirectedWindows for a sketch of the road ahead. -- 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. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: My bug is six months old and I don't even know if anyone's read it
On 5/14/07, Joseph Mulloy [EMAIL PROTECTED] wrote: At this point I am very annoyed at the fact that the composite extension still does not work on my laptop. I am still unable to use Beryl or Compiz. I submitted this bug over 6 months ago and as far as I can tell it's been completely ignored. I can't even have transparency never mind Beryl. -- Joseph Mulloy [EMAIL PROTECTED] Maybe giving url or bug id would have been helpfull here. best, Jerome Glisse - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
R200 minor cleanups
Hi, find attached some minor cleanups I did while comparing r200 and r300 code. Most of them are indention and cosmetical changes. Only real changes are that I replaced som if (0) with if (R200_DEBUG DEBUG_TEXTURE) It generally reduces the diff between r200 and r300. That's it. Review and commit please, Christoph Brill r200-updates.tar.bz2 Description: application/bzip-compressed-tar - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R200 minor cleanups
Christoph Brill wrote: Hi, find attached some minor cleanups I did while comparing r200 and r300 code. Most of them are indention and cosmetical changes. Only real changes are that I replaced som if (0) with if (R200_DEBUG DEBUG_TEXTURE) It generally reduces the diff between r200 and r300. That's it. Review and commit please, Christoph Brill Hmm, personally I'm not too happy with kernel-style indentation (and worse, some parts of the driver but not others converted to it). But maybe that's just me. If you're truely going to unify the drivers, there is obviously no way around that (though you could just convert r300 to use style of radeon/r200...) but if the files are still separate anyway I don't see much point. Other opinions? Roland - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R200 minor cleanups
Am Montag, den 14.05.2007, 22:53 +0200 schrieb Roland Scheidegger: Christoph Brill wrote: Hi, find attached some minor cleanups I did while comparing r200 and r300 code. Most of them are indention and cosmetical changes. Only real changes are that I replaced som if (0) with if (R200_DEBUG DEBUG_TEXTURE) It generally reduces the diff between r200 and r300. That's it. Review and commit please, Christoph Brill Hmm, personally I'm not too happy with kernel-style indentation (and worse, some parts of the driver but not others converted to it). But maybe that's just me. If you're truely going to unify the drivers, there is obviously no way around that (though you could just convert r300 to use style of radeon/r200...) but if the files are still separate anyway I don't see much point. Other opinions? Roland I don't really have an opinion on that. The only thing I dislike in the r200 code is that it uses spaces for indents. But that's only my opinion. We can choose whatever indention you like. Note: I'm not 100% sure if merging r300 and r200 code is usefull or even possible. I generally think there is a high amount of redundancy that could be unified. But I need to check that against radeon first before I really continue to do so. I'd rather say to keep my patches out of git for now until a decision for indention was made. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R200 minor cleanups
On 5/14/07, Christoph Brill [EMAIL PROTECTED] wrote: Am Montag, den 14.05.2007, 22:53 +0200 schrieb Roland Scheidegger: Christoph Brill wrote: Hi, find attached some minor cleanups I did while comparing r200 and r300 code. Most of them are indention and cosmetical changes. Only real changes are that I replaced som if (0) with if (R200_DEBUG DEBUG_TEXTURE) It generally reduces the diff between r200 and r300. That's it. Review and commit please, Christoph Brill Hmm, personally I'm not too happy with kernel-style indentation (and worse, some parts of the driver but not others converted to it). But maybe that's just me. If you're truely going to unify the drivers, there is obviously no way around that (though you could just convert r300 to use style of radeon/r200...) but if the files are still separate anyway I don't see much point. Other opinions? Roland I don't really have an opinion on that. The only thing I dislike in the r200 code is that it uses spaces for indents. But that's only my opinion. We can choose whatever indention you like. Note: I'm not 100% sure if merging r300 and r200 code is usefull or even possible. I generally think there is a high amount of redundancy that could be unified. But I need to check that against radeon first before I really continue to do so. I'd rather say to keep my patches out of git for now until a decision for indention was made. If you want to reunify some more function i think you should stick to radeon indentation as you won't likely rewrite most of it, so better follow its code guideline. That said i have the feeling that if we ever want to have ttm on radeon (and i believe we do :)) we will some times need to rewrite most of it at least i did have the impression that most others dev thought that. best, Jerome Glisse - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: R200 minor cleanups
My thoughts are, we should unify the really common stuff... but I don't think it's possible to unify r200_tex.c and r300_tex.c. The hardware is different, and the file would end up with an #ifdef on every 3rd line; it doesn't make sense here. Just for really common code it does. I don't know what is going to happen with TTM. Maybe we should hack the r300 driver for TTM (and someone else can do R200 and R128 (radeon) if they like) or maybe we should start a new DRI driver completely from scratch, with TTM and good state handling in mind from the beginning. Then we just take the code we need from R300 and merge it into the new DRI driver. Regarding indenting, I indented the driver with the Linux kernel style because that is what matched most (but not all) of the code. The indenting was a little inconsistent. If you like, fell free indent the R200 or R128 (radeon) code, too. I guess for TTM we'll have to wait and see what happens... On 5/14/07, Jerome Glisse [EMAIL PROTECTED] wrote: On 5/14/07, Christoph Brill [EMAIL PROTECTED] wrote: Am Montag, den 14.05.2007, 22:53 +0200 schrieb Roland Scheidegger: Christoph Brill wrote: Hi, find attached some minor cleanups I did while comparing r200 and r300 code. Most of them are indention and cosmetical changes. Only real changes are that I replaced som if (0) with if (R200_DEBUG DEBUG_TEXTURE) It generally reduces the diff between r200 and r300. That's it. Review and commit please, Christoph Brill Hmm, personally I'm not too happy with kernel-style indentation (and worse, some parts of the driver but not others converted to it). But maybe that's just me. If you're truely going to unify the drivers, there is obviously no way around that (though you could just convert r300 to use style of radeon/r200...) but if the files are still separate anyway I don't see much point. Other opinions? Roland I don't really have an opinion on that. The only thing I dislike in the r200 code is that it uses spaces for indents. But that's only my opinion. We can choose whatever indention you like. Note: I'm not 100% sure if merging r300 and r200 code is usefull or even possible. I generally think there is a high amount of redundancy that could be unified. But I need to check that against radeon first before I really continue to do so. I'd rather say to keep my patches out of git for now until a decision for indention was made. If you want to reunify some more function i think you should stick to radeon indentation as you won't likely rewrite most of it, so better follow its code guideline. That said i have the feeling that if we ever want to have ttm on radeon (and i believe we do :)) we will some times need to rewrite most of it at least i did have the impression that most others dev thought that. best, Jerome Glisse - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
