This is the
talk page for discussing improvements to the
AIGLX article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to multiple WikiProjects. | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Started up the article, linked the Fedora Wiki. Someone might want to add some links, but all I can find are little snippets in blogs which are hardly relevant (and say nothing more than I've described in this article.) My work here is done, so someone else should start fixing all the things I've got wrong. :) LainOfIICHAN 16:22, 27 February 2006 (UTC)
BTW, does this work with/replace Xinerama for running GL (like xscreensaver hacks) across multiple displays?
"hardware-driven usability improvements, such as smoothed fonts, accelerated window-drawing" -- This is a bit misleading because, compared to Xgl which does font smoothing and accel through GL, AIGLX does _NOT_ do so, instead using traditional acceleration.
The first paragraph also suggests that AIGLX has similarities to compiz, which doesn't make sense. AIGLX is analogous to Xgl, but compositing managers like compiz and modified Metacity work one layer above AIGLX/Xgl, and should in theory work with both.
Will hopefully find time to clean up the article, but in the meantime, readers should be aware of these inaccuracies -- lstanley
Hardware support for the product is limited to hardware with free drivers due these changes: currently R200 generation and earlier ATI Radeon cards (R300 drivers are currently in development) and a few Intel embedded onboard video modules.
This is outdated. VIA Unichrome works now, and probably several others as well. In addition, the latest nVidia drivers do support XOrg 7.1, though they don't work with AIGLX.
ATI drivers support X.org 7.1 now. Not sure about AIGLX.
What is the problem?
I'll state my case.
I run Linux and have an ATI card. The facts are quite accurate, there is no AIGLX support, the DRI API used is obsolete, it has been going on for over a year and there is no timelime for its introduction. The development process of the driver has not addressed these fundemental issues. Combined with numerous other flaws:
A Look at the State of ATI Linux Drivers (2005) Posted by timothy on Sat Jul 30, '05 03:53 PM from the better-than-nothing dept. http://linux.slashdot.org/article.pl?sid=05/07/30/197259
The State of ATI Drivers on GNU/Linux (2006) Posted by timothy on Thu Jul 20, '06 11:22 AM from the all-I-want-is-some-hot-3d-action dept. http://linux.slashdot.org/article.pl?sid=06/07/20/1433230
...and end-user feedback of the development process:
Insight Into AMD's Linux Driver Development (2007) Posted by CmdrTaco on Monday June 04, @12:07PM from the they-should-all-wear-hats-while-they-code- dept. http://linux.slashdot.org/article.pl?sid=07/06/04/1532215&from=rss
It is quite clear that there is a serious problem with the skillsets available to ATI. It is not something that has happened recently, nor is it something that is new.
Therefore, I do not feel that there is anything wrong with the point of view, it is an expression of the facts. It just happens to be that the facts paint ATI in a bad light.
Whoever made the dispute would like me to change the facts of reality, not my personal opinion.
I don't know why this is being disputed; I've run AMD/ATI on both Linux (gentoo) and Solaris 10 within the last 24 hours and I can attest to the fact that this is not a biased view, but rather the reality of ATI drivers on *nix. GLX will work on gentoo (sabayon 3.2 only- 3.3, 3.3b, 3.4loop3 all drop the screen like a hot rock) at low refresh, and just barely... the screen 'shakes' and wobbles. AIGLX will not work. I came across this page while trying to find if I can write to the VFB since ATI's lack of driver support has made my solaris development box a brick. I've never commented on a talkpage before, but I'm dealing with this very issue at the moment and thought I'd put in my $.02. 64.9.41.146 01:23, 5 July 2007 (UTC)
Exactly, me and hundreds of forum questions around the Web are trying to deal with the same issue. AMD/Ati's almost complete lack of regard of *nix users. It is really frustrating. Especialy for Mobility Radeon users - my 3D performance is really bad and I can't even use compiz or beryl. 128.86.161.200 13:53, 7 July 2007 (UTC)
I couldn't agree more. This section is "not neutral" because of choices made by ATI and not the editors of this page. I can't think of how to express that ATI does not support Linux without making it sound negative; however, that is the case.
I'm planning a nice color graph on the AIGLX - links between protocols, directions of communication, languages, etc. Be free to suggest your additions. The 1st draft:
User program | X server | Graphic card
Konstantin Kosachev ( talk) 16:23, 15 February 2008 (UTC)
I think this article has a couple good screenshots (and descriptions) of the problem AIGLX fixes: http://smspillaz.wordpress.com/2010/05/21/beware-the-benchmarks/. The author is Sam Spilsbury, primary compiz developer. — Darxus ( talk) 06:35, 3 January 2011 (UTC)
I took the liberty of removing sections that, although useful 4-5 years ago, are misleading and unmaintainable here in "the future". Assistance documenting AIGLX from a historical perspective would be greatly appreciated. I'll leave the tags for someone else to remove. Thanks! Krushia ( talk) 00:03, 20 September 2012 (UTC)
If you are intimately familiar with this subject and are aware of examples of non-trivial coverage from reliable third party publications, could you please add them to the article? I'm not having any luck. AMFMUHFVHF90922 ( talk) 18:50, 28 April 2013 (UTC)
AIGLX replaced Xgl, which was a display server. Therefore, AIGLX should be a display server too, I guess. Am I wrong? If not, then it should be part of Category:Display servers. The term "project" at the beginning of the article is too generic. Should be more specific: library, API, display server or something like that. The product's wiki is not exactly helping in understanding what kind of product it is exactly. It uses the term "technology", which is also too generic. — Ark25 ( talk) 02:56, 24 September 2013 (UTC)
This is the
talk page for discussing improvements to the
AIGLX article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to multiple WikiProjects. | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Started up the article, linked the Fedora Wiki. Someone might want to add some links, but all I can find are little snippets in blogs which are hardly relevant (and say nothing more than I've described in this article.) My work here is done, so someone else should start fixing all the things I've got wrong. :) LainOfIICHAN 16:22, 27 February 2006 (UTC)
BTW, does this work with/replace Xinerama for running GL (like xscreensaver hacks) across multiple displays?
"hardware-driven usability improvements, such as smoothed fonts, accelerated window-drawing" -- This is a bit misleading because, compared to Xgl which does font smoothing and accel through GL, AIGLX does _NOT_ do so, instead using traditional acceleration.
The first paragraph also suggests that AIGLX has similarities to compiz, which doesn't make sense. AIGLX is analogous to Xgl, but compositing managers like compiz and modified Metacity work one layer above AIGLX/Xgl, and should in theory work with both.
Will hopefully find time to clean up the article, but in the meantime, readers should be aware of these inaccuracies -- lstanley
Hardware support for the product is limited to hardware with free drivers due these changes: currently R200 generation and earlier ATI Radeon cards (R300 drivers are currently in development) and a few Intel embedded onboard video modules.
This is outdated. VIA Unichrome works now, and probably several others as well. In addition, the latest nVidia drivers do support XOrg 7.1, though they don't work with AIGLX.
ATI drivers support X.org 7.1 now. Not sure about AIGLX.
What is the problem?
I'll state my case.
I run Linux and have an ATI card. The facts are quite accurate, there is no AIGLX support, the DRI API used is obsolete, it has been going on for over a year and there is no timelime for its introduction. The development process of the driver has not addressed these fundemental issues. Combined with numerous other flaws:
A Look at the State of ATI Linux Drivers (2005) Posted by timothy on Sat Jul 30, '05 03:53 PM from the better-than-nothing dept. http://linux.slashdot.org/article.pl?sid=05/07/30/197259
The State of ATI Drivers on GNU/Linux (2006) Posted by timothy on Thu Jul 20, '06 11:22 AM from the all-I-want-is-some-hot-3d-action dept. http://linux.slashdot.org/article.pl?sid=06/07/20/1433230
...and end-user feedback of the development process:
Insight Into AMD's Linux Driver Development (2007) Posted by CmdrTaco on Monday June 04, @12:07PM from the they-should-all-wear-hats-while-they-code- dept. http://linux.slashdot.org/article.pl?sid=07/06/04/1532215&from=rss
It is quite clear that there is a serious problem with the skillsets available to ATI. It is not something that has happened recently, nor is it something that is new.
Therefore, I do not feel that there is anything wrong with the point of view, it is an expression of the facts. It just happens to be that the facts paint ATI in a bad light.
Whoever made the dispute would like me to change the facts of reality, not my personal opinion.
I don't know why this is being disputed; I've run AMD/ATI on both Linux (gentoo) and Solaris 10 within the last 24 hours and I can attest to the fact that this is not a biased view, but rather the reality of ATI drivers on *nix. GLX will work on gentoo (sabayon 3.2 only- 3.3, 3.3b, 3.4loop3 all drop the screen like a hot rock) at low refresh, and just barely... the screen 'shakes' and wobbles. AIGLX will not work. I came across this page while trying to find if I can write to the VFB since ATI's lack of driver support has made my solaris development box a brick. I've never commented on a talkpage before, but I'm dealing with this very issue at the moment and thought I'd put in my $.02. 64.9.41.146 01:23, 5 July 2007 (UTC)
Exactly, me and hundreds of forum questions around the Web are trying to deal with the same issue. AMD/Ati's almost complete lack of regard of *nix users. It is really frustrating. Especialy for Mobility Radeon users - my 3D performance is really bad and I can't even use compiz or beryl. 128.86.161.200 13:53, 7 July 2007 (UTC)
I couldn't agree more. This section is "not neutral" because of choices made by ATI and not the editors of this page. I can't think of how to express that ATI does not support Linux without making it sound negative; however, that is the case.
I'm planning a nice color graph on the AIGLX - links between protocols, directions of communication, languages, etc. Be free to suggest your additions. The 1st draft:
User program | X server | Graphic card
Konstantin Kosachev ( talk) 16:23, 15 February 2008 (UTC)
I think this article has a couple good screenshots (and descriptions) of the problem AIGLX fixes: http://smspillaz.wordpress.com/2010/05/21/beware-the-benchmarks/. The author is Sam Spilsbury, primary compiz developer. — Darxus ( talk) 06:35, 3 January 2011 (UTC)
I took the liberty of removing sections that, although useful 4-5 years ago, are misleading and unmaintainable here in "the future". Assistance documenting AIGLX from a historical perspective would be greatly appreciated. I'll leave the tags for someone else to remove. Thanks! Krushia ( talk) 00:03, 20 September 2012 (UTC)
If you are intimately familiar with this subject and are aware of examples of non-trivial coverage from reliable third party publications, could you please add them to the article? I'm not having any luck. AMFMUHFVHF90922 ( talk) 18:50, 28 April 2013 (UTC)
AIGLX replaced Xgl, which was a display server. Therefore, AIGLX should be a display server too, I guess. Am I wrong? If not, then it should be part of Category:Display servers. The term "project" at the beginning of the article is too generic. Should be more specific: library, API, display server or something like that. The product's wiki is not exactly helping in understanding what kind of product it is exactly. It uses the term "technology", which is also too generic. — Ark25 ( talk) 02:56, 24 September 2013 (UTC)