... this is actually not really a bug, but I can see why valgrind
complains, so let's keep it happy.

It is indeed possible for the pass FIFO to have more than the tag FIFO. If
the TX mux is blocked after popping the tag, but before popping the pass
FIFO, the pass FIFO can have one more element.  Thus, if you have all of the
pending tags landing in the same FIFO (pass, wbm, cfg), you can end up with
the situation where the tag FIFO is indeed less full and thus you refill the
tag FIFO while overflowing the other FIFOs.

The result of this bug is that when writing to slow slaves, a very homogeneous
access pattern can end up with a corrupted word if you are unlucky.

The worst part of this bug is that when I wrote that code, I was uncertain
if this was safe and marked it to be reviewed.  It never got reviewed. Doh.

This reverts commit 8d5e5f78.
It caused pcie to resend the header on each request!

Changing from void return to int return should not change the ABI.

This got lost when '-a' was removed.

- flush command no longer ignored when busy
- commit_len_fifo write pointer bug fixed

fixed ebm manifest and other things screwing with hdlmake. Beware, this change depends on general cores proposed master