From owner-cvs-all Mon Oct 12 12:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19065 for cvs-all-outgoing; Mon, 12 Oct 1998 12:25:21 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19035; Mon, 12 Oct 1998 12:25:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA26149; Mon, 12 Oct 1998 13:24:53 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810121924.NAA26149@panzer.plutotech.com> Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c In-Reply-To: <199810121915.MAA07560@dingo.cdrom.com> from Mike Smith at "Oct 12, 98 12:15:49 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 12 Oct 1998 13:24:53 -0600 (MDT) Cc: mjacob@feral.com, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Mike Smith wrote... > > We're going to put in a mechanism in the next day or two to allow > > specifying SCSI revision in quirk entries. This will allow us to disable > > cache sync, multi-lun probing and serial number inquiries for SCSI-1 > > devices. > > Hmm. Would you consider adding a facility to parse a text-format quirk > description and add it to the compiled-in tables (if unique?). Yes, I'll certainly think about doing it. It would probably be best to do it via camcontrol. It'll require mallocing memory in the kernel to store the additional quirk entries, and therefore could be abused by a malicious hacker. But then again, it would be much easier to just send a nice format unit command..:) Another difficulty will be handling the fact that we've got a number of quirk tables, not one master quirk table like the old code. This will probably require some thought/design to implement. This won't happen before 3.0. > If you were to do this, it would be possible to read quirk entries from > a file during the boot phase, decoupling the quirk data from the kernel > code. (This would eg. make it possible to boot/install on a system > which wouldn't run without a quirk entry.) Hmm, how early in the boot phase? The earlier in the boot phase it goes, the more difficult it would be to do. If you're talking about from /etc/rc, then sure, it could be done via camcontrol or something similar. Doing it before the CAM probe phase would be much more difficult. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message