Ian Romanick wrote:
Holger Waechtler wrote:
Jon Smirl wrote:
Sharing graphics contexts is not the same thing as allowing two
completely
different device drivers access to the hardware on VT swap. Two
different device
drivers may have completely different contents in all of the
registers, CP
On Sul, 2004-05-09 at 14:32, Jon Smirl wrote:
I would like to see a single device drver always controlling the GPU and
VRAM/AGP memory management. Then it is easy to switch graphics contexts on VT
swap.
VRAM/AGP most of the time can probably be a generic library but yes I
agree, and at times
Sharing graphics contexts is not the same thing as allowing two completely
different device drivers access to the hardware on VT swap. Two different device
drivers may have completely different contents in all of the registers, CP
running or not, VRAM and AGP space. With two device drivers you
Alan Cox wrote:
On Iau, 2004-05-06 at 20:57, Jon Smirl wrote:
Simple example, DRM starts GPU coprocessor running. VT swap happens. New user
stops coprocessor. VT swap back to DRM. Now DRM thinks it left the coprocessor
running but that's not true now. DRM and FB conflict when FB is using the
Jon Smirl wrote:
Sharing graphics contexts is not the same thing as allowing two completely
different device drivers access to the hardware on VT swap. Two different device
drivers may have completely different contents in all of the registers, CP
running or not, VRAM and AGP space. With two
Holger Waechtler wrote:
Jon Smirl wrote:
Sharing graphics contexts is not the same thing as allowing two
completely
different device drivers access to the hardware on VT swap. Two
different device
drivers may have completely different contents in all of the
registers, CP
running or not, VRAM
On Sun, May 09, 2004 at 08:14:59PM -0700, Ian Romanick wrote:
| ... I very seriously doubt that you can halt and restart an
| in-progress shader. That would require extra logic, reduce performance,
| and wouldn't help games. What makes you think any of the current cards
| are designed
On Iau, 2004-05-06 at 20:57, Jon Smirl wrote:
Simple example, DRM starts GPU coprocessor running. VT swap happens. New user
stops coprocessor. VT swap back to DRM. Now DRM thinks it left the coprocessor
running but that's not true now. DRM and FB conflict when FB is using the
coprocessor for
Jon Smirl wrote:
--- Jens Owen [EMAIL PROTECTED] wrote:
Six years ago, most devices could not handle this type of restriction
efficiently. Things have improved on the high end; but the low end
devices, are still very similar to what we had back in the day. Even
today, I would be very
On Thu, 6 May 2004, Keith Whitwell wrote:
Jon Smirl wrote:
--- Jens Owen [EMAIL PROTECTED] wrote:
Six years ago, most devices could not handle this type of restriction
efficiently. Things have improved on the high end; but the low end
devices, are still very similar to what we had back
--- Vladimir Dergachev [EMAIL PROTECTED] wrote:
As far as acceleration - either 2d or 3d - it makes sense for it to stay
in userspace.
X and everything else needs to stop mapping the registers to user space and
instead start using an IOCTL interface to a driver. The problem is that X or
11 matches
Mail list logo