On Tue, Jul 13, 2004 at 10:39:00AM -0700, Ian Romanick wrote:
Yeah, there's a lot of stuff in the Redhat RPMs that aren't in my patch
yet. I'm trying to take things in small steps to make it easier to find
binary compatability problems as they crop up. The other part of the
problem is
First I built the i830 module from 2.4.24. Then I tried to unload the
current module which was built from dri cvs, the kernel gave me an oops.
See attachment for the decoded oops.
okay there is something wrong with the unload but I can't see it straight
away, can you insmod the i830 from the
Dave Airlie wrote:
First I built the i830 module from 2.4.24. Then I tried to unload the
current module which was built from dri cvs, the kernel gave me an oops.
See attachment for the decoded oops.
okay there is something wrong with the unload but I can't see it straight
away, can you
Dave Airlie wrote:
okay there is something wrong with the unload but I can't see it straight
away, can you insmod the i830 from the snapshot with drm_opts=debug and
then rmmod it and send me the dmesg output I'd like to track that one
down... I'll then make the fix I think is needed to stop
[drm:i830_ctxbitmap_init] drm_ctxbitmap_init : 0
[drm] Initialized i830 1.3.2 20021108 on minor 1: Intel Corp. 82852/855GM Integrated
Graphics Device (#2)
[drm:drm_cleanup]
[drm:i830_takedown]
[drm:i830_stub_unregister] 0
inter_module_unregister: no entry for 'drm'kernel BUG at
Hello all !
I'm using the savage driver for a ProSavage PN133 from the
06 July 2004 snapshot. I have some troubles with the glScissor
function. I don't know if it's a driver problem but the same
code works ok under intel i865G (Extreme 2).
The next code usually sets a painting window.
//
On Wed, 14 Jul 2004 15:54:29 +0200
[EMAIL PROTECTED] wrote:
Hello all !
I'm using the savage driver for a ProSavage PN133 from the
06 July 2004 snapshot. I have some troubles with the glScissor
function. I don't know if it's a driver problem but the same
code works ok under intel i865G
On Iau, 2004-07-15 at 00:19, Felix Khling wrote:
It's not exactly a known problem. I havn't had problems with scissors
yet, probably because it's not widely used in games and other stuff I
tested. I suspect that scissors interact badly with the window cliprect.
It's still a big mess in the
Dave Airlie wrote:
I've checked in a fix for this load/unload it probably won't help your
main situation yet but I'd appreciate if you could check it the module
load and unload, if that works I'll try and fix your specific problem or
at least rule out the DRM.
oops again, seems this
