From owner-freebsd-hackers  Tue Dec  2 12:52:59 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id MAA02501
          for hackers-outgoing; Tue, 2 Dec 1997 12:52:59 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from iworks.InterWorks.org (root@iworks.interworks.org [128.255.18.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02441;
          Tue, 2 Dec 1997 12:52:45 -0800 (PST)
          (envelope-from deischen@iworks.interworks.org)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id OAA10631; Tue, 2 Dec 1997 14:24:31 -0600 (CST)
Message-Id: <199712022024.OAA10631@iworks.InterWorks.org>
Date: Tue, 2 Dec 1997 14:24:31 -0600 (CST)
From: "Daniel M. Eischen" <deischen@iworks.interworks.org>
To: sos@FreeBSD.dk
Subject: Re: Fix for slow reacting ATAPI CD-ROM
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Sxren Schmidt wrote:
> > Obviously, this drive isn't detected as a slow device (I
> > can post the boot messages later if needed).  What I wanted
> > to do was to add a config flag for setting this, but it doesn't
> > look like that is sent down to the atapi driver.
> >
> > 
> > Question: Can we change atapi_attach() to accept a 4th argument
> >           and use this to pass config flags from wdattach() in
> >           wd.c?  Is there another method I should be using to
> >           handle atapi device quirks?
>
> Hmm, I think that atapi_attach should be educated on how to treat
> this device, test for model make etc, and then set the slow bit...
> This is the place to do quirks for atapi CDROM device.

I like being able to explicitly set it to aid in new installations.
It kinda sucks not being able to install from CD-ROM.  Or perhaps
this wait count should be set higher in FAILSAFE mode?

Dan Eischen
deischen@iworks.InterWorks.org