From: <bug...@an...> - 2006-10-31 01:52:36
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8816 ------- Additional Comments From ag...@ya... 2006-10-30 17:52 ------- (In reply to comment #15) > > Thanks - I should have stuck to IRC, cause I knew this would be a wontfix and > merely wanted help with trying to debug it on my own. > > It wasn't my intent to start this discussion about disabling the option, I > personally think that despite the pain of having to tell users that AGPFastWrite > is a bad idea, they should still have the choice of trying it out, so making the > option a no-op is not nice. Worse, if you make it a no-op, users will actually > think that it worked, and misinformation of already not very well informed users > doesn't sound like a well thought out plan either. I'm sorry we sound so discouraging, but I guess we're a bit jaded. Too many users complain the driver in broken only to reveal much later (after much wasted developer time) that they have fastwrites turned on. As such it's a bit of a knee-jerk reaction. The problem is, there's not really a good way to debug this. There have been several suggestions, but the problem is it locks up bad and years later still no one knows why. You could try and track down what fglrx does (if anything) by dumping the radeon and AGP chipset regs. Since you haven't had much luck with conventional software means, you may need access to hardware analyzers or unpublished chipset errata. Perhaps others with more AGP chipset-side knowledge have some ideas. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |