3 ms·
As a HW designer who over the years has deal with many HW bugs, it’s amusing to see how almost everybody is agreeing that it’s a software issue “because it goes
by TomVDB 4y ago
As a HW designer who over the years has deal with many HW bugs, it’s amusing to see how almost everybody is agreeing that it’s a software issue “because it goes away when I restart or when I close this or that application…”
As if SW applications that stress the system in some way are capable of triggering a HW bug?
And if the issue eventually does get solved with a SW update, then it most definitely was a SW bug, because software update that work around a HW bug aren’t a thing.
- kalleboo 4y agoThe audio hardware is integrated into the M1 SoC, so if this was a hardware issue I guess it would also affect iPads, right?
- TomVDB 4y agoWho knows? I’ve seen cases where a functional block of an SOC got used one generation to the next without even seeing an issue. And then suddenly, due to changing boundary conditions, a bug got triggered. I’ve similarly seen cases where HW bugs were known but SW workarounds where calculates to reduce the chances of them manifesting themselves to be low enough. Until they suddenly didn’t. The state space of HW is incredible, and it’s often not possible to foresee or understand the interactions between of SW and HW.
- kevincox 4y ago> because software update that work around a HW bug aren’t a thing. This definitely isn't true. We have seen microcode updates that work around buggy CPUs before. Often by taking a slow path for buggy cases. For example there were microcode updates to "fix" (moderately mitigate) Specter and Meltdown which were almost certainly hardware bugs.
- mrpf1ster 4y agoI believe he was being sarcastic.