On 10/1/19 8:26 PM, Martin K. Petersen wrote:
Ok, then why make this a module option that you will have to support for the next 20+ years anyway if you feel this fix is the correct way that it should be done instead?
I agree.
Why not just shut FCP down unconditionally on excessive bit errors? What's the benefit of allowing things to continue? Are you hoping things will eventually recover in a single-path scenario?
Experience told me that there will be an unforeseen end user scenario where I need a quick switch to let even shaky paths survive.