Subject: Re: mmap'ing framebuffer memory in MI drivers...
To: None <eeh@netbsd.org>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: tech-kern
Date: 03/06/1999 09:34:28
On Sat, 6 Mar 1999 07:49:26 -0800 (PST) 
 "Eduardo E. Horvath" <eeh@one-o.com> wrote:

 > And it immediately calls pmap_enter() if the mapping would succeed.  There
 > is no instance I can find where if the d_mmap() routine is called and
 > returns a success, pmap_enter is not immediately called.  I see no other
 > calls just to check for permissions.

BZZT :-)

That's the FAULT handler you're looking at.

Now, take a look udv_attach().

 > That would also work.  Probably good to have it called for unmapping
 > (pmap_remove()) so the driver (and bus_space*()) can free up any resources
 > they may have needed to allocate for the mapping.

No, not pmap_remove(), but rather when the device is munmap'd (this is
a different operation).

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>