--- Rick Harris <[EMAIL PROTECTED]> wrote:
[snip]
> Everything else worked as you described though I'm not sure why it's
> only showing 640x480 for you & Alex.
> All resolutions work fine up to 1024x768 on the laptop (MobileSavage
> IX/MV).
>
The problem we have is due to the fact that we are us
Attached is a patch that allows the depth of the Radeon depth buffer to
be set to either 16 or 24 bpp (24 bpp actually takes twice the space of
16 bpp, since the format is not packed; the extra byte is used for an
accellerated stencil buffer). As it is, the driver chooses 16 when the
display depth
On Sun, 18 Jan 2004 01:30:24 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
[snip]
> P.S.: drawing everything as software fallbacks doesn't always work on my
> ProSavage. With glxgears and some xscreensaver hacks I tried the window
> stays black. In flightgear some polys are missing (the runway) a
On Sat, 17 Jan 2004 17:52:07 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I got software fallbacks to work with Savage IX ;-), more or less.
> > It's
> > scribbling all over the screen, and what it draws depends on the
> > b
On Sul, 2004-01-18 at 01:56, Alex Deucher wrote:
> I'm not sure if this is a leak per se... the problem is the 2D and 3D
> driver aren't too good at managing memory. the 3D driver may snag a
> big chunk for a full screen 3D app and then "keep" it. It's then no
> longer available for the 2D driver
--- Alan Cox <[EMAIL PROTECTED]> wrote:
> On Sul, 2004-01-18 at 01:56, Alex Deucher wrote:
> > I'm not sure if this is a leak per se... the problem is the 2D and
> 3D
> > driver aren't too good at managing memory. the 3D driver may snag
> a
> > big chunk for a full screen 3D app and then "keep" i
On Sun, 2004-01-18 at 18:19, Brian Paul wrote:
> CVSROOT: /cvs/mesa
> Module name: Mesa
> Repository: Mesa/src/mesa/drivers/dri/common/
> Changes by: [EMAIL PROTECTED] 04/01/18 09:19:05
>
> Log message:
> include sched.h to get sched_yield() prototype
>
> Modified files:
>
Ohh I'm also using MergedFB, any options for that as long as I have to have a conf?
I'm on an
r200 (8900).
I also have this problem with quake3 using the left screen, needs to be on the right.
The left
then should be usable, don't think quake3 will give up the mouse. :(
Things like that can be
On Sun, 18 Jan 2004 16:16:13 +0100
Felix Kühling <[EMAIL PROTECTED]> wrote:
[snip]
> I found it. :) Comparison with the Utah driver helped once more. I'm
> attaching two new patches, one for the 2D driver, one for the 3D driver.
> They are against the latest savage-2-0-0-branch. With them fallback
On Wed, 2004-01-14 at 17:31, Keith Whitwell wrote:
>
> The patch looks good - I'm happy to see it committed.
Thank you. I noticed that the R100 driver handles attenuation (or at
least tries to? :) in Lightfv(), so
http://penguinppc.org/~daenzer/DRI/r200-attenuation-2.diff
might be better? BTW,
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=946
--- Additional Comments From [EMAIL PROTECTED] 2004-01-18 16:40 ---
I can reproduce 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=946
--- Additional Comments From [EMAIL PROTECTED] 2004-01-18 17:56 ---
okay I've updated
Does the r100 support the rectangle textures extension?
or is the driver borked? I have a CVS from a week or so ago and texrect
seems to now function correctly... is this a chip limitation or driver
bug?
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet
in the i810/5 manual I have, it mentions bit 31 of dword 2 the MAP_INFO
register allows non power of dimensions, and bit 14 of MAP_COORD_SETS is
whether the set is normalized or not ..
does anyone know if this is possible? I've hacked together
NV_texture_rectangle support but it doesn't seem to w
14 matches
Mail list logo
