>
> I added some transition code for getting rid of
> inter_module_get("agp"); I need to get a small kernel patch in place
> for it to switch to get_symbol("drm_agp_entry"). The code in CVS will
> work both ways.
>
CC [M] /storage/dri/drm/linux-core/drm_drv.o
/storage/dri/drm/linux-core/drm_drv.
A recent DRM checkin "Bring in patch from kernel for remap_pfn_range" only
workes if your 2.6 kernel has remap_pfn_range, unlike Debain's 2.6.8-1-k7.
___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
-
I figured out how to change the drm_debug to just debug and not cause
symbol conflicts.
insmod ./drm.ko debug=1
insmod ./radeom.ko
You can do this in sysfs now and it works
echo "1" /sys/module/drm/debug
echo "0" /sys/module/drm/debug
I added some transition code for getting rid of
inter_module_
On Thu, Oct 21, 2004 at 11:49:20PM +0200, Dieter Nützel wrote:
> Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
> > Hi,
> >
> > There is disagreement about the meaning of the CLIPSPAN _n parameter in
> > CVS.
> >
> > The drivers I have looked at and drivers/dri/common/spantmp.h treat _
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=1388
[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=960
--- Additional Comments From [EMAIL PROTECTED] 2004-10-22 16:21 ---
A long time
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=960
--- Additional Comments From [EMAIL PROTECTED] 2004-10-22 15:24 ---
Yes, this is
I had a dri failure-to-load with Radeon in a 64 bit Opteron system
(fedora core 2). Card is a Radeon RV250 (9000). (I did not find it in
drm_pciids.txt -- pci id 0x1002 0x496e -- but that's a separate issue)
The symptoms were kernel messages on modprobe:
radeon: Ignoring new-style parameters in
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=960
--- Additional Comments From [EMAIL PROTECTED] 2004-10-22 11:48 ---
But Roland's
I've been trying to get large point sizes and ARB_point_parameters to
work on the r200. I was only somewhat succesful, but at least that's a
start...
Maybe someone has some ideas how to get it to work completely.
What works and what doesn't:
- I could not get the point primitive of the r200 to re
As of today, after installing yesterday's binary snapshot
from fd.o instead of CVS, I'm happy to report the bug is gone.
Actually, I thought I had updated everything that needed
to be, but I had forgotten to copy the 2D (ati_drv.o, radeon.o)
driver when I updated the dri (r200_dri.so) driver.
Tha
Am Freitag, 22. Oktober 2004 02:38 schrieb khaqq:
> Hello,
>
> After realizing that the R200 driver bundled with xorg 6.8 wasn't
> stable, I installed the CVS of DRI (as of 2 hours ago).
A little more precise system specs, please.
OK, below ;-)
> The problem *was* :
> random lockups / freezes whe
On Fri, 22 Oct 2004, khaqq wrote:
> Hello,
>
> After realizing that the R200 driver bundled with xorg 6.8 wasn't
> stable, I installed the CVS of DRI (as of 2 hours ago).
> The problem *was* :
> random lockups / freezes when playing UT (original one) or
> Q3A (latest patch) ; those lockups happen
Ian Romanick wrote:
Dieter Nützel wrote:
Am Freitag, 15. Oktober 2004 22:51 schrieb Nicolai Haehnle:
There is disagreement about the meaning of the CLIPSPAN _n parameter in
CVS.
The drivers I have looked at and drivers/dri/common/spantmp.h treat
_n as
the number of pixels in the span after clippin
14 matches
Mail list logo
