Originally posted by dffx
View Post
Announcement
Collapse
No announcement yet.
RadeonSI Gallium3D Gets UBO/TBO Support, OpenGL 3.3
Collapse
X
-
Originally posted by bridgman View Post- the "firmware" debates related to using AtomBIOS -- low level firmware shared by VBIOS and gfx drivers -- not the on-GPU microcode
- you might find starting with 5xx acceleration and moving forward works better than starting with SI/CI and moving backward, since each new programming guide assumes some familiarity with the previous generations rather than making each subsequent doc longer and harder to read
#if FGLRX
//do gl stuff very very fast
#else
//do less gl stuff slower
#endif signed by evil AMD
instead of the reality, where microcode and firmwares are used to power on the blocks in the chip/set boot freqs/expose API interfaces/etc which end up been completely unrelated to speed or features as long as you get all microcodes ofc[r600g and radeonsi do have them all btw]
another interesting fact is that even if AMD release the microcode/firmware they most likely will be useless since you don't have the chip blueprints electronically speaking and without it you just will see a bunch of lines of nemo/hexa code that makes no sense, hence a new cycle of whine will start but for blueprints because evil AMD nerf open drivers in the chip, etc repeat cycle.
the only real reason that fglrx is faster is :
r600g/radeonsi send too much redundant shader data to the GPU[vadim did an superb job with SB to help here for r600g] and the cpu related code have more latency, which translate the GPU is not feed fast enough and have to do more work per frame because the shader code is not optimal enough and thats it, there is no conspiration theory.
Comment
-
Sorry for hijacking...
Originally posted by HD7950 View PostCode:OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.0-devel (git-86cdff5) OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.0.0-devel (git-86cdff5) OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions:
Code:OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL version string: 2.1 Mesa 10.0.0-devel (git-86cdff5) OpenGL shading language version string: 1.30 OpenGL extensions:
Code:/autogen.sh --prefix=/opt/xorg --with-dri-drivers=radeon,r200 --with-gallium-drivers=r300,r600,radeonsi,swrast --with-egl-platforms=x11,drm --enable-gbm --enable-shared-glapi --enable-glx-tls --enable-driglx-direct --enable-r600-llvm-compiler --enable-xorg --enable-xa --enable-gallium-egl --enable-gallium-gbm --enable-texture-float
Comment
-
Originally posted by fooza View PostSorry for hijacking...
Hmm, can someone explain why my mesa build shows this:
Code:OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL version string: 2.1 Mesa 10.0.0-devel (git-86cdff5) OpenGL shading language version string: 1.30 OpenGL extensions:
Code:/autogen.sh --prefix=/opt/xorg --with-dri-drivers=radeon,r200 --with-gallium-drivers=r300,r600,radeonsi,swrast --with-egl-platforms=x11,drm --enable-gbm --enable-shared-glapi --enable-glx-tls --enable-driglx-direct --enable-r600-llvm-compiler --enable-xorg --enable-xa --enable-gallium-egl --enable-gallium-gbm --enable-texture-float
Comment
-
Originally posted by fooza View PostHmm, can someone explain why my mesa build shows this:
Code:OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL version string: 2.1 Mesa 10.0.0-devel (git-86cdff5) OpenGL shading language version string: 1.30 OpenGL extensions:
Code:/autogen.sh --prefix=/opt/xorg --with-dri-drivers=radeon,r200 --with-gallium-drivers=r300,r600,radeonsi,swrast --with-egl-platforms=x11,drm --enable-gbm --enable-shared-glapi --enable-glx-tls --enable-driglx-direct --enable-r600-llvm-compiler --enable-xorg --enable-xa --enable-gallium-egl --enable-gallium-gbm --enable-texture-float
Comment
-
Originally posted by bridgman View Post
- you might find starting with 5xx acceleration and moving forward works better than starting with SI/CI and moving backward, since each new programming guide assumes some familiarity with the previous generations rather than making each subsequent doc longer and harder to read
That's a great tip. Thanks.
Comment
-
Originally posted by frosth View PostL4D2 on my hd7770 works ok but serious sam crash with llvm assertion bug. So Source seems ok.
Dota2 even improved (no glitches in the menu anymore) but sound is also gone.
Sound for Mark of the ninja and everywhere else however works fine - whats going on? which logs can I provide?
Code:grep EE /var/log/Xorg.0.log [ 7.719] Current Operating System: Linux linux.site 3.12.0-3-desktop #1 SMP PREEMPT Mon Nov 4 12:54:39 UTC 2013 (ec24572) x86_64 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 7.725] Initializing built-in extension MIT-SCREEN-SAVER [ 7.738] (EE) Failed to load module "fglrx" (module does not exist, 0) [ 7.740] (EE) Failed to load module "vesa" (module does not exist, 0)
Comment
Comment