53 minutes ago, ZeroByte said:
The YM read also has one more important functionality than IRQ checking - the busy flag.
Right. I omitted that intentionally, which makes it all the dumber. I was thinking applications would schedule writes on their own. But the schedule would be for blocks of writes, not individual ones. Thanks for the correction.
Anyway, I suppose it is possible reads are working on the bench but that is almost worse. It is much better for things to be broken-broken, not sometimes-broken or sometime-in-the-future-broken. It would suck to have a batch of slow parts causing sound problems halfway through a production run. It's even worse if the slow parts break a bunch of DIY kits.