From owner-p4-projects@FreeBSD.ORG Sat Oct 4 12:16:43 2003 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 6551B16A4C0; Sat, 4 Oct 2003 12:16:43 -0700 (PDT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AFE416A4B3 for ; Sat, 4 Oct 2003 12:16:43 -0700 (PDT) Received: from perrin.nxad.com (internal.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0B4043F85 for ; Sat, 4 Oct 2003 12:16:42 -0700 (PDT) (envelope-from hmp@nxad.com) Received: by perrin.nxad.com (Postfix, from userid 1072) id C62E421064; Sat, 4 Oct 2003 12:16:41 -0700 (PDT) Date: Sat, 4 Oct 2003 12:16:41 -0700 From: Hiten Pandya To: "M. Warner Losh" Message-ID: <20031004191641.GA27319@perrin.nxad.com> References: <20031001142349.A87379@FreeBSD.org> <20031001.164315.11988972.imp@bsdimp.com> <20031002022135.GA26666@perrin.nxad.com> <20031003.000052.96921421.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031003.000052.96921421.imp@bsdimp.com> X-Operating-System: FreeBSD FreeBSD 4.7-STABLE User-Agent: Mutt/1.5.4i cc: perforce@freebsd.org cc: julian@elischer.org Subject: Re: PERFORCE change 38917 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Oct 2003 19:16:43 -0000 On Fri, Oct 03, 2003 at 12:00:52AM -0600, M. Warner Losh wrote: : In message: <20031002022135.GA26666@perrin.nxad.com> : Hiten Pandya writes: : : Does this also include PCI Hotplugging or is this going to be : : a separate effort? : : Yes and no. : : We already have removable devices in the tree. CardBus, PC Card, USB : and Firewire. Right now the drivers take liberties and chances and : there are a number of ugly races that rear their ugly heads. This is : an effort to clean that up and make things totally safe in all the : cases that we can think of, and to document those areas where we : can't. : : There's no specific plans on my part to implement the hot plug state : transition and deal with it. People have raised their hands in the : past to work on it, but so far no one has made significant progress in : public view. Hmm, I see your point of view. Also, another problem with PCI Hotplug controllers is that most of them are proprietary, like for example, the IBM controllers. Regards, -- Hiten Pandya hmp@backplane.com