Leif Delgass wrote:
> Jens,
>
> This works after fixing one thing in this section from DRICloseScreen:
>
> if (pDRIPriv->wrap.AdjustFrame) {
> - ScrnInfoPtr pScrn = xf86Screens[pScreen->myNum];
> - pScrn->AdjustFrame = pDRIPriv->wrap.AdjustFrame;
> -
Jens,
This works after fixing one thing in this section from DRICloseScreen:
if (pDRIPriv->wrap.AdjustFrame) {
- ScrnInfoPtr pScrn = xf86Screens[pScreen->myNum];
- pScrn->AdjustFrame = pDRIPriv->wrap.AdjustFrame;
- pDRIPriv->wrap.AdjustFrame
Leif Delgass wrote:
>>> On Fri, 5 Jul 2002, Jens Owen wrote:
Okay, try the attached patch. I think I'll do more than this, but it
would be great if you could test just this, first.
Okay, I have attached a more robust patch. Can you try this on your branch?
>
> I'll apply this to t
On Fri, 5 Jul 2002, Jens Owen wrote:
> Leif Delgass wrote:
>
> > The backtrace from the static server was the same. BTW, this might help
> > others trying to debug with a dynamic server: I removed 'Load "GLcore"'
> > from my XF86Config, because I saw that it was being reloaded by the glx
> > m
Leif Delgass wrote:
> On Fri, 5 Jul 2002, Jens Owen wrote:
>
> [...]
>
The xc/config/cf/host.def in the DRI tree is setup to easily modified to
build a debuggable server. Attached is a copy of a modified host.def
file I used for debugging an i810 problem. You'll probably need to
On Fri, 5 Jul 2002, Jens Owen wrote:
[...]
> >>The xc/config/cf/host.def in the DRI tree is setup to easily modified to
> >>build a debuggable server. Attached is a copy of a modified host.def
> >>file I used for debugging an i810 problem. You'll probably need to add
> >>the mach64 driver to
Leif Delgass wrote:
> On Fri, 5 Jul 2002, Jens Owen wrote:
>
>
>>Leif Delgass wrote:
>>
>>
>>>On Fri, 5 Jul 2002, Jens Owen wrote:
>>>
>>>[snip]
>>>
>>>
>>>
However, I think you may be tickling a latent bug in the DRI. It's
possible that all the other drives have just avoided this bug
On Fri, 5 Jul 2002, Jens Owen wrote:
> Leif Delgass wrote:
>
> > On Fri, 5 Jul 2002, Jens Owen wrote:
> >
> > [snip]
> >
> >
> >>However, I think you may be tickling a latent bug in the DRI. It's
> >>possible that all the other drives have just avoided this bug so far.
> >>
> >>I looked at
Leif Delgass wrote:
> On Fri, 5 Jul 2002, Jens Owen wrote:
>
> [snip]
>
>
>>However, I think you may be tickling a latent bug in the DRI. It's
>>possible that all the other drives have just avoided this bug so far.
>>
>>I looked at DRICloseScreen and I don't see that the DRIClipNotify
>>wra
On Fri, 5 Jul 2002, Jens Owen wrote:
[snip]
> However, I think you may be tickling a latent bug in the DRI. It's
> possible that all the other drives have just avoided this bug so far.
>
> I looked at DRICloseScreen and I don't see that the DRIClipNotify
> wrapper is being removed. There ar
Leif Delgass wrote:
> After merging the trunk into the mach64 branch, I get a segfault in the
> Xserver in DRIClipNotify (dereferences a null pointer when trying to call
> a wrapper function, I think) if direct rendering is disabled after
> DRIFinishScreenInit is called, e.g. if the init of the d
11 matches
Mail list logo
