Date: Wed, 21 Jul 2004 10:41:22 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Doug Rabson <dfr@nlsystems.com> Cc: freebsd-current@freebsd.org Subject: Re: Excellent job on the firewire support! Message-ID: <16638.32914.509773.486468@grasshopper.cs.duke.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16638.32914.509773.486468>