Thread (101 messages) 101 messages, 14 authors, 2005-03-17

Re: [Linux-fbdev-devel] Re: radeon, apertures & memory mapping

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2005-03-14 21:54:35

On Mon, 2005-03-14 at 17:30 +0100, Soeren Sandmann wrote:
Benjamin Herrenschmidt [off-list ref] writes:
quoted
In an ideal world ... However, since we are planning to move the memory
manager to the kernel, that would mean a kernel access (syscall, ioctl,
whatever...) twice per access to AGP memory. Not realistic.
Could the user space driver batch many such accesses together and use
a lock_many()/unlock_many() API?
We may have to use a lock/unlock API anyway due to interaction with the
VGA arbiter in fact. If for some reason, the card can't completely
disable decoding of VGA and IO space, it needs to bracket any access to
the framebuffer with something.

That is unuseable for things like MOL though. We are giving the
framebuffer to some foreign OS in an emulation shell that doesn't know
how to do but blit directly at any time. Oh well, I need to think a bit
more about those sceniario.

Ben.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help