Originally posted by glisse
View Post
Announcement
Collapse
No announcement yet.
Where The Open-Source AMD Driver Is At For Modern GPUs
Collapse
X
-
damn edit time
btw i discovered that K/ubuntu normally set the cpu scheduling to conservative and actually unless you have a laptop or a good acpi implementation in the bios(i assume that it exists somewhere) the cpu is always set to the lower frequency available and it never goes up (same with ppa ubuntu kernels).
the point been that i discovered that when i set my phenom II X4 955 to preformance scheduler my fps jump very hard aka nexuiz default 20ish fps -- performance cpu/ mid gpu 40 ish
Comment
-
Originally posted by glisse View PostKernel side is one part of the issue if you want to compete with catalyst. Right now the biggest issue is in r600g itself. Thought given the number of r600g needs i fear that kernel side might also impact it a little bit more than r300g.
Comment
-
Originally posted by glisse View PostKernel side is one part of the issue if you want to compete with catalyst. Right now the biggest issue is in r600g itself. Thought given the number of r600g needs i fear that kernel side might also impact it a little bit more than r300g.
- What are the r600g needs (on performance side)?
- Are they being implemented?
- They will solve the performance problems r600g has?
Comment
-
The main reason r300 is closer to catalyst is that more people have been working on it longer compared to r600.
Some of the things r300 has that haven't been implemented yet on r600:
- texture tiling
- flushing only when necessary
- limited threading
- hyper Z
- fast clears
- lots of vertex upload optimizations
- more optimized shader compiler
Comment
-
-
Originally posted by bug77 View PostTell that to millions of happy Windows and MacOS users.
Free software is not even an argument, it's a boon. First, the software has to work, that's the killer argument.
Comment
-
Soemthing I've longed wondered...
In the best cases (in terms of drivers) how much does Mesa hurt performance? I've long heard that Mesa was in need of, at least, some re-factoring, but I've not heard anyone come out with actual numbers as to how much it is hurting the OSS stack.
Does anyone have any idea?
Comment
Comment