Jacek Rosik wrote:
Hi,
I was testing some apps on my PCI 9200. And I noticed that they run
terribly slow. But when i switched to wireframe mode the frame rate
seemed much better. This seemed strange. IIRC radeons are much faster in
rendering solid geometry than wireframe. So after a little
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=1657
--- Additional Comments From [EMAIL PROTECTED] 2004-10-19 01:49 ---
Perhaps
Hi!
Here is my work on adding stereo support for radeon. It consists of
patches against drm (as of 2004/10/04) , mesa (as of 6.2 release) and
xorg (as of 6.8.1 release). Note that 'linux-core' drm version is
untested as it doesn't work with my pci r200, and i don't have an agp
card currently.
On Monday 18 October 2004 16:04, Tino Keitel wrote:
On Mon, Oct 18, 2004 at 09:13:57 +0200, Tino Keitel wrote:
[...]
Thanks again. Looks like I used the wrong 2d driver patch before
(xorg680.atipatch.r300). Now the glxinfo output looks right:
OpenGL renderer string: Mesa DRI R300
A fix is in CVS now to make missing/broken I2C buses a non-fatal
error. Fixed in linux-2.6 and linux-core.
--
Jon Smirl
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your
Jon Smirl wrote:
On Tue, 19 Oct 2004 03:12:36 +0200, Roland Scheidegger
[EMAIL PROTECTED] wrote:
Vladimir Dergachev wrote:
On Tue, 19 Oct 2004, Roland Scheidegger wrote:
Jon Smirl wrote:
Does the new radeonfb driver in the kernel load? It uses the
same I2C initialization code.
excuse my
I noticed some kernel oopses in DRM in my kernel log. They don't seem to
be fatal as DRI is still working. This is on a machine with Vesa
framebuffer. On the other box without kernel framebuffer there are no
oopses.
Oct 19 18:30:31 trabant kernel: [drm] Initialized savage 1.0.0 20011023 on minor
Jon Smirl wrote:
A fix is in CVS now to make missing/broken I2C buses a non-fatal
error. Fixed in linux-2.6 and linux-core.
Ok, thanks. That gets around that problem, though it still doesn't work
(linux-core, I've not yet tried the linux-2.6 version).
When the X server starts and vesafb is
The fault is in drm_set_busid. It's a NULL pointer reference. I'm not
seeing this so it may be savage specific. The only place I can see
where you could get a NULL reference is if the PCI driver didn't set a
name, dev-pdev-driver-name. Can you add a debug statement and check
if there is one? The
Roland Scheidegger wrote:
Jon Smirl wrote:
A fix is in CVS now to make missing/broken I2C buses a non-fatal
error. Fixed in linux-2.6 and linux-core.
Ok, thanks. That gets around that problem, though it still doesn't work
(linux-core, I've not yet tried the linux-2.6 version).
Forgot to mention,
On Tue, 19 Oct 2004 18:14:32 +0200, Roland Scheidegger
[EMAIL PROTECTED] wrote:
Another posibility is that the monid port on your card is just
broken, but you never noticed since you don't have a monitor plugged
in that needs it.
What exactly are the different ports good for? Getting the
What do I have to do to X to make it call set_busid? It's not getting
called in my config.
--
Jon Smirl
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us
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=1657
--- Additional Comments From [EMAIL PROTECTED] 2004-10-19 13:14 ---
As far as
Am Di, den 19.10.2004 schrieb Jon Smirl um 20:11:
The fault is in drm_set_busid. It's a NULL pointer reference. I'm not
seeing this so it may be savage specific. The only place I can see
where you could get a NULL reference is if the PCI driver didn't set a
name, dev-pdev-driver-name. Can you
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=1657
--- Additional Comments From [EMAIL PROTECTED] 2004-10-19 15:07 ---
(In reply
On Tue, 19 Oct 2004 12:24:23 -0400, Jon Smirl [EMAIL PROTECTED] wrote:
On Tue, 19 Oct 2004 18:14:32 +0200, Roland Scheidegger
[EMAIL PROTECTED] wrote:
Another posibility is that the monid port on your card is just
broken, but you never noticed since you don't have a monitor plugged
in
Does this fix it for you? I haven't figured out how to trigger it yet.
[EMAIL PROTECTED] drm-bk]$ bk -r diffs -u
= linux-core/drm_drv.c 1.11 vs edited =
--- 1.11/linux-core/drm_drv.c 2004-10-18 22:58:26 -04:00
+++ edited/linux-core/drm_drv.c 2004-10-20 00:33:20 -04:00
@@ -329,6 +329,8
On Wed, 20 Oct 2004 00:40:07 -0400, Jon Smirl [EMAIL PROTECTED] wrote:
Does this fix it for you? I haven't figured out how to trigger it yet.
I think the problem here is that vesafb is not attached as a true
device driver but it has the resources allocated. DRM comes along and
see vesafb so it
I checked in a fix that switches from
dev-pdev-driver-name
to
drm-driver-pci_driver.name
This should fix the segfaults in stealth mode when the pci driver is
set to the wrong driver (fbdev) or no driver (vesafb).
Please give it a try.
--
Jon Smirl
[EMAIL PROTECTED]
I checked in a fix that switches from
dev-pdev-driver-name
to
drm-driver-pci_driver.name
This should fix the segfaults in stealth mode when the pci driver is
set to the wrong driver (fbdev) or no driver (vesafb).
Please give it a try.
--
Jon Smirl
[EMAIL PROTECTED]
20 matches
Mail list logo
