On May 28, 2005, at 17:50:05, Dave Jones wrote:
On Sat, May 28, 2005 at 11:39:00PM +0200, Geert Uytterhoeven wrote:
config DRM
tristate "Direct Rendering Manager (XFree86 4.1.0 and higher
DRI support)"
-depends on AGP || AGP=n
+depends on (AGP || AGP=n) && PCI
The whole depen
DRM depending on `AGP=n' is driving me crazy! How to make CONFIG_DRM not
eligible for selection on platforms that do not have AGP?
Since many of the core DRM files depend on PCI, add a dependency on PCI,
to minimize the damage.
Signed-off-by: Geert Uytterhoeven <[EMAIL PROTECTED]>
--- linux-2.6
Rune Petersen wrote:
Roland Scheidegger wrote:
Rune Petersen wrote:
Michel Dänzer wrote:
On Fri, 2005-05-27 at 20:48 +0200, Rune Petersen wrote:
Hi,
One more for good messure.
2048x2048 texturer are corrupted. half (1024x2048) is correct, the
rest is random data from memory.
Not be
Morning,
After playing UT2004 for 10 or so minutes, and then quickly checking
some other
apps known to worn, I see no regressions with either patch.
I'll be putting it through some more rigorous testing as the day
progresses, will
report back if I find anything.
Also, out of interest, what
On 5/28/05, Nicolai Haehnle <[EMAIL PROTECTED]> wrote:
> Hi everybody,
>
> I once again tripped upon an R300 lockup (possibly the same one that
> everybody's been talking about) and spent the last one and half days
> chasing it down.
>
> It turns out that writing the vertex buffer age to scratch
On Sat, May 28, 2005 at 11:39:00PM +0200, Geert Uytterhoeven wrote:
>
> DRM depending on `AGP=n' is driving me crazy! How to make CONFIG_DRM not
> eligible for selection on platforms that do not have AGP?
>
> Since many of the core DRM files depend on PCI, add a dependency on PCI,
> to mini
Hi everybody,
I once again tripped upon an R300 lockup (possibly the same one that
everybody's been talking about) and spent the last one and half days
chasing it down.
It turns out that writing the vertex buffer age to scratch registers (the
ones that are written back to main memory) during a
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://bugs.freedesktop.org/show_bug.cgi?id=2673
[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://bugs.freedesktop.org/show_bug.cgi?id=3217
[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://bugs.freedesktop.org/show_bug.cgi?id=3217
[EMAIL PROTECTED] changed:
What|Removed |Added
--
Roland Scheidegger wrote:
Rune Petersen wrote:
Michel Dänzer wrote:
On Fri, 2005-05-27 at 20:48 +0200, Rune Petersen wrote:
Hi,
One more for good messure.
2048x2048 texturer are corrupted. half (1024x2048) is correct, the
rest is random data from memory.
Not being familiar with the r3
On Sat, 2005-05-28 at 20:07 +1000, Nik wrote:
>
> The folks at JOGL indicated the problem could be due to JOGL making
> extensive of threads. Does that sound like a good plasce to start the
> investigation, or would you suggest I just start tracing back from the
> exception?
That's usually a g
Hello,
The stock DRI as found in linux 2.6.11.11 does not
recognize the mobile i915GM chip as found on some
laptops (including my HP nx6110). Adding the following
PCI_ID of 0x2592 to drm_pciids.h makes DRI functional:
{0x8086, 0x2592, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}
Comments at the top state tha
Nik schrieb:
>
>
> ...which brings me to the next point: Presumably, I should be
> testing/debugging this in a recent version of the DRI source? But which
> one? Should I be checking out from CVS? Or is it acceptable for me to
> work with the source of my distro (2.6.11-1.14_FC3)?
>
> And could
Nik schrieb:
> Philipp Klaus Krause wrote:
>
>> Nik schrieb:
>
>
> Oh ok. So in terms of names, the structure is:
>
>> The card-speciifc module in the kernel <== radeon
>> the card specific driver part in the DRI. <== r200
>
>
> correct?
Yes.
---
Philipp Klaus Krause wrote:
Nik schrieb:
Oh ok. So in terms of names, the structure is:
The card-speciifc module in the kernel <== radeon
the card specific driver part in the DRI. <== r200
correct?
Ok, so the r200 driver is actually not a kernel module, but is a driver
used by the DRI
Phillip!
Nochmal vielen Dank. Entschuldigen sie mir auch bitte dass ich so wenig
weiss dass ich immer noch neue Fragen stellen muessen.
Philipp Klaus Krause wrote:
Nik schrieb:
If I remeber correctly, the problem does not affect Mesa software
rendering. Thus it should be in the r200 specif
Nik schrieb:
> Philipp!
>
> Vielen Dank.
>
> Philipp Klaus Krause wrote:
>> Nik schrieb:
>>
>> It's unlikely that you'll have to debug the kernel module.
>> The bug probably is is the DRI.
>
> Ok, thanks. Any tips on what I should be looking for in the DRI?
>
> If the problem is in the DRI, the
Philipp!
Vielen Dank.
Philipp Klaus Krause wrote:
> Nik schrieb:
>
> It's unlikely that you'll have to debug the kernel module.
> The bug probably is is the DRI.
Ok, thanks. Any tips on what I should be looking for in the DRI?
If the problem is in the DRI, then does that it mean it should affe
Nik schrieb:
> Hi all,
>
> I've already reported this in bugzilla (bug# 3386). If I should have
> reported this problem in this forum first, I apologise. I am happy to
> debug this myself, if someone could please give me some pointers on how
> to debug an active kernel module, and what I should lo
oops.. cc-ing dri-devel this time.
Donnie Berkholz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Dergachev wrote:
I tagged yesterday "the_perfect_frag" snapshot of R300 driver.
The code is in CVS at http://r300.sf.net
As the name suggests I cannot find visible fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vladimir Dergachev wrote:
> I tagged yesterday "the_perfect_frag" snapshot of R300 driver.
>
> The code is in CVS at http://r300.sf.net
>
> As the name suggests I cannot find visible faults with rendering
> Quake3 levels. Also, PPRace
On Mon, May 23, 2005 at 01:37:10PM +0200, Dario Laera wrote:
> I'm doing some test with this driver, and I read on the website that
> "Radeon 9600 (including Radeon Mobility M10) - works well, no
> lockups"... well, not for me :P
>
> Exactly, I can play almost every 3d game avaible for linux/PPC,
23 matches
Mail list logo
