From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 14:41:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ADCC16A4CE; Wed, 21 Jul 2004 14:41:29 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 136E543D5A; Wed, 21 Jul 2004 14:41:29 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i6LEfSR0018374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jul 2004 10:41:28 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i6LEfMlQ046520; Wed, 21 Jul 2004 10:41:22 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16638.32914.509773.486468@grasshopper.cs.duke.edu> Date: Wed, 21 Jul 2004 10:41:22 -0400 (EDT) To: Doug Rabson In-Reply-To: <200407182104.53221.dfr@nlsystems.com> References: <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: simokawa@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire support! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 21 Jul 2004 14:41:29 -0000 Doug Rabson writes: > Actually thats the only downside of dcons. It doesn't cut in until the > firewire controller attaches. It relies on the fact that the fwohci > driver allows access to physical memory from any node on the bus > (implemeted in hardware so you can examine the memory of a hung > machine). The dconschat program uses this feature to access the dcons > ring buffers in the target machine. Does remote access to physical memory require dcons to be loaded on the target? If no, assuming I had a Windows or Linux box on the firewire bus, would it be possible to access physical memory from a different OS? Thanks, Drew