From owner-freebsd-current Mon Aug 21 03:14:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id DAA08816 for current-outgoing; Mon, 21 Aug 1995 03:14:41 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id DAA08807 ; Mon, 21 Aug 1995 03:14:36 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id LAA28054; Mon, 21 Aug 1995 11:13:39 +0100 From: Paul Richards Message-Id: <199508211013.LAA28054@server.netcraft.co.uk> Subject: Re: ATAPI To: sos@freebsd.org Date: Mon, 21 Aug 1995 11:13:39 +0100 (BST) Cc: paul@freebsd.org, vak@cronyx.ru, FreeBSD-current@freebsd.org In-Reply-To: <199508210531.WAA21303@freefall.FreeBSD.org> from "sos@freebsd.org" at Aug 20, 95 10:31:41 pm Reply-to: paul@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1591 Sender: current-owner@freebsd.org Precedence: bulk In reply to sos@freebsd.org who said > > In reply to Paul Richards who wrote: > > > > My IDE cdrom seems to think it's a hard disk. > > > > wdc0 at 0x1f0-0x1f7 irq 14 on isa > > wdc0: unit 0 (wd0): > > wd0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S > > wdc0: unit 1 (wd1): > > wd1: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (atapi): , removable, dma, iordis > > wdc1: ATAPI hard disks not supported > > > > It's not working anyway. It's an NEC CDR-260, claims to be ATAPI rev 1.7B > > compatible. > > Oh well, you have one of the drives that doesn't byteswap its name :) > It probably has other "non-std" things as well, making the driver > fail to see it as a CDROM. This was one of the probelms that effectively > delayed my ata driver, there seems to be no clear way to deal with this > except searching through a table with known stange devices.... :-( Hmm, we're going to have to deal with this in some way. Releasing an IDE cdrom driver to all the masses waiting for one only for them to find it doesn't work with their particular cdrom would be a major PR disaster. I'll try and find the problem with my drive this week. I think we'd better try and find a lot of IDE cdrom owners out there to thoroughly shake out this driver. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)