Date: Tue, 17 Jan 95 8:09:29 CST From: Jim Babb <babb@sedhps01.mdc.com> To: bde@zeta.org.au (Bruce Evans) Cc: freebsd-hackers@FreeBSD.org, j@uriah.sax.de Subject: Re: Colorado 250 Tape Drive Message-ID: <199501171411.GAA08047@freefall.cdrom.com> In-Reply-To: <199501170329.OAA23004@godzilla.zeta.org.au>; from "Bruce Evans" at Jan 17, 95 2:29 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> >As far as i know, the fdc line in the config file does also need a > >``flags 0x1'' clause (right after the `bio' keyword), otherwise the ft > >probe will be skipped. > > History: ft0 was added to generic in case someone wants to install from > ft0. This broke some systems without ft0. The correct way to fix this > is to disable ft0 at (static) config time. However, there is no way to > statically configure the device enable flag (it isn't in `flags' and > config always sets it to 1). The 0x1 flag was hacked on instead. > I think some of the problems that were blamed on the ft driver were actually the spurious interrupts from certain controller chips (which has now been fixed). The only way for the ft probe to screw up a floppy drive (by stepping it too far) is for that drive to be broken and ignore the drive select signal. I would like to work with anyone that has a machine that the ft probe breaks to try and fix the driver (if possible). I think the number of people with working tape drives far outnumber the number of people with broken floppy drives, so the logic of the flag should be inverted, such that you set the flag to *disable* the probe. Jim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501171411.GAA08047>