From owner-freebsd-questions@FreeBSD.ORG Fri Jul 30 05:26:41 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDC8E106566C for ; Fri, 30 Jul 2010 05:26:41 +0000 (UTC) (envelope-from steven@too1337.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 819A48FC24 for ; Fri, 30 Jul 2010 05:26:41 +0000 (UTC) Received: by ywf9 with SMTP id 9so557925ywf.13 for ; Thu, 29 Jul 2010 22:26:40 -0700 (PDT) Received: by 10.101.154.30 with SMTP id g30mr1400437ano.256.1280466084419; Thu, 29 Jul 2010 22:01:24 -0700 (PDT) Received: from thinkpad.susnet (ip68-99-10-223.om.om.cox.net [68.99.10.223]) by mx.google.com with ESMTPS id x33sm2388180ana.13.2010.07.29.22.01.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 29 Jul 2010 22:01:23 -0700 (PDT) Message-ID: <4C525C90.9000003@too1337.com> Date: Fri, 30 Jul 2010 00:01:04 -0500 From: Steven Susbauer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.11) Gecko/20100729 Thunderbird/3.0.6 MIME-Version: 1.0 To: freebsd-questions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: EforeZZ Subject: Re: Firewire RAM access X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2010 05:26:41 -0000 On 07/27/10 07:38, EforeZZ wrote: > Hi, > > I was playing around with fwcontrol and its "-m" switch. > I connected my FreeBSD 7.2 notebook to Win7 PC Via firewire and > attempted to access Win7's RAM through the /dev/fwmem interface. I > failed. > > The question is.. Should this always work? As far as I know I should > be able to access other PC's RAM through the firewire connection > without any support from the connected PC's OS, right? > > Best regards, > EforeZZ According to this page for the Linux mem1394 driver, the host can set up a filter to block it, and Windows appears to do so (http://johannes.sipsolutions.net/Projects/mem1394). -Steve