From owner-freebsd-current Mon Aug 21 23:47:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E823A37B42C for ; Mon, 21 Aug 2000 23:47:53 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA57404; Tue, 22 Aug 2000 00:47:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA02074; Tue, 22 Aug 2000 00:47:42 -0600 (MDT) Message-Id: <200008220647.AAA02074@harmony.village.org> To: Mike Meyer Subject: Re: Why no CDR ioctls for SCSI cds? Cc: "Kenneth D. Merry" , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 22 Aug 2000 01:39:57 CDT." <14754.8253.80322.822607@guru.mired.org> References: <14754.8253.80322.822607@guru.mired.org> <14753.62883.183839.508028@guru.mired.org> <14753.20681.165961.352066@guru.mired.org> <20000821104114.A67935@panzer.kdm.org> <14753.42672.286077.409965@guru.mired.org> <20000821163458.A70871@panzer.kdm.org> <14753.47379.141329.994631@guru.mired.org> <20000821175657.A71753@panzer.kdm.org> <14753.50849.16035.805395@guru.mired.org> <20000821212517.B73232@panzer.kdm.org> <200008220607.AAA01652@harmony.village.org> Date: Tue, 22 Aug 2000 00:47:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14754.8253.80322.822607@guru.mired.org> Mike Meyer writes: : You may well be right, and there are good technical reasons for not : doing this. The only real reason that's been presented for not doing : MMC is that all the non-MMC drives might cause a support : headache. There are sound technical reasons for *not* doing non-MMC : drives, and Ken and I agree on that. Actually, the real reason is that MMC drives that mostly support the standard, but do it wrong in ways that are hard to detect. Those are going to be the worst to try to support. There are some drives out there that just hang when you issue them certain MMC commands, as an example. They shouldn't but they do and you have to be careful not to send them these commands. : If the answer from the person who would have to approve the code had : come back "Ok, provide the code and we'll see how well it works in : practice", I'd do the code. But when it appears the code would never : make it into the tree to be used, why waste my time? I think that you overstate ken's reluctance. If you can come up with a good way to deal with this and have a good error mechanism for those drives that don't support this then I think he might (and I repeat might) be talked into it. I've found Ken quite accepting of code in the past when I've gone to the trouble of doing something. I've found in the past that working code has a way of making people reconsider their opinions of things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message