Date: Tue, 29 Aug 1995 17:18:43 -0500 From: Jon Loeliger <jdl@chrome.onramp.net> To: Bruce Evans <bde@zeta.org.au> Cc: vak@cronyx.ru, hackers@freebsd.org Subject: Re: wd0 detect fails Message-ID: <199508292218.RAA06678@chrome.onramp.net> In-Reply-To: Your message of "Wed, 30 Aug 1995 06:51:12 %2B1000." <199508292051.GAA00059@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Apparently, Bruce Evans scribbled: > [ code ] > > >I'm not sure that this code is 100% correct. > >Old version did not work for some CD-ROMs, > >current one seems to fail for some disks. :-( > > >Unfortunately, ATA specs cannot help much here, > >just as ATAPI specs cannot help in CD-ROM probing. > >Manufacturers never read specifications. :-) > > A user reported that the status was 0x52 for the old code (0x02 = IDX). > The spec says 0x50 :-). > > We could ignore some bits, perhaps all except 0x51, but the old code > essentially ignored all except 0x50 (and BUSY). Why did it fail exactly? With minor cable finagling here, I can easily, :-(, construct a failing probe case. Would you like to go a few rounds with me on this one? I was getting the CDROM detect failure when trying to put the CDROM as the only device of the wdc1 controller. (The wdc0 had either 1 or 2 drives on it.) Is this the failure mode you were interested in? > >If so, what about removing the ATAPI option and enable ATAPI > >support by default? Cool! jdl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508292218.RAA06678>