Date: Mon, 19 Aug 1996 08:33:04 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: xmcd@bazooka.amb.org Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: XMCD problem on FreeBSD 2.1.5 Message-ID: <199608190633.IAA11467@uriah.heep.sax.de> In-Reply-To: <9608182136.AA11587@bazooka.amb.org> from Xmcd Admin at "Aug 18, 96 02:36:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Xmcd Admin wrote: > > I consider using direct SCSI commands the most ugly method to use, > > though of course, for many operating systems it's your only chance. > > That is a matter of opinion... :-) > 2. It allows me to support SCSI-1 and other CD-ROM drives that > implement non-standard command sets. Nothing prevents the operating systems to do the same. We have to implement drive-dependant features anyway, since we intend to enable reading CD-DA in the kernel some day. > Without the use of direct SCSI-passthrough, xmcd would not be > able to provide full support of such a wide array of CD-ROM drives. Well, OTOH, it also limits your list of features to SCSI only, while you obviously can't support things like the really popular ATAPI devices (which are basically SCSI drives, thus offer the same features internally). Of course, i realize that xmcd supports 22 operating systems, and believe me, i know that this is a hard piece of work. Anyway, i'm from the 22nd supported system :), and now that we've already got the ioctl, i'm more eager to make the kernel interface abstracting the hardware for you. This is the technically cleaner solution. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608190633.IAA11467>