From: Dave W. <daw...@sb...> - 2010-03-09 02:30:07
|
Was using Mesa 7.8-devel (git commit be1b7d1) of Mar. 3; upgraded to 7.9-devel (git commit 3ca9336) of Mar. 8. Hardware is Radeon HD 4850 (RV770). Don't know who to thank -- most likely candidate seems to be series of radeon patches from Maciej Cencora -- but I got a nice (subjective) performance boost on the applications I've tested. One game, torcs, has a built-in framerate indicator, and I'm getting roughly 10% more FPS there. Thanks, Dave W. |
From: Dave W. <daw...@sb...> - 2010-03-09 06:12:41
|
Dave Witbrodt wrote: > Was using Mesa 7.8-devel (git commit be1b7d1) of Mar. 3; upgraded to > 7.9-devel (git commit 3ca9336) of Mar. 8. Hardware is Radeon HD 4850 > (RV770). So, after I sent my last message, I took another look at the Mesa git tree and saw there were some new commits relevant to my hardware. I built yet another, newer version of Mesa (up to commit 4243ca1). I'm very happy with that as well. Then I noticed that kernel 2.6.34-rc1 has been released. So I built that and installed it. When I booted, I found this in 'dmesg': You have old & broken userspace please consider updating mesa MUAHAHAHAHAAHAHA Dave W. |
From: tom f. <tf...@al...> - 2010-03-09 18:08:24
|
Dave Witbrodt <daw...@sb...> writes: > So, after I sent my last message, I took another look at the Mesa git > tree and saw there were some new commits relevant to my hardware. I > built yet another, newer version of Mesa (up to commit 4243ca1). I haven't taken a look at what, exactly, 4243ca1 is.. but if you're using recent git (master) versions of Mesa, as opposed to released tarballs, I think the best place for these mails is on the developers mailing list. I'm not sure how many radeon devs follow this list. Cheers, -tom |
From: Dave W. <daw...@sb...> - 2010-03-09 20:30:30
|
tom fogal wrote: > Dave Witbrodt <daw...@sb...> writes: >> So, after I sent my last message, I took another look at the Mesa git >> tree and saw there were some new commits relevant to my hardware. I >> built yet another, newer version of Mesa (up to commit 4243ca1). > > I haven't taken a look at what, exactly, 4243ca1 is.. but if you're > using recent git (master) versions of Mesa, as opposed to released > tarballs, I think the best place for these mails is on the developers > mailing list. I'm not sure how many radeon devs follow this list. The context of providing that commit ID was my previous message, where I mentioned ... Was using Mesa 7.8-devel (git commit be1b7d1) of Mar. 3; upgraded to 7.9-devel (git commit 3ca9336) of Mar. 8. The 4243ca1 commit ID is also from Mesa 7.9-devel. I didn't post my message to the developer list because I assumed that the whole purpose of having two lists was to separate code/bug-related messages from general comments. Since my little thank-you message contained no information relevant to the developer list, I thought I should not post it there. If Mesa developers do not want to read user comments (which would be strongly suggested in the case of a developer who is NOT subscribed to this list), then maybe it is for the best that their time isn't wasted by having had to read my message. If you believe there was important info in my message that should appear on the developers' list, I'll be glad to forward it over to there. (Or, you could post a message over there letting people know about this message.) Thanks, Dave W. |
From: tom f. <tf...@al...> - 2010-03-09 20:47:18
|
Dave Witbrodt <daw...@sb...> writes: > tom fogal wrote: > > Dave Witbrodt <daw...@sb...> writes: > I didn't post my message to the developer list because I assumed > that the whole purpose of having two lists was to separate > code/bug-related messages from general comments. Since my little > thank-you message contained no information relevant to the developer > list, I thought I should not post it there. I agree with the general logic about separation. I'm not sure a "thanks!" falls into either category though. > If Mesa developers do not want to read user comments (which would be > strongly suggested in the case of a developer who is NOT subscribed > to this list), then maybe it is for the best that their time isn't > wasted by having had to read my message. I cannot presume to speak for any developer. > If you believe there was important info in my message that should > appear on the developers' list, I'll be glad to forward it over to > there. (Or, you could post a message over there letting people know > about this message.) It seemed to me like your note about the message you saw from the kernel was either surprising or indicative a bug. I don't use DRM though, maybe this is normal, I have no idea. If it was a bug, it should definitely be forwarded. -tom |
From: Dave W. <daw...@sb...> - 2010-03-09 20:53:34
|
>> If you believe there was important info in my message that should >> appear on the developers' list, I'll be glad to forward it over to >> there. (Or, you could post a message over there letting people know >> about this message.) > > It seemed to me like your note about the message you saw from the > kernel was either surprising or indicative a bug. I don't use DRM > though, maybe this is normal, I have no idea. If it was a bug, it > should definitely be forwarded. Oh, that. Now I understand. I was not reporting a bug or registering a complaint. It was just really funny that I had the most up-to-date git version for Mesa built and installed, but the new 2.6.34-rc1 kernel thought my version of Mesa was too old and I should consider updating. Update to what?! :-) None of this should distract Mesa developers for even a split second, so I don't think I'll put it on the developer list.... DW |