Using web site hits obviously leaves out embedded systems and PCs without internet connections but for consumer PC market analysis that is probably reasonable (since we have other channels for embedded support).
The server market is significantly different -- Linux is closer to 25% than 1% -- but servers tend to use stone-age graphics so again I think it's reasonable to exclude those numbers. The commercial workstation market also has a higher percentage of Linux users (mostly coming over from the proprietary Unix world) but workstation is pretty much entirely a closed-source business because of the extremely high performance expectations.
Last edited by bridgman; 12-30-2008 at 04:31 PM.
For that reason I can't use compiz effects, because I can't watch video while effects are on. I would really like to know how can tearless video work with radeon driver, but not with fglrx. Even 3D applications don't flicker with compiz turned on, and all that without DRI2. I'm not the driver developer, but my guess is that while using fglrx, compiz always redraws the whole screen, while while using radeon, it redraws parts of the screen where changes occurred. I can see that when I start a full screen 3D game with compiz turned on: with radeon, the only part of the screen that flickers is the one where is conky placed (or any other window that has to be redrawed often), and with fglrx, the whole screen flickers.
Btw., keep up with good work, AMD! Thank you very much for releasing the documentation for your graphics cards. Please, release the PowerPlay documentation ASAP - all ATI laptop users would be very grateful.
Power management info for 5xx is mostly out there already (in the AtomBIOS header & tables) and is gradually being included into the open source drivers. Power management for 6xx and up is quite different; that's next on our list but is going to be both time-consuming to document and difficult to use.
Right now most of the open source power management work is being done in the userspace drivers, which limits the amount of power saving possible -- eventually power management is going to have to be done in the drm (kernel module) if we want to match what the proprietary drivers can do.
3D apps *should* flicker under Compiz even with the open source drivers, unless you have the "don't redirect fullscreen windows" option set in Compiz and are running a fullscreen app (that works with fglrx as well). The video code in fglrx is being upgraded so you should continue to see improvements there.
This way you made yourself feel out of your ass better?But...I'll make you feel better. When your market share is less than 2 percent (and after all this time, to boot) it's hard to get people very interested in you. Fact of life.
What time to boot?
Btw. Now I'm sure that my next card will be AMD/Ati :> Thanks for that!
Last edited by kraftman; 12-30-2008 at 04:44 PM.
PowerPlay is WIP, as John mentioned, don't worry.
I will happily play Nexuiz with the crappy OpenGL 1.3 implementation of this driver anyday over fglrx that hangs my computer upon exiting Nexuiz.
Compiz is waaaaaaaaaaaaay faster than what fglrx delivers. 2d is waaaaaaaaaaaaaay faster. Even probably OGL 1.3 is faster than OGL 1.3 in fglrx.
Tear-freaking-free video playback!
Flicker-freaking-free video playback with compiz!
So to me, why you use fglrx, is a bit unjustified when you have in mind all the goodies coming in 2009 like Gallium, KMS, DRI2.
I will not be using fglrx anytime soon, even if they decode video with the GPU, but that won't be possible on r500 anyway. Fglrx is just one long, boring drag. I've had enough of it.
Last edited by sundown; 12-30-2008 at 05:38 PM.