On Sat, 2004-02-07 at 04:53, Michel Dnzer wrote:
On Sat, 2004-02-07 at 03:55, Stephen Waters wrote:
On Mon, 2004-01-12 at 18:09, Michel Dnzer wrote:
The best thing is to log in remotely and attach gdb to the server.
I just tried this. Here's what happens:
# gdb
(gdb) attach
http://bugme.osdl.org/show_bug.cgi?id=2054
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |REJECTED
Resolution|
http://bugme.osdl.org/show_bug.cgi?id=2054
Summary: ATI binary driver
Kernel Version: 2.6.2
Status: NEW
Severity: normal
Owner: [EMAIL PROTECTED]
Submitter: [EMAIL PROTECTED]
Distribution:
Fedora Core 1
Hardware Environment:
ATI R200
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Alex,
I'm working on 3D support for Savage IX right now. I've added
register
structures for SavageIX. Now I
On Mon, 9 Feb 2004 06:10:26 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
[snip]
I'm going to commit my current integration work now. This will break
Xv, tile mode, and console mode for the time being, but I hope to
rectify that soon. for
Hi,
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is terribly inefficient the way it implements
tiling and
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will
have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is
On Mon, Feb 09, 2004 Christian Schoenebeck wrote:
Hi!
I have the same problem as you mentioned on DRI-Devel ML (freeze of X with
Radeon Mobility whenever DRI access occurs). Has there been any progress in
this field meanwhile? Did anybody solve the problem?
Best regards
Christian
--- Alex Deucher [EMAIL PROTECTED] wrote:
--- Jon Smirl [EMAIL PROTECTED] wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic
but I've
Nice work Jon! Very impressive! How about dualhead cards? how are
Felix Kühling wrote:
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is terribly inefficient the way it
All of my 3d games are having issue with the i830 drm kernel module.
This error is produced by configuring jose to use a 3d view.
java: i830_tex.c:432: i830DeleteTexture: Assertion `t' failed.
I receive a similar error with tux racer.
tuxracer: i830_tex.c:432: i830DeleteTexture: Assertion
On Mon, 09 Feb 2004 09:14:28 -0800
Ian Romanick [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will have
to wait at least until the 3D driver can determine
Patrick Dohman wrote:
All of my 3d games are having issue with the i830 drm kernel module.
This error is produced by configuring jose to use a 3d view.
java: i830_tex.c:432: i830DeleteTexture: Assertion `t' failed.
I receive a similar error with tux racer.
tuxracer: i830_tex.c:432:
Dave,
I was the one that brought this up. I have a little time (a few hours a
week only) to work on it, and since no one else seemed to care I was
going to tackle this very slowly. I was going to work on the DRM
insecurities once I dug up the old conversations with Jose detailing
what needed
Andreas Stenglein wrote:
like the R200 one.
It doesnt contain intendation fixup yet.
I tried only with q3a.
The patch looks good to me. Does the texenv test look right? If that
looks good, commit it. Thanks for taking care of this.
---
On Mon, 2004-02-09 at 11:37, Jon Smirl wrote:
I'm working on some code for the R200 I2C devices. There are four of them. It's
obvious what CRT, CRT2, and DVI do. But what does MONID do?
As Alex said. Note that you can extract the mapping of outputs from
the BIOS, ATI devrel may be able to give
I haven't reached that stage yet so I'm open to any ideas that will work. Fell
free to download the code and work on whatever interests you.
My immediate goal is to get a login console up on a single screen. That means I
need to get the mode set, make fonts work and write a mini-terminal
Oh, and let me add that the notion of moving the console fully
to userland is definitely not something that has been accepted.
It is interesting to evaluate the solution, but lots of kernel
folks will just turn it down for some simple reasons, like not
beeing able to printk bug reports from
On Mon, 2004-02-09 at 15:27, Jon Smirl wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
bk clone
On Mon, 2004-02-09 at 22:41, Benjamin Herrenschmidt wrote:
[ lots of good points ]
I agree with your points Ben, thanks for bringing them up.
--
Earthling Michel Dnzer | Debian (powerpc), X and DRI developer
Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
Ian Romanick wrote:
Felix Kühling wrote:
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is terribly
On Tue, Feb 10, 2004 at 09:40:25AM +1100, Benjamin Herrenschmidt wrote:
bk clone bk://mesa3d.bkbits.net/drm
ERROR-Lock fail: possible permission problem.
Oops.
OK, fixed. Sorry for the inconvenience.
(In the future, please let [EMAIL PROTECTED] know of such problems.)
-andy
In my test system I run X from a PCI ATI Rage128, my target is a AGP Radeon
9000. So when I boot the Rage gets initialized and the Radeon does not. When you
load the Radeon DRM driver it will detect that the Radeon is not initialized in
the hotplug event. To make the reset automatic you need a
--- Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
Oh, and let me add that the notion of moving the console fully
to userland is definitely not something that has been accepted.
It is interesting to evaluate the solution, but lots of kernel
folks will just turn it down for some simple
Now that I've commited the lighting changes for r200 (still has the
material fallback though), I've wanted to commit the same changes (well
not exactly the same of course ;-)) to the radeon driver too (some brief
testing showed it worked just fine). But I'm a bit confused, the code
I'll need
On Mon, 9 Feb 2004, Jon Smirl wrote:
There are lots of solutions to this:
1) queue the printk's
2) add an in-kernel path for write to console that cooperates with the normal
user space one
3) if you know you are going to be debugging code like this, use an alternative
solution like the
On Tue, Feb 10, 2004 at 08:41:40AM +1100, Benjamin Herrenschmidt wrote:
|
| - GL cannot be the _only_ API, simply because we don't (and may not have
| for some time) GL support on all cards, while still wanting this new console
| stuff so we don't have to keep the old cruft around
Just so long
--- Linus Torvalds [EMAIL PROTECTED] wrote:
On Mon, 9 Feb 2004, Jon Smirl wrote:
There are lots of solutions to this:
1) queue the printk's
2) add an in-kernel path for write to console that cooperates with the
normal
user space one
3) if you know you are going to be debugging code
Just a quick thank you to for helping me get 3d support on my machine.
Regards,
Patrick
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity.
On Sun, Feb 08, 2004 at 08:27:17PM -0800, Jon Smirl wrote:
I have a new version of DRM at bk://mesa3d.bkbits.net/drm
In it's current form it's 2.6 kernel only. Some support is generic but I've
mainly be working on an R200. It is still under development with lots of work to
do.
Ugh. I find
Bugs item #893194, was opened at 2004-02-08 22:53
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=100387aid=893194group_id=387
Category: ATI OpenGL
Group: X Server Hang/Core Dump
Status:
[ Following up to the dri-devel mailing list, we aren't really using the
sf.net bug tracker anymore but rather the kernel and XFree86 bugzillas ]
On Mon, 2004-02-09 at 04:55, SourceForge.net wrote:
I just ported the latest CVS drm-kernel code into the
2.6.2 vanilla kernel.
Do you have a
On Sat, Feb 07, 2004 at 12:44:39AM -0800, Ian Romanick wrote:
I like it. :) It looks a little weird to me like that, but I think
doing 1.2 (1.4.20040108 Foobar, Inc. Fancypants GL) should work just
as well.
I would want to be very sure that there are no apps parsing that
string before
33 matches
Mail list logo
