On Thu, 25 Sep 2003, Dave Airlie wrote:
If Linus thinks your patch goes far enough for him..
I actually usually don't much like whitespace changes, and the one I sent
was purely in response to the fact that there already was a lot of
whitespace changes in the i810 driver.
Don't worry too
On Thu, 2003-09-25 at 22:58, Linus Torvalds wrote:
On Thu, 25 Sep 2003, Dave Airlie wrote:
If Linus thinks your patch goes far enough for him..
I actually usually don't much like whitespace changes, and the one I sent
was purely in response to the fact that there already was a lot of
On Thu, Sep 25, 2003 at 01:24:21PM -0400, Malcolm Mallardi wrote:
Second concern. With any build of the drivers, certain applications
and games when in hardware accellerated mode will not display the mouse
cursor. Two games that readily come to mind are Unreal Tournament and
Soldier of
26 2003 07:48 Rafael Maximo :
At 07:38 PM 25/9/2003, Felix Khling wrote:
Hi Rafael, (a bit confused now, which one is your first name ;-)
I'm just back from vacation and read about your progress. I'm eager to
start testing and debugging the new driver. I think the best thing would
be if
On Fri, 26 Sep 2003 14:03:39 +0600
Dimitry N. Naldaev [EMAIL PROTECTED] wrote:
Ð ÑообÑении Ð¾Ñ 26 СенÑÑбÑÑ 2003 07:48 Rafael Maximo
напиÑал:
At 07:38 PM 25/9/2003, Felix Kühling wrote:
Hi Rafael, (a bit confused now, which one is your first name ;-)
I'm just
26 2003 14:31 Felix Khling
:
On Fri, 26 Sep 2003 14:03:39 +0600
Dimitry N. Naldaev [EMAIL PROTECTED] wrote:
26
2003 07:48 Rafael Maximo
:
At 07:38 PM 25/9/2003, Felix Khling wrote:
Hi Rafael, (a bit confused now, which one is your first name ;-)
I'm just back from
Hello!
I'm developing a graphic driver for radeon cards
as part of a research OS (PLURIX) at an university.
We're already supporting the R100-based radeon cards
(including the (simple) TCL) and want also to support
the R200-based cards.
But with these cards I have a big problem:
I can draw
On Fri, 26 Sep 2003 00:53:13 +0100
José Fonseca [EMAIL PROTECTED] wrote:
BTW, have u seen
http://dri.sourceforge.net/cgi-bin/moin.cgi/ConfigurationInfrastructure
? ;-)
Feel free to add any more info you see fit.
Also, I noticed I put your name wrong there too: The umlaut ü-ue thingy
I
At 06:28 AM 26/9/2003, Dimitry N. Naldaev wrote:
Ð ÑообÑении Ð¾Ñ 26 СенÑÑбÑÑ 2003 14:31 Felix Kühling
напиÑал:
On Fri, 26 Sep 2003 14:03:39 +0600
Dimitry N. Naldaev [EMAIL PROTECTED] wrote:
àÃÂþþñÃÂõýøø þà26
On Fri, 26 Sep 2003 07:36:02 -0300
Rafael Maximo [EMAIL PROTECTED] wrote:
At 06:28 AM 26/9/2003, Dimitry N. Naldaev wrote:
Ð_ Ñ_ообÑ_ении оÑ_ 26 СенÑ_Ñ_бÑ_Ñ_ 2003 14:31 Felix Kühling
напиÑ_ал:
On Fri, 26 Sep 2003 14:03:39 +0600
Dimitry N. Naldaev [EMAIL PROTECTED]
I think R128 support is broken in the current 2.6 bk kernel. All 3D apps
segfault. Can anyone else verify?
Radeon support works without problem.
=
Jon Smirl
[EMAIL PROTECTED]
__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
On Fri, 2003-09-26 at 14:06, Jon Smirl wrote:
I think R128 support is broken in the current 2.6 bk kernel. All 3D apps
segfault. Can anyone else verify?
Have you verified that the same 3D driver works with another DRM? IIRC
you posted somewhere that it segfaults in the Mesa SSE check, which is
On Fri, Sep 26, 2003 at 10:49:03AM +0300, Ville Syrj?l? wrote:
On Thu, Sep 25, 2003 at 01:24:21PM -0400, Malcolm Mallardi wrote:
I doubt it's an SDL bug because I think that most games render their own
mouse cursor. I've seen this bug with freespace2 under XFree86. It works
fine under
I'm thinking about implementing a textured video option on radeon for
mergedfb (or non-mergedfb too for that matter). It would be useful
since video windows could span heads in mergedfb mode and you could
also have multiple Xv windows at the same time rather than just one
with the overlay unit.
I found at least a workaround for the problem. Set
Option DisableTile on
in the Device section of XF86Config-4. I think this has something to do
with the frame buffer layout. Accellerated stuff seems to get it right.
But non-accelerated stuff accesses the frame buffer in the wrong way.
Try
I think I found it. Try this patch with patch -p0 in
xc/programs/Xserver/hw/xfree86/drivers/savage:
--- ./savage_driver.c.~1.10.10.5.~ 2003-09-26 14:00:23.0 +0200
+++ ./savage_driver.c 2003-09-26 19:03:30.0 +0200
@@ -2601,7 +2601,7 @@
pScrn =
Hello Dimitry,
Thanks for the patch. The BCI_LINE_MISC thing is already corrected on
the savage-1_0_0-branch. The other things look like attempts to enable
DRI on a chip for which DRI is not supported at this point. As was said
before, the S3 driver has DRI support for the Savage4 series but not
I believe there was some discussion of this on the directfb mailing
list. I think the savage chips require a tile based framebuffer for
acceleration, but this is incompatible with things that assume a linear
based framebuffer.
Alex
--- Felix K�hling [EMAIL PROTECTED] wrote:
I found at least a
In the linux 2.4 kernel tree under drivers/char there is both a drm
subdirectory and a drm-4.0 subdirectory.
I've looked high and low for an explanation of drm vs. drm-4.0, I assume
its a version difference, but I've come up dry. Can someone either
explain to me what drm-4.0 is or send me a
Here's what I know:
Redhat Rawhide Xfree works on 2.4 uni and smp with R128 DRM
Redhat Rawhide Xfree fails on 2.6 uni and smp, using kernel R128 DRM
DRI CVS fails on 2.6 uni and smp, using kernel R128 DRM
All combinations work on Radeon
All failures are the same, immediate segfault of 3D apps.
I
The DRM changed between xfree86 4.0.x and 4.1.0 in an incompatible way.
some kernel trees retained both DRMs so that you could build the
appropriate DRM depending on what version of xfree86 you were using.
Alex
--- John Dennis [EMAIL PROTECTED] wrote:
In the linux 2.4 kernel tree under
perfectly.
now i want dri support too. i downloaded the radeon package
(radeon-20030926-linux.i386.tar.bz2) run install.sh and everything
worked great but when i run startx i get the same message as when the
card wasnt detected by the driver before.
[quote /var/log/XF86log.0.log]
...snip
(II) Primary
and it worked perfectly.
now i want dri support too. i downloaded the radeon package
(radeon-20030926-linux.i386.tar.bz2) run install.sh and everything
worked great but when i run startx i get the same message as when the
card wasnt detected by the driver before.
[quote /var/log/XF86log.0.log
On Fri, 2003-09-26 at 21:17, Jon Smirl wrote:
Redhat Rawhide Xfree works on 2.4 uni and smp with R128 DRM
Redhat Rawhide Xfree fails on 2.6 uni and smp, using kernel R128 DRM
DRI CVS fails on 2.6 uni and smp, using kernel R128 DRM
All combinations work on Radeon
Could still be another
On Fri, 2003-09-26 at 22:30, Alex Deucher wrote:
Also I believe Michel added the patch to CVS so it should show up in
the snapshots soon.
It's only in XFree86 CVS yet, but overriding the chip ID to another 9200
should be fine.
--
Earthling Michel Dnzer \ Debian (powerpc), XFree86 and
On Fri, 2003-09-26 at 19:26, Alan Hourihane wrote:
Log message:
no longer need radeon_pci.h since the XFree86 merge
Then it was never needed. I added it in order to
* try and confine radeon driver merges between XFree86 and DRI CVS
to the ati driver directory (as mentioned in
I believe this is a problem isolated to the Redhat Rawhide Xfree binaries,
specifically their r128_dri.so modules. No version of the DRM module is causing
problems.
I was tricked earlier when I though I was running DRI CVS but in fact I wasn't.
RH has a tls enabled version in
On Fri, 2003-09-26 at 18:16, Alex Deucher wrote:
1. looking at the mga textured video code, it disables the DRI when it
is in use. is there any reason for this? is it possible to use the
texture engine for Xv and DRI at the smae time. It seems like it
should.
I agree.
When
28 matches
Mail list logo
