Author: Burstaholic
Subject: AGESA 1.0.0.6
Posted: 22 Jun 2017 at 1:19am
Good grief. The AGESA code is the same for everyone, but obviously everyone's actual BIOS is different, and therefore the process of integrating the two is at least a little different. If you don't understand/believe that I could dig up links to statements from AMD and others explicitly saying so, but come on.
Software is complicated - from the outside we do not have enough information to share out blame.
Maybe ASRock is having a harder time making the new AGESA play nice with their BIOS and hardware than other vendors, but if for example it is because of some cool feature they have that others don't, it would be worth it. Maybe AMD's changes do something that's harder to adapt to some random choice ASRock made writing their BIOS that others made differently - is that AMD's fault for screwing them over, or their fault for not being clairvoyant?
Neither, because software is complicated and there's no way to anticipate every problem and complication. We don't have enough information to share out blame in a useful way and angry speculation isn't helpful, especially going round with "It could be A's fault!" "Yes, but it could also be B's fault" endlessly.
Subject: AGESA 1.0.0.6
Posted: 22 Jun 2017 at 1:19am
Good grief. The AGESA code is the same for everyone, but obviously everyone's actual BIOS is different, and therefore the process of integrating the two is at least a little different. If you don't understand/believe that I could dig up links to statements from AMD and others explicitly saying so, but come on.
Software is complicated - from the outside we do not have enough information to share out blame.
Maybe ASRock is having a harder time making the new AGESA play nice with their BIOS and hardware than other vendors, but if for example it is because of some cool feature they have that others don't, it would be worth it. Maybe AMD's changes do something that's harder to adapt to some random choice ASRock made writing their BIOS that others made differently - is that AMD's fault for screwing them over, or their fault for not being clairvoyant?
Neither, because software is complicated and there's no way to anticipate every problem and complication. We don't have enough information to share out blame in a useful way and angry speculation isn't helpful, especially going round with "It could be A's fault!" "Yes, but it could also be B's fault" endlessly.