Originally posted by Qaridarium
Announcement
Collapse
No announcement yet.
A Batch Of Graphics Cards On Gallium3D
Collapse
X
-
Originally posted by smitty3268 View PostMichael, can you clarify what Phoronix's position on that is? Are you afraid of getting sued if you publish an article using ST3C? I seem to remember some a long time ago, but perhaps not.Michael Larabel
https://www.michaellarabel.com/
Comment
-
Originally posted by whitecat View PostCan you explain ? You mean libtxc_dxtn cannot run on 64 bits ? Sorry if I misunderstood.
Comment
-
Originally posted by Michael View PostBecause it's not "out of the box" configuration... While I'm sure there's a fair number of active Phoronix members that may install it, as far as overall Linux usage goes, how many people do you think will actually go forward and do it or even know about it? Not many at all.
and have a 3rd party (if you're to conservative to host them directly) make and host the S3TC and other related modules bits, that can be if wanted loaded locally or off a web site, just like any other slax module at runtime into the test run.
and then even people without knowing about them at the time can also try it and submit results.
there's already a Phoronix test Suite 1.8.1 slax module made for instance on that page
plus OC in you're case if you want to run many PCs on a LAN with the same options you can simply boot a single slax cd/USB with the included net boot server option and then boot any other PC off that LAN directly into the slax image that gets booted, simple so why not do it
Comment
-
Originally posted by marek View PostThe problem is you need a 32-bit driver in order to accelerate those closed 32-bit apps, i.e. to get direct rendering. If you don't have it, indirect rendering is used, which doesn't have all the features Mesa has - it's stuck at OpenGL 1.4 with a lot less extensions. Things might work but the performance will suck to say the least.
So if I summarize, running ETQW/Doom3 on 64 bits-kernel + libGL.i686 is less optimized than running it on 32 bits-kernel + libGL.i686 ?
Comment
-
Originally posted by whitecat View PostIt's a big information you give to me !
So if I summarize, running ETQW/Doom3 on 64 bits-kernel + libGL.i686 is less optimized than running it on 32 bits-kernel + libGL.i686 ?
Comment
-
Originally posted by marek View PostOn a 64-bit kernel, you need 32-bit Mesa (libGL + driver) and 32-bit libtxc_dxtn, which is not out-of-the-box experience either. Otherwise 32-bit 3D apps will either crash, misrender, or be slow.
- 64-bit kernel
- both 64/32-bit libdrm packages
- both 64/32-bit xorg-x11-drv-ati packages
- both 64/32-bit mesa-dri-drivers, mesa-libGL and mesa-libGLU packages
- both 64/32-bit libtxc_dxtn packages
- a 32-bits game
I shouldn't expect 3D problems ?
Comment
-
Originally posted by whitecat View PostOK, I understand. So in my case, on my system I currently have :
- 64-bit kernel
- both 64/32-bit libdrm packages
- both 64/32-bit xorg-x11-drv-ati packages
- both 64/32-bit mesa-dri-drivers, mesa-libGL and mesa-libGLU packages
- both 64/32-bit libtxc_dxtn packages
- a 32-bits game
I shouldn't expect 3D problems ?
Comment
-
intel rocks @ oss
Looking at this test and some other phoronix graphics tests it seems to me that using a discrete graphics card (other than X1xxx) with an opensource driver provides only minimal advantage over running an 2500K igp (exluding lightsmark). just stunning. or did i get the wrong impression?
Comment
Comment