[Bug 5986] The X server locks up after a few days

2006-03-27 Thread bugzilla-daemon
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=5986  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:21 ---
With the new 20060322 driver and the 1.0.2 server X still locks up.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6357] savage problem: glxgears produce black window

2006-03-27 Thread bugzilla-daemon
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=6357  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:27 ---
A little update. I tried latest snapshot and common libraries (20060324). Now X
won't start and gives a black screen. With previows  common libraries (20060311)
glxgears gives always a little black screen (and 99% CPU usage).  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6357] savage problem: glxgears produce black window

2006-03-27 Thread bugzilla-daemon
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=6357  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:31 ---
Created an attachment (id=5080)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5080&action=view)
Xorg.log with common-20060311
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6357] savage problem: glxgears produce black window

2006-03-27 Thread bugzilla-daemon
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=6357  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:32 ---
Created an attachment (id=5081)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5081&action=view)
Xorg.log with common-20060324
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6357] savage problem: glxgears produce black window

2006-03-27 Thread bugzilla-daemon
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=6357  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:33 ---
Created an attachment (id=5082)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5082&action=view)
Latest Kernel configuration
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6357] savage problem: glxgears produce black window

2006-03-27 Thread bugzilla-daemon
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=6357  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-27 18:34 ---
Created an attachment (id=5083)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5083&action=view)
Latest Xorg configuration
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: Mach64

2006-03-27 Thread Felix Kühling
Am Freitag, den 24.03.2006, 23:50 +0200 schrieb Micha Feigin:
> On Thu, 28 Jul 2005 16:30:47 -0400
> Alex Deucher <[EMAIL PROTECTED]> wrote:
> 
> > On 7/28/05, Svante Signell <[EMAIL PROTECTED]> wrote:
> > > Is anything happening on the Mach64 front for DRI/X.org? It would be
> > > nice to use the 3D capabilities, now that Debian has upgraded unstable
> > > to Xorg.
> > 
> > there is a DRI driver for mach64, but the drm is not yet secure so
> > it's not built by default.
> 
> Somehow considering the age of this card I doubt the time will be found to
> secure the DRM, but maybe I'm wrong.

I'm currently trying to get my hands on an old Mac Notebook with Mach64.
In its current state, Mach64 DRI support is essentially a waste of
everyone's time who has been working on it in the past. Probably most
potential users aren't even aware of it. I am hoping to change that.

Cheers,
  Felix

> 
> > binary snapshots:
> > http://dri.freedesktop.org/wiki/Download#head-55420c59a1c2e9a70f07a6fa02f0d228ffb87b76
> 
> I am using the binary snapshot with the unstable version of X.org and its
> working great. Currently it doesn't really complicate things much as the 
> kernel
> doesn't include the mach64 driver anyway so even if X included it, it would
> still require to compile the kernel driver each time you update the kernel.
> 
> > building from source:
> > http://dri.freedesktop.org/wiki/Building
> > 
> > Alex
> > 
> > > --
> > > Svante Signell <[EMAIL PROTECTED]>
> > > 
> > >
> > 
> > 

-- 
| Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu |
| PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3  B152 151C 5CC1 D888 E595 |



---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6409] New: XvMC on Intel i810

2006-03-27 Thread bugzilla-daemon
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=6409  
 
   Summary: XvMC on Intel i810
   Product: DRI
   Version: XOrg CVS
  Platform: PC
OS/Version: other
Status: NEW
  Severity: normal
  Priority: P2
 Component: General
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]


tried to use XvMC on a Celeron 1GHz with an intel 810 integrated video chipset
So started with it enabled on config file, lots of memory allocated (64MB) and 
played with mplayer -vo xvmc. Each time the player window opens then the whole 
machine gets frozen (even Alt-Syst-B doesn't reboot it).
Does anyone had success with XvMC on this hardware, in order to help me 
debugging?  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 5600] sis_tex.c Failure to allocate texture memory

2006-03-27 Thread bugzilla-daemon
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=5600  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 00:00 ---
There are now lots of OpenGL software that needs more than 32MB, looks like 
your problem is only your SIS misses memory that display everything the 
software wants to display.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: radeon problems with current cvs code

2006-03-27 Thread Luca Dionisi
On 3/25/06, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> On Sat, 2006-03-25 at 02:26 +0100, Luca Dionisi wrote:
> > I'm having problems with Xorg built from cvs sources very recently.
> > I've also built from cvs sources libdrm and the latest kernel (2.6.16)
> > with the drm enabled for my card (radeon)
> > I don't know for sure, but I think my problem is with the
> > video driver (the ati open source driver)
> > The syptom is that Xorg start, but sometimes it hangs hup very
> > quickly, sometimes when I change VT, sometimes when I
> > click the mouse, ... Most of the times my whole machine
> > becomes unusable.
> >
> > Any help please! I attach the log and the xorg.conf
>
> Looks like the engine is going nuts. Can you try:
>
>  - Disabling AGP fast write
>  - Lowering AGP speed
>  - Load DRM with option no_wb=1
>  - Try latest DRM CVS
>
> And tell me if any of these helps. Also, when you say "very recently"
> for your X.org build, when exactly did you get the ati driver from CVS ?
> If it was more than 4 days ago, it might be worth updating and trying
> again.
>
> Ben.
>
>
>

Very recently was not enough recently.
I updated again from cvs and now it all works.

Just 2 questions:
> Load DRM with option no_wb=1
what is it for and how do I do it?
> Try latest DRM CVS
I have kernel 2.6.16. I saw that source files such as radeon.c
were identical to the ones in DRM CVS. Am I wrong?
At the moment I have a kernel compiled without module support.
And the radeon drm is built-in. Do I have to change that?

At the moment it works, but xgl is slow with movies.
I saw this sentence in the suse site:

Driver has neither pBuffer nor FBO support. When using a composite
manager all windows are rendered in software and only compositing is
hardware accelerated. Astonishingly, this works well enough for most
use cases.

What does it mean? That is, is the driver _never_ going to have that support?

Many thanks

--Luca


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


DRI fails when quickly closing an app

2006-03-27 Thread Dave Kavanagh
I have a strange problem that happens when I start and then quickly close an
app that enables direct rendering. If I close it quickly enough, the app will
end with the following error:

"(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI."

The next time I run an app that requires direct rendering, it will fail to
load i915_dri.so. Instead, it will use Mesa indirect rendering. The next
app I run after this will correctly enable DRI and use i915_dri.so.

Running glxinfo causes the problem 99% of the time. I believe it's because
it runs so quickly.

I have been looking through the code trying to figure out what fails when I
close an app quickly. So far, I have traced it to the point where drm_ioctl
(in drm/linux-core/drm_drv.c) handles DRM_IOCTL_SET_VERSION. There's code in
this function that checks to see if priv->master is set. If it is not then
the function returns an error (EACCES) instead of calling the handler for
DRM_IOCTL_SET_VERSION.

I am using the following versions:
- Xorg 6.9.0
- Mesa 6.4
- libdrm 1.0.5

I applied the patches listed here to add vblank sync:
https://bugs.freedesktop.org/show_bug.cgi?id=3031

Any info, help, or pointers would be appreciated.

Thanks,
Dave


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] New: mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 
   Summary: mach64 vertex buffer cleanup
   Product: Mesa
   Version: CVS
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: P2
 Component: Drivers/DRI/Mach64
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]


mach64 is unique is having two implementations of VB, one that uses the
"template" vertex format and one that uses the "native" vertex format.

The "template" implementation uses the mesa provided t_dd_vb.c. However, 
it still provides its own version of t_dd_vbtmp.h (mach64_vbtmp.h) and 
adds complex draw functions in mach64_tris.c for conversion to native format.

The "native" implementation has simple draw functions. However, it performs
conversion to native format during emit (mach64_native_vbtmp.h) and back to
template format in translate (mach64_native_vb.c), these functions differ
greatly from the tnl_dd templates.

The attached patches have yet another implementation of the mach64 VB.
They define mach64Vertex as a struct that matches the native vertex format,
this allows to use both the mesa templates with very little changes and 
the simple draw functions.

The quirks are:
* we still have to provide slightly modified versions of templates t_dd_vb.c
  and t_dd_vbtmp.h, however the changes to t_dd_vb.c are minimal and can be
  dropped with another iteration of cleanups if the patches are accepted.

* they drop MACH64_PREMULT_TEXCOORDS, it did not seem to make a difference
  in performance.

* they push conversion to little-endian down to the draw functions, these
  changes are untested as I have x86.  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 09:00 ---
Created an attachment (id=5096)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5096&action=view)
patch for mach64 DRI
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 09:01 ---
Created an attachment (id=5097)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5097&action=view)
t_dd_vb.c for mach64
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 09:01 ---
Created an attachment (id=5098)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5098&action=view)
t_dd_vbtmp.h for mach64
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 10:06 ---
I haven't looked at your patches yet ... You may want to take a look at the
t_vertex.c based code in e.g. the Savage driver. Template-based vertex setup
code in some drivers has been replaced with the t_vertex-based code. If it is
flexible enough to generate mach64 native vertices that may be beneficial in
terms of binary and source code size, though not necessarily performance.   
   
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 12:07 ---
Created an attachment (id=5100)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=5100&action=view)
big patch for mach64 DRI

This patch does not add files, instead it merges the changes to existing files.


Specifically, it incorporates the changes for NATIVE_VTXFMT in mach64_vbtmp.h
which would only be used for the template format. mach64_vbtmp.h was derived
from t_dd_vbtmp.h v3.5 while the changes for native format are derived 
from t_dd_vbtmp.h v5.0.1 (current). Thus the changes for mach64_vbtmp.h are
those between the different versions of t_dd_vbtmp.h and the additions for the
native format (patch 5098).

As a side effect, it fixes the mach64 driver when compiled with the template
format (currently it shows a black screen).
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Bug 6412] mach64 vertex buffer cleanup

2006-03-27 Thread bugzilla-daemon
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=6412  
 




--- Additional Comments From [EMAIL PROTECTED]  2006-03-28 12:12 ---
(In reply to comment #4)
> I haven't looked at your patches yet ... You may want to take a look at the
> t_vertex.c based code in e.g. the Savage driver. Template-based vertex setup
> code in some drivers has been replaced with the t_vertex-based code. If it is
> flexible enough to generate mach64 native vertices that may be beneficial in
> terms of binary and source code size, though not necessarily performance.

I'll have a look at it,
thanks for the pointer.
  
 
 
--   
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email 
 
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.


---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: radeon problems with current cvs code

2006-03-27 Thread Benjamin Herrenschmidt

> > Load DRM with option no_wb=1
> what is it for and how do I do it?

Well... it tells your DRM to not try to do writeback through AGP (that
is to not let the video card write various status informations back to
memory via the AGP bus). Doing AGP writeback is faster, but on some
chipsets, it doesn't work properly. The driver tries to detect it, but
we had some examples in the past where the detection would say "ok"
while it's still unreliable. This option forces not to do it. To do
that, you either:

  modprobe radeon no_wb=1

(Or edit the appropriate modultils config file to have that option by
default)

Or if the module is built-in the kernel, boot the kernel with

  radeon.no_wb=1

On the kernel comand line.

> > Try latest DRM CVS
> I have kernel 2.6.16. I saw that source files such as radeon.c
> were identical to the ones in DRM CVS. Am I wrong?

There is no such file as radeon.c that I can remember :) the drm CVS has
a slightly more up to date version than 2.6.16. To build it in linux, go
to linux-core and type

 make DRM_MODULES="radeon"

> At the moment I have a kernel compiled without module support.
> And the radeon drm is built-in. Do I have to change that?

If it works for you, stay with it.

> At the moment it works, but xgl is slow with movies.
> I saw this sentence in the suse site:
> 
> Driver has neither pBuffer nor FBO support. When using a composite
> manager all windows are rendered in software and only compositing is
> hardware accelerated. Astonishingly, this works well enough for most
> use cases.
> 
> What does it mean? That is, is the driver _never_ going to have that support?

It will, just no yet. It's beeing developped on intel chipsets at the
moment and will probably be ported over at one point. I can't tell more
precisely.

Ben.




---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel