From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 19:56:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79C25106566B for ; Thu, 19 Feb 2009 19:56:56 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 50E108FC13 for ; Thu, 19 Feb 2009 19:56:56 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id D930D46B2D; Thu, 19 Feb 2009 14:56:55 -0500 (EST) Date: Thu, 19 Feb 2009 19:56:55 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Hans Petter Selasky In-Reply-To: <200902190931.32064.hselasky@c2i.net> Message-ID: References: <499CC89E.2040408@ongs.co.jp> <200902190857.05883.hselasky@c2i.net> <499D1462.6030900@ongs.co.jp> <200902190931.32064.hselasky@c2i.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Daichi GOTO , Masanori OZAWA Subject: Re: USB2: booting from usb memory issue, including a foolish patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 19:56:56 -0000 On Thu, 19 Feb 2009, Hans Petter Selasky wrote: >> I have checked a patch on above URL (freesbie term), it looks like better >> than mine. How about to merge that patch to usb2 stack, HPS? >> >> If someone could add feature that waits all boot deives prove, that's best. >> And adding tuning feature of 16 seconds wait time by /boot/loader.conf, >> it's great. Anyone could do that? > > Could we change "mount", that if we specify some wait flag, it will simply > loop in kernel and userland for a user specified amount of time? I thought run_interrupt_driven_config_hooks(), done at SI_SUB_INT_CONFIG_HOOKS, allowed subsystems such as SCSI to suspend the boot while they finish probing, and root_mount_hold() similarly allowed higher level subsystems such as GEOM modules to delay the root mount while they do their bit. Robert N M Watson Computer Laboratory University of Cambridge