From owner-freebsd-hackers Wed Apr 5 01:18:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA11059 for hackers-outgoing; Wed, 5 Apr 1995 01:18:46 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA11051 for ; Wed, 5 Apr 1995 01:18:42 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id AAA10030; Wed, 5 Apr 1995 00:14:55 -0700 From: "Rodney W. Grimes" Message-Id: <199504050714.AAA10030@gndrsh.aac.dev.com> Subject: Re: Colorado Jumbo 250MB ft, and FreeBSD 2.0R To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 5 Apr 1995 00:14:55 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: <199504050700.JAA04588@uriah.heep.sax.de> from "J Wunsch" at Apr 5, 95 09:00:05 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1787 Sender: hackers-owner@FreeBSD.org Precedence: bulk > > As Rodney W. Grimes wrote: > > > > > I submitted a patch some time ago but nobody committed it. ... > > > > I have tested the patch here, and it is sitting in my tree ready for commit, > > I am waiting on Joerg Wunsch to finish his review of it (since I only > > had a drive to test with for a short time, and only one model of drive > > I felt it best to get a second review before commiting). > > Sorry for not getting back on this... My old test machine crashed by > the weekend. > > Unfortunately, it looks that my old (& cheap) Insight tape drive is > disfunctional. So all i could do is to have a look at the patch (and > it looks ok), without being able to actually test it with a floppy > tape drive. > > Rod, go and commit it. I hope there are some other people with ft > drives around who can finally test them, perhaps with the next snap > release. Okay, unless some one steps forward as an alternate ft driver change tester by tomarrow I will commit what I have to the tree. It has been tested on the Colorado 250 only, the changes are rather small so I can send anyone who would be willing to test this a patch. > > > The fix within ft to avoid the messages works, but the correct way to > > > remove them is to get them out of the fd driver in the first place. ... > > > > Some one from the fdc driver camp care to comment about this? > > It's the topmost entry in my TODO list. I'm just sitting and wait for > Rod to commit his changes. This commit will be done one way or the other by 23:59 PST Apr 5th. > I promise 2.1 will not complain too much about ``ready for output in > input''... :) :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD