Subject: Re: mmap'ing framebuffer memory in MI drivers...
To: None <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 03/03/1999 12:02:17
On Wed, 3 Mar 1999 11:57:00 -0800 (PST)
"Eduardo E. Horvath" <firstname.lastname@example.org> wrote:
> > But there's no MI way to do this: some ports use low_order bits as
> > flags, some use high-order bits, and there's not even a standard
> > namespace of MI flags.
> Yes, I noted this when I split vm_offset_t into paddr_t and vaddr_t. One
> solution would be to define a paddr_t with all the extra fields to define
> whether it's cacheable, etc.
AAACK! I _already_, some months ago, posted what the API for this
should look like.
Please search the tech-kern archives for "bus_space_mmap".
-- Jason R. Thorpe <email@example.com>