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
--- Additional Comments From [EMAIL PROTECTED] 2004-02-17 00:05 ---
I have your same
Ok, so I'l build X at 64 bits as having a 32bit kmod would proble mean I'd
need a 32bit kernel. I have stoped working on this cause I can't build
the DRI tree. I have a working copy of Xfree86(provided by debian) so it
must be posible to build xfree86. Could I get a list of all the files
that I'
Mike Mestnik wrote:
--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
On Mon, 2004-02-16 at 21:14, Mike Mestnik wrote:
[...] Other than that and endianess and byte size issues is there any
thing else that might not work?
FWIW, people have been running Mach64 DRI on PPC for a while (only with
MMIO tho
Brian Paul wrote:
Ian Romanick wrote:
2. Mesa's X11 driver, which is the basis of libGLcore, depends on
information from an X VisualInfo. Most of the uses can be eliminated
trivially, but the depth / nplanes and ColomapEntries / colormap_size
fields are another story. The problem here is that
--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
> On Mon, 2004-02-16 at 21:14, Mike Mestnik wrote:
> > [...] Other than that and endianess and byte size issues is there any
> > thing else that might not work?
>
> FWIW, people have been running Mach64 DRI on PPC for a while (only with
> MMIO though,
On Mon, 2004-02-16 at 21:14, Mike Mestnik wrote:
> [...] Other than that and endianess and byte size issues is there any
> thing else that might not work?
FWIW, people have been running Mach64 DRI on PPC for a while (only with
MMIO though, not DMA), so endianness shouldn't be a problem.
--
Eart
--- Brian Paul <[EMAIL PROTECTED]> wrote:
> As Keith has mentioned a few times over the years, another approach to
> unifying libGLcore.a and the *_dri.so drivers would be replace the
> XMesa stuff with a new DRI pseudo-hardware driver that used software
> fallbacks for everything. That is, com
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
--
OK, thanks for the info about Mesa... I'm building it now I expect to be
testing it after 2300EST (after monday night stargate).
Onto bigger and better issues... I've been picking through the Gatos and
DRI 2D driver sources, trying to integrate the Gatos 2D changes cleanly.
Getting the radeon_dri
Ian Romanick wrote:
On Sunday I researched what it would take to migrate the
libglx.a-libGLcore.a interface to match the (new) libGL.so-*_dri.so
interface. Much to my surprise, I don't think it will be as difficult
as I had first thought. There are a few issues.
1. Right now libGLcore has sev
On Sunday I researched what it would take to migrate the
libglx.a-libGLcore.a interface to match the (new) libGL.so-*_dri.so
interface. Much to my surprise, I don't think it will be as difficult
as I had first thought. There are a few issues.
1. Right now libGLcore has several entry-points fo
--- Hod McWuff <[EMAIL PROTECTED]> wrote:
> On Mon, 2004-02-16 at 11:19, Michel Dänzer wrote:
> > On Sat, 2004-02-14 at 05:31, Hod McWuff wrote:
> > That's why I told you to forget about their 3D drivers.
>
> Understood. I'm just making the point that they were forgotten right
> from the word Go
Am Montag, 16. Februar 2004 21:43 schrieb Hod McWuff:
> On Mon, 2004-02-16 at 11:19, Michel Dänzer wrote:
> > On Sat, 2004-02-14 at 05:31, Hod McWuff wrote:
> > That's why I told you to forget about their 3D drivers.
>
> Understood. I'm just making the point that they were forgotten right
> from th
Mike Mestnik wrote:
I have a UltraSparc5 with an onboard Rage3D, workes with the mach64
driver. There are some problems with the kernel and PCI domains, but I
got thoes cleared out. There is still a problem that the chip is stuck in
whaterver mode is set by openboot(the bios), but I can change t
On Mon, 2004-02-16 at 11:19, Michel Dänzer wrote:
> On Sat, 2004-02-14 at 05:31, Hod McWuff wrote:
> That's why I told you to forget about their 3D drivers.
Understood. I'm just making the point that they were forgotten right
from the word Go ;)
> >
> > The problem is simply that I can't see an
I have a UltraSparc5 with an onboard Rage3D, workes with the mach64
driver. There are some problems with the kernel and PCI domains, but I
got thoes cleared out. There is still a problem that the chip is stuck in
whaterver mode is set by openboot(the bios), but I can change the bit
depth. Other
Hi, I just tested the latest drivers(two hours old, maybe? :)) and
everything works great, except the vesa FB console problem. glxgears
reports only 200fps and consumes 100%cpu, so i guess it still uses
software rendering. tuxracer works perfectly, but slowly(compared to
the old VIA driver and
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
4:00PM EST or 1:00PM PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous IR
Am Montag, 16. Februar 2004 18:39 schrieb Roland Scheidegger:
> Dieter Nützel wrote:
> > I ask if you have any idea why it (r200 with new lightning, e.g. hardware
> > accelerated TCL) hangs immediately in "Capture the Flag -> Citadel" when
> > I use the mouse (only put my hand on it and have some n
I have installed
XFree 4.3.99.16 patched and kernel 2-4-23-pre9, following Bruce
Copelandinstructions http://bugs.xfree86.org/show_bug.cgi?id=314
At the moment it is the same as getting dri from sourceforge, so I think I can
talk you about the bug even if I have not yet installed the last dr
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, 2004-02-15 at 03:27, Dieter NÃtzel wrote:
> ipers is faster (nearly as fast as last years best numbers).
Any interesting differences in the oprofile output?
> And ugh, what's that:
> atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
> atkbd.c: This is an XFr
Hi,
I would like to be able to read the current status of each individual
graphics
card, whether they are currently in retrace or not, and also how to
read/write the registers on each graphics card that store hsync/vsync
values. There are literature on vga programming which does about the same
job
Dieter Nützel wrote:
I ask if you have any idea why it (r200 with new lightning, e.g. hardware
accelerated TCL) hangs immediately in "Capture the Flag -> Citadel" when I
use the mouse (only put my hand on it and have some nervous fingers is
enough), but runs fine with cursor keys and both of it
Andreas Stenglein wrote:
Am 2004.02.14 00:11:35 +0100 schrieb(en) Roland Scheidegger:
Andreas Stenglein wrote:
Just tried ut2003 on R100 with current DRI+MESA cvs HEAD.
Now with the "MULT-code" in radeon_state.c radeon_state_init.c
(change lighting to use MULT instead of PREMULT ...) the
shadin
Hi,
The Savage driver now works on SavageIX (and probably Savage3D and
SavageMX) with 3D acceleration. I just committed the last few pieces to
the savage-2-0-0-branch. There are a few known issues left to sort out:
- flat shading
(Savage IX uses the first vertex's color instead of the last one
On Llu, 2004-02-16 at 16:42, Thomas Biege wrote:
> I attached my enhanced (hot-) fix patches. The same bugs appear in the
> drm4/ subdirectory too.
>
> Alan, were is the upper limit of 4096 for 'count' from?
Random safe number that seemed sufficient.
-
On Sat, 14 Feb 2004, Alan Cox wrote:
> On Gwe, 2004-02-13 at 11:31, Thomas Biege wrote:
> > Hi,
> > one of our developers mentioned that depth->n can be negative.
> >
> > I didn't checked the whole code but even if depth->n is unsigned,
> > count is signed and can be negative by using a depth->n
Michel DÃnzer wrote:
On Sat, 2004-02-14 at 02:47, Roland Scheidegger wrote:
[...] the trace tux leaves behind is missing on the R200 (with hw tcl).
Sometimes it shows up but at the wrong place.
That seems to work here.
Strange. I've just checked I'm running the same version, it's also 0.61.
I
On Sat, 2004-02-14 at 05:31, Hod McWuff wrote:
> I just caught on to something - the "Gatos 3D driver" that's been
> referred to as the cause of my woes. While reading the documentation
> (http://dri.sourceforge.net/cgi-bin/moin.cgi/DriverFiles) I realized
> that the "3D driver" is under "xc/lib/G
On Sat, 2004-02-14 at 12:42, Keith Whitwell wrote:
> Michel DÃnzer wrote:
> > On Sat, 2004-02-14 at 00:11, Roland Scheidegger wrote:
> >
> >>Just the other day, I've noticed not even the good old tuxracer runs
> >>correct on the R100 on my 2nd PC - the ice areas flickered a lot,
> >
> > That's
On Sat, 2004-02-14 at 02:47, Roland Scheidegger wrote:
>
> [...] the trace tux leaves behind is missing on the R200 (with hw tcl).
> Sometimes it shows up but at the wrong place.
That seems to work here.
--
Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer
Libre softwa
dan list wrote:
>
> Hi, I have a radeon 8500 card with 64MB of RAM, and my desktop
> resolution set to 2048x1536 I'm running the debian 4.3.0 radeon
xserver.
>
> I can run 3d programs at lower resolutions or in smaller windows just
> fine, but at full screen I get mostly black pixels, with a fe
Ville Syrjälä wrote:
[...]
I want to bypass the drm to do accel from user space. Doing an ioctl() for
each blit feels very expensive. Rather than do an ioctl() for each blit
the drm could check the commands in the DMA buffer for bad stuff. But that
doesn't feel very efficient either.
If an ioct
On Mon, Feb 16, 2004 at 01:30:33PM +0100, Helge Hafting wrote:
> Ville Syrjälä wrote:
> [...]
> >
> >I want to bypass the drm to do accel from user space. Doing an ioctl() for
> >each blit feels very expensive. Rather than do an ioctl() for each blit
> >the drm could check the commands in the DMA
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
--
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
--
37 matches
Mail list logo
