From owner-freebsd-current Mon Feb 11 18:29:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 7DD8F37B48C; Mon, 11 Feb 2002 18:17:05 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id BAAB423185; Mon, 11 Feb 2002 21:16:48 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 043E29F29C; Mon, 11 Feb 2002 21:11:53 -0500 (EST) Date: Tue, 05 Feb 2002 12:49:06 -0600 From: Jordan Breeding To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Support for atapi cdrw as scsi in -current? Message-Id: <20020212021153.043E29F29C@okeeffe.bestweb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garrett Wollman wrote: > < > >>I noticed a patch on freebsd-scsi a while back that >>added a not very complete form of atapi as scsi support >>to the freebsd kernel. Are there plans to complete >>this and add it to -current sometime before -current >>turns into 5.0-RELEASE? Thanks for any information. >> > > I've been using it somewhat actively in the past week or so in > -current. The patch as it exists needs a few changes to fit in > current -current. > > $ camcontrol devlist > at scbus0 target 0 lun 0 (cd0,pass0) > at scbus0 target 1 lun 0 (cd1,pass1) > > I don't think that ATAPICAM works well enough to use it entirely in > place of the atapi-cd driver; for example, I get the following errors: > > atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 > atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > > However, it works well-enough to run cdrdao, which is what mattered to > me, for both reading and writing on both of the afore-mentioned ATAPI > devices. > > -GAWollman > > > Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message