Hi,
Wanted to report that without this patch my ATI Radeon IGP 345M
didn't have direct rendering support with yesterday mesa-cvs and
dri-cvs. After applying patch I have dri support :) Hope this patch will
be included in cvs soon... it's great ;)
Lafriks
p.s. patch by Jon Smirl:
=
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=969
[EMAIL PROTECTED] changed:
What|Removed |Added
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=969
--- Additional Comments From [EMAIL PROTECTED] 2004-08-26 03:40 ---
What
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=969
--- Additional Comments From [EMAIL PROTECTED] 2004-08-26 04:01 ---
root # ls
Hi, Erdi.
Thomas Hellström wrote:
I just noticed that you are using a 2d BITBLT to temporarily stall the
command regulator for a moment.
I believe the XAA implementation in all current via 2d X server drivers
out there assume that they are reasonably alone in using the 2d engine
and
that
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=969
--- Additional Comments From [EMAIL PROTECTED] 2004-08-26 05:55 ---
I set it to
I haven't checked xorg cvs, but this patch may be needed there as well.
-- Forwarded message --
From: Lafriks [EMAIL PROTECTED]
Date: Thu, 26 Aug 2004 11:54:50 +0300
Subject: drm patch
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Hi,
Wanted to report that without this patch
Here is the current version of the patch. As soon as Dave approves it
will go in.
The problem was a conflict between VesaFB and DRM. The patch detects
VesaFB and puts DRM in stealth mode.
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
New
Also had a guy at the unichrome lists that reported a kernel panic within
the via modules on a 2.4.20 kernel. I have checked on 2.6.3, and it seems
OK. Have you checked 2.4?
I just checked with 2.4.27 and it all seems OK. I will update the
Unichrome project's
DDX to initialize the ring buffer
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1195
Summary: (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.
Hi,
I've enabled color tiling on the radeon. However, since you have to put
the crtc in tiling mode to compensate the effect, this can only be used
in fullscreen (or you're screwing everything around the 3D window).
Thus my question : how can I reliably detect fullscreen operation from
the
Looks good to me please feel free to commit to CVS, myself and the lk are
an impasse but I'll try and break it over the weekend :-)
Dave.
On Thu, 26 Aug 2004, Jon Smirl wrote:
Here is the current version of the patch. As soon as Dave approves it
will go in.
The problem was a conflict
Alex Deucher wrote:
On Fri, 27 Aug 2004 01:01:23 +0200, Stephane Marchesin
[EMAIL PROTECTED] wrote:
Hi,
I've enabled color tiling on the radeon. However, since you have to put
the crtc in tiling mode to compensate the effect, this can only be used
in fullscreen (or you're screwing everything
On Fri, 27 Aug 2004 01:24:18 +0200, Stephane Marchesin
[EMAIL PROTECTED] wrote:
Alex Deucher wrote:
On Fri, 27 Aug 2004 01:01:23 +0200, Stephane Marchesin
[EMAIL PROTECTED] wrote:
Hi,
I've enabled color tiling on the radeon. However, since you have to put
the crtc in tiling mode to
This is a code snippet that reg_pause_addr:
VGAOUT8(0x3c4, 0x38);
device_id = VGAIN8(0x3c5) 8;
VGAOUT8(0x3c4, 0x37);
device_id |= VGAIN8(0x3c5);
switch (device_id) {
case PCI_CHIP_CLE3122:
case PCI_CHIP_CLE3022:
pVia-Chipset = VIA_CLE266;
15 matches
Mail list logo
