I think this discussion is really interesting cause it discuss about the
biggest problem the DRI project has to deal with: compatibility.
The ideas Ian suggested here may fix the problem, but may also create a
big confusion in the driver code. I'm just thinking about what will
happened after mul
he DRI
patching rules (that I didn't know, of course). But now, I'm not sure I
have time to do it, so maybe somebody else?
Karl
On Thu, 2002-01-24 at 01:17, Keith Whitwell wrote:
> Lawrence Gold wrote:
> >
> > Hi,
> >
> > Back in June 2001, Karl Lessar
Is there a lot of people experiencing problems getting this patch
running correctly? As I said, the patch needs to be applied on a fresh
install of XFree86 4.1.0 and disabledEXTCompiledVertexArray should be
set to "1" in the ClientPrefs file for Tribes2 players.
It is important to make this cl
There is a AGP-to-PCI bridge on a G450 PCI. The thing is that you have a
AGP chip on your PCI card , and the bridge is used to connect the chip
on a PCI bus. But I don't know why DRI only supports AGP cards, need to
investigate a little bit more. Did anyone have any cue on this?
Karl
MacGy
You're right, mgaConvertTexture needs to handle RGB5_A1 as a special
case. But there is no need to redefined MGAPACKCOLOR1555, check
MGAPACKCOLOR555.
So this is the patch to apply over the other one.
Thanks Ralf,
Karl
ralf willenbacher wrote:
>Karl Lessard wrote:
>
>
Andreas Ehliar wrote:
>I'm looking through mga_storm.c and found something which might be a bug.
>In the DRI initialization, pMGADRIServer->textureSize is determined
>by using pMga->FbMapSize.
>Is this correct?
>Shouldn't it be pMga->FbUsableSize instead, since at least the HW cursor is
>located
Andy Isaacson wrote:
>On Wed, Jun 13, 2001 at 12:17:34PM -0400, Karl Lessard wrote:
>
>>Hi everybody,
>>
>>this patch fixes some problems in texturing in the mga driver.
>>
>>1) It fixes a texture corruption problem, as the mga driver did not use
>
Hi everybody,
this patch fixes some problems in texturing in the mga driver.
1) It fixes a texture corruption problem, as the mga driver did not use
the right texture format in some case
( I've seen that when an application wants to store a texture in
RGB5_A1, but it is actually stored i
Well, that's really interesting, and would be a huge step for the Linux
driver. I think that a big issue of implementing this feature will be
the synchronisation between the two heads. As the two screens will use
two diferrent contexts for their 3D drawing, what would happened if a
applicatio
Are you using the HALlib? It takes care of a lot of synchronisation
issues after the dac initialisation in those 2 files. About the options,
I've never seen that in our driver. What it supposed to do?
Karl
Stephen Davies wrote:
>Hi,
>
>Does the mga driver support the -HSync -VSync options?
[EMAIL PROTECTED] wrote:
>Can I compile the files in a driver directory alone, without having to do
>the whole DRI or X11 tree ? Then grab the driver_dri.so file and throw
>it in the modules directory and restart X11 for it to take effect ?
>
>This assumes that the only changes are within
time ago. The contract covered a specific set of features over
> a specific time period. Contracts like that don't go on forever (as
> some people seem to think).
>
> Karl Lessard <[EMAIL PROTECTED]> from Matrox seems to be their new
> in-house
We've saw this problem too when running Gears on XFree 4.0.3. The thing
is that a lot of work has been done to the mga driver that fixes all
those problems related to hardware lock ups, but it only has been
included for the next release of XFree86, i.e. 4.1.0, a preview for this
summer. If yo
s sort of thing to help get
> me off to a good start I would love to use them and learn. I'm eager
> to get my feet wet, though I can't promise I'll deliver due to being
> a novice in this particular area. I appreciate any help that can be
> sent my way.
>
> A
A lot of bugs has been fixed since XFree86 4.0.3, that gonna be included
in next generation of XFree86 (4.1.0 and so on). I don't know which
version of XFree you are using, but if it's <= 4.0.3, downloading and
installing the current head of the XFree86/DRI CVS may fix your problems.
-Karl
B
Jeff Hartmann wrote:
> Fred Black wrote:
>
>> Hello everyone,
>>
>> I've been reading about how drm works and going through some code.
>> To understand the whole thing I'm trying a couple of stuff. But I
>> now need some help.
>>
>> I'm trying to find a way for sending some intructions t
Hi,
Starting gears under XFree86 4.0.3-3 with DRI enabled freeze my system.
It seems to happened when the app needs to render back its content from
a passive state (as a example, when I drag another window to entirely
cover it, and move it back to see the gears). I'm using a G400, but it
happ
17 matches
Mail list logo
