There's not really a reason to have _any_ device bang on the memory before it's asked to by the current device manager (ie. BIOS or OS) and its drivers.
It's a shame the author (mjg59?) did not respond to hpa's comment - it seems the "obvious" solution.
2. Drivers that depend on this: which ones? Are they hard to fix?
Obligatory: I'm a kernel developer so I may be overly optimistic, but isn't this a security problem, at least in one sense? (That is, a malicious device may try to use bus mastering to attack a running kernel.)
However, what if the malicious device is actually a compromised but popular vendor who ships malicious firmware? That wouldn't be a stretch.
Resetting devices and fixing drivers isn't a huge win, but it's still an improvement. Like ASLR doesn't actively prevent buffer overflows - it just makes attacks more difficult.
Actual: a pretty interesting debugging story involving a misbehaving driver DMA'ing things into memory where it shouldn't.