From: Alexander S. <Ale...@at...> - 2003-02-19 12:03:38
|
> > Here my system > > > > Athlon Xp-1600+ > > Hercules 3D Prophet All-In-Wonder 8500DV ( 64mb ) > > slackware 8.1 > > kernel 2.4.20 > > xfree86 4.2.99.2 > > dri ( cvs version downloaded on 23/01/2003 ). > > > > I downloaded dri and compiled it with ( #define > MesaUse3DNow YES && > > #define MesaUseKatmai YES ) in > ~/DRI-CVS/build/xc/config/cf/host.def but > as > > you can see it in my log files, dri is disabled and it seems startx > doesn't > > load r200 for my radeon graphics adapter. > > IIRC, isn't the Katmai instruction set proprietary to the > Pentium III CPUs? > The problem could start right there with how you compiled it. > However, I > haven't enough experience with DRI to know for certain. > > CaptJosh in historical order: MMX = Intel design, later integrated into AMD CPUs; slight performance advantages 3DNow! = AMD design, never integrated into Intel CPUs; significant performance boost SSE = Intel design, later integrated into AMD CPUs; significant performance boost 3DNow!-2 = AMD design, never integrated into Intel CPUs; extension to 3DNow! SSE2 = Intel design, later integrated into AMD CPUs(?); extension to SSE non x86 platforms have their own sort "vectorized" processor opcodes. hitting the point, the latest family of AMD CPUs (say the Athlon) does provide SSE(2) as well so a setting as described above should work in terms of CPU compatibility. its just the question how internal designs are, meaning which implementation path will be selected. further there is the doubt if permanently swiching between the models will impact performance. -Alex. |
From: Leif D. <lde...@re...> - 2003-02-19 19:46:25
|
On Wed, 19 Feb 2003, Alexander Stohr wrote: > > > Here my system > > > > > > Athlon Xp-1600+ > > > Hercules 3D Prophet All-In-Wonder 8500DV ( 64mb ) > > > slackware 8.1 > > > kernel 2.4.20 > > > xfree86 4.2.99.2 > > > dri ( cvs version downloaded on 23/01/2003 ). > > > > > > I downloaded dri and compiled it with ( #define > > MesaUse3DNow YES && > > > #define MesaUseKatmai YES ) in > > ~/DRI-CVS/build/xc/config/cf/host.def but > > as > > > you can see it in my log files, dri is disabled and it seems startx > > doesn't > > > load r200 for my radeon graphics adapter. > > > > IIRC, isn't the Katmai instruction set proprietary to the > > Pentium III CPUs? > > The problem could start right there with how you compiled it. > > However, I > > haven't enough experience with DRI to know for certain. > > > > CaptJosh > > in historical order: > > MMX = Intel design, later integrated into AMD CPUs; slight performance > advantages > 3DNow! = AMD design, never integrated into Intel CPUs; significant > performance boost > SSE = Intel design, later integrated into AMD CPUs; significant performance > boost > 3DNow!-2 = AMD design, never integrated into Intel CPUs; extension to 3DNow! > SSE2 = Intel design, later integrated into AMD CPUs(?); extension to SSE > > non x86 platforms have their own sort "vectorized" processor opcodes. > > hitting the point, the latest family of AMD CPUs (say the Athlon) > does provide SSE(2) as well so a setting as described above should work FYI, current Athlons have SSE, but not SSE2 (maybe hammer does?). > in terms of CPU compatibility. its just the question how internal designs > are, meaning which implementation path will be selected. further there is > the doubt if permanently swiching between the models will impact > performance. > > -Alex. -- Leif Delgass http://www.retinalburn.net |