Right its a good movement and the result is a profit even if the solution isn't here for now.
Originally Posted by bridgman
But now its up to AMD to fix this mess.
Well, the code is still supposed to be there. Unless it's obfuscated. Or a needle in a haystack. Or a "why is this here to begin with" type of code. All of the cases being a result of poor code commenting/management.
Originally Posted by curaga
I explain in my blog post why there might very well be no errata or special code in the closed source driver for the issue i am hitting. So to paraphrase myself, fglrx is doing things differently than the open source driver and this is the out come of many things :
Originally Posted by GreatEmerald
- intentional to work around some issue
- out come of driver stack architecture
- human that wrote the code, wrote that register A before register B with no special intention to do so
In the end due to those difference the closed source driver might never trigger the issue the open source driver is facing. This is a possibility. If that the case no one in AMD/ATI ever faced the hang we are having and thus no errata for it was ever written.
So, no, there is not necesarily any code in fglrx that work around the issue we are having. Furthermore as i said, if there is such code, it might very well not be documented as a work around or errata, it might be some engineer fixed it and forgot about filling errata for all the reason human forgot about things.
Or maybe the planets were in the right order when AMD wrote catalyst command stream emition code, and didn't revealed the bug. Unfortunately Mesa developers weren't that lucky
Missing the point
Reading comment here, i obviously failed at making my point, AMD contributed a lot of engineering time helping me on hyperz. My point was that it's stupid to blame AMD for this because they might very well just don't have the information we need, or if they have this information they might ignore they have it because some one forgot to document it.
It's just life, maybe i should do an hyperz bumper sticker for my car ...
That's probably a fair statement.
Originally Posted by Drago
There are all kinds of advantages that come from designing the HW and SW together, but the downside is that you end up with some unspoken, undocumented assumptions.
Typical example -- during early design HW dev explains a particular function to SW dev on a whiteboard, explanation shows the HW getting inputs in a certain sequence. SW dev now thinks about the HW that way. When it comes time to write the code, they organize operations in the same sequence the HW dev talked about a few months earlier... not because it's the only way to do it, not because it's even the "official" way to do it, but it's what was in the HW dev's head at the time they designed the block. SW dev writes the code, it works and gets integrated into the rest of the driver stack, everyone is happy.
The only real solution for that is to write open source driver software at the same time as proprietary driver software, run it on the same simulators & emulators, and be able to talk to the HW folks about odd issues like this while everything is still fresh in their heads AND we can try to reproduce on the emulators to see what is happening inside the chip.
I know people complained a lot about us working on support for new hardware when features were still missing from older hardware, but realistically the only way for this to work is if open source drivers are written and tested alongside the rest of the engineering effort. Getting there took 5 years of really hard work from the developers (basically supporting 10 years of hardware in 5 years) and I'll take a bit of credit for getting open source drivers at least partially integrated into the top level planning efforts, but I'm hoping you'll see the benefits and understand why we did this in the future.
We were a bit too late for this to give much benefit for SI since the HW focus had already moved to the next gen even though we started months before SI launch, but (crosses fingers) hopefully that will be the last time.
Wait until it's working... then you can get one of those "I fought HyperZ and won... and so can you !!" stickers
Originally Posted by glisse
EDIT -- tried to add "Hyper" to Captain Z-Ro's uniform ( http://www.dhark.com/CAPTAIN_Z-RO/index.html ) but it didn't work well...
Last edited by bridgman; 07-14-2012 at 07:51 PM.
You da man.
Originally Posted by maldorordiscord
Now we just need to get that onto a T-shirt for glisse.
Auggh !! My eyes !!!
Originally Posted by maldorordiscord
Last edited by bridgman; 07-14-2012 at 09:21 PM.