Date: Thu, 19 Jun 1997 22:30:02 -0700 (PDT) From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-bugs Subject: Re: kern/3909: Patches - new worm drivers for CDrom burners: Philips CDD522 and T.Yuden EW-50 Message-ID: <199706200530.WAA12160@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/3909; it has been noted by GNATS.
From: j@uriah.heep.sax.de (J Wunsch)
To: mmcg@mjolnir.cs.monash.edu.au
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/3909: Patches - new worm drivers for CDrom burners: Philips CDD522 and T.Yuden EW-50
Date: Fri, 20 Jun 1997 07:09:31 +0200
As Mike McGaughey wrote:
> Here is a modification to the 2.2.2-RELEASE worm.c which implements
> support for the Philips CDD 522 and T.Yuden EW-50 (very cheap in
> Australia).
Thanks!
> NOTE: I have made a slight change to the handling of other CDrom
> cutters. In particular, the spindown/medium unload commands are
> now sent *after* the cache flush when finalizing a track.
You ought to have a look at the current driver... Jean-Marc has
already fixed this (and improved many other things).
> I have burned a bunch of data CDs using this; I haven't tried
> audios, multi-track, or multi-session disks (the multisession
> support looks broken anyway, due to a block addressing issue).
Multisession works fine for me (one of my test CDs bailed out with
`volume overflow' at 29 sessions :); the block addressing problem can
be reduced to read operations, but with the current overall kernel
struct (namely the b_blkno handling), it cannot be fixed at all. For
writing, you should always set the block number to 0.
> + {
> + "PHILIPS", "CDD522",
> + cdd522_prepare_disk, cdd522_prepare_track,
> + cdd522_finalize_track, cdd522_finalize_disk
> + },
> + {
> + /* (aic0:4:0): "T.YUDEN CD-WO EW-50 2.16" type 4 removable SCSI 2 */
> + "T.YUDEN", "EW-50",
> + cdd522_prepare_disk, cdd522_prepare_track,
> + cdd522_finalize_track, cdd522_finalize_disk
> + },
These things have been moved out to scsiconfig.c. I assume you had to
modify scsiconfig.c anyway, in order to make the device known as a
CD-R, did you? At any rate, please tell us where the `CD-WO' string
belongs to in the inquiry data. I.e., is the required entry for
scsiconfig { "T.YUDEN CD-WO", "EW-50", ...} or { "T.YUDEN", "CD-WO
EW-50", ... }?
> + /*
> + * Philips CDD522/Taiyo Yuden EW-50 section.
> + *
> + * Ack: I am very grateful to Philips, who supplied me with a SCSI manual
> + * for their unit. Taiyo Yuden considers their manual proprietry.
> + *
> + * This section was written using the CDD522 SCSI manual, but has only
> + * been tested on my T.YUDEN EW-50 (it's a long story).
> + */
What's the difference to the existing HP4020/HP6020/CDD2000/CDD2660
option? From a cursory look, i didn't see any. There's not much use
to duplicate code.
I suspect you could have been successfully using the old code, too, by
pretending it to be an HP 4020i?
--
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?199706200530.WAA12160>