From owner-freebsd-multimedia  Fri Mar 21 16:04:11 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA24657
          for multimedia-outgoing; Fri, 21 Mar 1997 16:04:11 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24648
          for <multimedia@freebsd.org>; Fri, 21 Mar 1997 16:04:06 -0800 (PST)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id QAA03210; Fri, 21 Mar 1997 16:04:00 -0800 (PST)
Message-Id: <199703220004.QAA03210@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Anthony.Kimball@East.Sun.COM
cc: smp@csn.net, multimedia@freebsd.org
Subject: Re: Continquous Memory vs Virtual Memory 
In-reply-to: Your message of "Fri, 21 Mar 1997 17:04:27 CST."
             <199703212304.RAA27833@compound.east.sun.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 21 Mar 1997 16:04:00 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>From The Desk Of Tony Kimball :
> Quoth Steve Passe on Fri, 21 March:
> : [kernel memory protection violation of RISC engine programs 
> :  implies need for kernel-level compiler]
> 
> Are there any applications which care?  If there are none, your
> concerns are excessively zealous.  
> 
> 
Hi Tony, 

The answer is yes. We have applications which can load up into the
driver any old memory address which they want. For instance, 
dtv passes to the driver the physical address of the frame buffer.
Programs like dtv do PCI to PCI data transfer or in a case of 
a hacker exploit it can do PCI to kernel address space.

	Regards,
	Amancio