I recompiled a static Xserver so that could get a backtrace inside the
driver. This is the result:
Program received signal SIGSEGV, Segmentation fault.
0x080532e3 in SavageHelpSolidROP (pScrn=0x8624270, fg=0xb724, pm=-1,
rop=0xb728) at savage_accel.c:758
758 pm =
On Thu, 2003-12-18 at 18:21, craig qu wrote:
Is it possible to disable the side address mechanism
of Radeon 7000 by using command register(offset
CAP_PTR +8) bit SBA_ENABLE? and how?
Bit 12 of the RADEON_AGP_CNTL register is called SBA_DIS, there's no
further explanation in the docs though.
Felix Kühling wrote:
I recompiled a static Xserver so that could get a backtrace inside the
driver. This is the result:
Program received signal SIGSEGV, Segmentation fault.
0x080532e3 in SavageHelpSolidROP (pScrn=0x8624270, fg=0xb724, pm=-1,
rop=0xb728) at savage_accel.c:758
758
Hi!
After upgrading my box to latest trunk DRI, I got strange problem -
XServer did not start correctly, e.g. it hangs after init dri stuff. But I
can ssh to this box, and SysRq keys are working and I can
sync/umount/reboot. If I comment Load dri/remove radeon.o module - all
works fine except DRI
On Sun, 2003-12-21 at 14:55, Konstantin Lepikhov wrote:
Hi!
After upgrading my box to latest trunk DRI, I got strange problem -
XServer did not start correctly, e.g. it hangs after init dri stuff. But I
can ssh to this box, and SysRq keys are working and I can
sync/umount/reboot. If I
On Sun, 2003-12-21 at 14:55, Konstantin Lepikhov wrote:
After upgrading my box to latest trunk DRI, I got strange problem -
XServer did not start correctly, e.g. it hangs after init dri stuff. But I
can ssh to this box, and SysRq keys are working and I can
sync/umount/reboot. If I comment
On Sun, 21 Dec 2003 08:35:14 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
I recompiled a static Xserver so that could get a backtrace inside the
driver. This is the result:
Program received signal SIGSEGV, Segmentation fault.
0x080532e3 in SavageHelpSolidROP
Felix Kühling wrote:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both started
since I use different hardware
Keith Whitwell wrote:
Felix Kühling wrote:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two problems. One with
tnl/t_vb_render.c, the other one with tnl_dd/t_dd_tritmp.h. Both
started
since I use
Hi Michel!
Sunday 21, at 03:20:33 PM you wrote:
On Sun, 2003-12-21 at 14:55, Konstantin Lepikhov wrote:
After upgrading my box to latest trunk DRI, I got strange problem -
XServer did not start correctly, e.g. it hangs after init dri stuff. But I
can ssh to this box, and SysRq keys are
On Sun, 21 Dec 2003 09:52:32 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Keith Whitwell wrote:
Felix Kühling wrote:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two
Hello Tim,
as mentioned earlier on [EMAIL PROTECTED] I'm working on the savage S3
code drop, specifically on the 3D driver. A few days ago I managed to
get a working 3D driver ported to Mesa 4. It is now in DRI CVS on the
savage-2-0-0-branch. However, many users (including myself) are
Felix Kühling wrote:
On Sun, 21 Dec 2003 09:52:32 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Keith Whitwell wrote:
Felix Kühling wrote:
On Sat, 20 Dec 2003 08:01:07 -0500
Keith Whitwell [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
Hi,
while working on the savage driver I found two
Having briefly looked at the savage_dri.c file in cvs, there are
several XAA-like functions defined there, so there are two versions,
one for DRI (in savage_dri.c) and ones for XAA (in savage_accel.c).
e.g.:
static void
SAVAGEDRISetupForScreenToScreenCopy(
ScrnInfoPtr pScrn, int xdir, int
it looks like the file
Mesa-newtree/src/mesa/drivers/dri/radeon/radeon_lighting.c
isnt needed anymore.
At least it isnt in the Makefile.
Andreas
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just
On Sun, 2003-12-21 at 16:10, Konstantin Lepikhov wrote:
I send different logs/configs sorry about that. In previous XFree86.log.0,
I'm use AGPMode 1 and commented UseFBDev 1 and yes, this
XFree86.log.0 of hanged XFree86 server, it doesn't init keyboard/mouse and
my screen is blank.
I
Hi Michel!
Sunday 21, at 06:26:27 PM you wrote:
On Sun, 2003-12-21 at 16:10, Konstantin Lepikhov wrote:
I send different logs/configs sorry about that. In previous XFree86.log.0,
I'm use AGPMode 1 and commented UseFBDev 1 and yes, this
XFree86.log.0 of hanged XFree86 server, it doesn't
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
[EMAIL PROTECTED] changed:
What|Removed |Added
On Sun, 2003-12-21 at 20:14, Konstantin Lepikhov wrote:
Here is logs from dmesg:
skip
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Detected Intel i850 chipset
agpgart: AGP aperture is 64M @ 0xe000
radeonfb:
19 matches
Mail list logo
