From owner-freebsd-hackers Tue Jan 24 03:40:20 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA28612 for hackers-outgoing; Tue, 24 Jan 1995 03:40:20 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA28593 for ; Tue, 24 Jan 1995 03:39:32 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA28709; Tue, 24 Jan 1995 12:32:59 +0100 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id MAA19630 for freebsd-hackers@FreeBSD.org; Tue, 24 Jan 1995 12:32:58 +0100 Received: by bonnie.tcd-dresden.de (8.6.8/8.6.6) id LAA21122; Tue, 24 Jan 1995 11:57:18 +0100 From: j@uriah.sax.de (J Wunsch) Message-Id: <199501241057.LAA21122@bonnie.tcd-dresden.de> Subject: Re: Floppy tape probe patch To: steve2@genesis.nred.ma.us (Steve Gerakines) Date: Tue, 24 Jan 1995 11:57:17 +0100 (MET) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199501240745.XAA03010@genesis.nred.ma.us> from "Steve Gerakines" at Jan 23, 95 11:45:53 pm X-Phone: +49-351-8141 137 Reply-To: joerg_wunsch@uriah.sax.de X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1428 Sender: hackers-owner@FreeBSD.org Precedence: bulk As Steve Gerakines wrote: | | Here's a set of patches against -current that should fix the probe | issues that were brought up. The "output in input" messages should be | gone and people without tape drives should not see any drive activity. Good news! | Also, the ft driver brought out the output on input messages because | it is polling for a seek or recalibrate completion by sending sense | interrupt commands to the fdc. The fd driver doesn't see them because | it doesn't poll, it just waits a long time and hopes that it finished. | This is impractical for ft because the the probe would take too long. Hmmmm. Perhaps fd should also poll. On the other hand, polling the FDC is dangerous (the danger is only being eliminated by in_fdc() watching thoroughly for the ready-for-input bit), since many FDC's tend to lock up if someone requests ``unusual'' things (e.g. SENSEI where no interrupt happened) from them. | Although I'm glad the messages in the fd driver pointed out what was | happening, as far as I can tell ft wasn't really doing anything wrong. | Seems to me fd is reporting a bit too much for a non-debug mode. It should be made less noisy, and will be before 2.1 gets shipped. -- cheers, J"org work: --- no longer --- private: joerg_wunsch@uriah.sax.de Never trust an operating system you don't have sources for. ;-)