From owner-cvs-all@FreeBSD.ORG Wed Mar 26 08:17:21 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B8537B404; Wed, 26 Mar 2003 08:17:21 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F7AD43F93; Wed, 26 Mar 2003 08:17:20 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h2QGHIA7087907; Wed, 26 Mar 2003 09:17:19 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 26 Mar 2003 09:15:51 -0700 (MST) Message-Id: <20030326.091551.56531668.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <1618.1048687116@critter.freebsd.dk> References: <20030325.233035.105508479.imp@bsdimp.com> <1618.1048687116@critter.freebsd.dk> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-9.9 required=5.0 tests=AWL,IN_REP_TO,REFERENCES version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/usb umass.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 16:17:25 -0000 : As far as I know we don't even mount the cdrom as the root filesystem, : but rather run on a preloaded MD disk ? We do if you use a live filesystem disk to recover from something nasty. Also, the problem would be that many of the quirks need to be known when the device is detected or the system completely hangs. You'd have to disconnect the cdrom at exactly the right time during the boot process in the installation case. It is too late to load the quirks from userland. I'm not saying that we can't have some way to load additional quirks, but there's a core set of them that say "This device is hozed in this way and we need to know that before we start touching it." pccard and cardbus cards have similar issues, but fewer quirks at the moment (more are needed for problem child cards that I have). Warner