Comment 295 for bug 441835

peter b [2010-11-25 21:12 -0000]:
> Martin, pls do not look at what follows as an intrusion into your good
> efforts in resolving this issue

To the contrary -- it seems this bug needs more thinking/involvement,
not less :-)

> basics are still there with little changes ) ; I may be wrong in this
> but pls check my thoughts out and take a look at the floppy drive/device
> probing procedure code and maybe introduce a timer in device call
> loop/iterations and based on the feedback (y or n) obtained introduce an
> if/else decision followed by a goto statement to the corresponding line
> of code that will either configure or not configure the device (or maybe
> call another file/s with the conf procedures). pls tell me what's your
> opinion - will it do the trick ?

This would need to happen in the kernel, though; I'm pretty sure that
it already has a timeout, since the detection calls do fail eventually
- it just takes excruciatingly long (some 20 seconds).