Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Apr 1995 05:59:11 -0400 (EDT)
From:      Peter Dufault <dufault@hda.com>
To:        rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes)
Cc:        steve2@freefall.cdrom.com, freebsd-hackers@FreeBSD.org
Subject:   Re: Colorado Jumbo 250MB ft, and FreeBSD 2.0R
Message-ID:  <199504050959.FAA03821@hda.com>
In-Reply-To: <199504050234.TAA09378@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 4, 95 07:34:43 pm

next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes writes:
> 
> > 
> > > The "ready for output in input" errors are par for the course.  Ignore them.
> > > I thought I heard that the current maintainer of the driver was going to
> > > get rid of them by 2.1, but they're still there.
> > 
> > I submitted a patch some time ago but nobody committed it.  There was also
> > a fix in there to keep the motor from being activated during the probe for
> > people who do not have tape drives.  I re-sent this fix to Rod a couple of
> > weeks ago but I'm not sure what he's doing with 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).
> 
> > 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.  In my
> > opinion they should only be debug messages, since it's not as if the user
> > can take some corrective action after seeing them.  It would be nice if
> > someone did this before 2.1 is burned.
> 
> Some one from the fdc driver camp care to comment about this?

I'll say something since I put the warning in (but I think there
is really only one person in the FDC driver camp...).

It was a problem that this warning complained about that caused
the "2.0 boot floppy fails on Micronics motherboard" problem, which
is why I added the warning.  If we take it out it perhaps a similar
problem will creap back in.  At the time I put in the warning I
figured we could eliminate all the problems this indicated.

If I was wrong and this really isn't indicative of a problem in
the driver logic then by all means rip it out.

I don't have a floppy tape and don't get any of these warnings.

-- 
Peter Dufault               Real Time Machine Control and Simulation
HD Associates, Inc.         Voice: 508 433 6936
dufault@hda.com             Fax:   508 433 5267



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504050959.FAA03821>