El Sáb 15 Sep 2001 02:41, escribiste:
On Friday 14 September 2001 21:08, you wrote:
That's fine -- I wasn't suggesting that. But, for the people who can
actually do this job, the r128/G400 isn't terribly interesting anymore.
Isn't the whole open source thing about developers scratching an
Hello all:
I am new to this list. I have a Sony C1VN (256MB RAM, 12GB disk, ATI
Mobility M1 w/8MB VRAM PCI) running Mandrake 8.0 with XF86 3.3.6 and
UTAH-glx. This has been running OpenGL apps like Quake III and Shogo
very nicely. I have done some C coding before but not to this level, I
once
On Saturday 15 September 2001 07:08, you wrote:
Frank, one more time, I would like to have your work to take a look on it.
Perhaps with more eyes looking at the problem we could find something. And
if you could release your changes we could test it in another machines and
see different
On Sat, 15 Sep 2001, Frank Earl wrote:
On Saturday 15 September 2001 07:08, you wrote:
Frank, one more time, I would like to have your work to take a look on it.
Perhaps with more eyes looking at the problem we could find something. And
if you could release your changes we could test it
Gerd Knorr wrote:
I've figured why the Rage 128 crashes if the bttv overlay is active (see
http://sourceforge.net/tracker/index.php?func=detailaid=210239group_id=387atid=100387).
Because the r128 driver does 2D acceleration using MMIO commands, it has
to shutdown the CCE every time it
Gareth Hughes wrote:
Anyone who questions my dedication to this project can take it up with me
offline -- I'd be more than happy to discuss it with them.
I certainly don't question your past dedication. I appreciate it very much. I
was a bit deceived by your abandoning it though.
I think
On Sun, 16 Sep 2001, Michel Dänzer wrote:
Anyone who questions my dedication to this project can take it up with me
offline -- I'd be more than happy to discuss it with them.
I certainly don't question your past dedication. I appreciate it very much. I
was a bit deceived by your abandoning it
On Sunday 16 Sep 2001 2:45 am, you wrote:
If the companies could get volunteers to maintain the old drivers for them
that could even save them some money ... and it would be almost like free
advertising. I certainly would buy my next graphics card from a company
that supports volunteer
On Sat, 2001-09-15 at 21:45, Frank Worsley wrote:
As usual I have to give my 2 cents on this. :)
First off all, it is very sad to hear that the whole team has been let go
from VA Linux. I wish all of you the best luck in the future. Thanks a lot
for all the work you have put into this!
On Sat, 2001-09-15 at 23:44, Jeffrey W. Baker wrote:
Lots of people are willing to help, but it's very naive to think that
random hackers are going to reverse engineer these complicated drivers in
any kind of reasonable time frame. Open source drivers for new 3D gear
depend entirely on
Michel Dänzer wrote:
I certainly don't question your past dedication. I appreciate it very much. I
was a bit deceived by your abandoning it though.
Mate, if you understood the situation, you wouldn't be saying this. I will
let this pass by as a result.
My point is that nobody is
Dear Gareth and all,
I think that people need to calm down --- the issue of funding seems to be
in the forefont of everyone's mind. I'm just going to enumerate some things.
1) People NEED to work for a living. If thats working for VA or PI doing
open source DRI drivers or working for
The fact of the matter is that without funding it will always be difficult
find decent dri drivers for unixes. Nvidia spends alot of money on driver
development and that is why their drivers both perform well and are easy
to install on multiple platforms. You would think that a company like
The Radeon driver has some CP code for 2D that should be easily ported
to the Rage128's CCE engine. Although it only accelerates SolidFill and
ScreenToScreenCopies it should help a lot.
Hmm, maybe it's easy for someone who doesn't touch the dri code for the
first time, but not for me. I've
On Sunday 16 September 2001 23:53, Brian Paul wrote:
Anyway, those are my hunches. I could probably play devil's advocate
and come up with more issues but those are the first that come to mind.
Those are the ones that come immediately to mind whenever I've actually
gotten into frank (no pun
On Mon, Sep 17, 2001 at 12:05:50PM +0200, Gerd Knorr wrote:
to the Rage128's CCE engine. Although it only accelerates SolidFill and
ScreenToScreenCopies it should help a lot.
Hmm, maybe it's easy for someone who doesn't touch the dri code for the
first time, but not for me. I've
On Mon, Sep 17, 2001 at 11:33:25AM +0100, Alan Hourihane wrote:
On Mon, Sep 17, 2001 at 12:05:50PM +0200, Gerd Knorr wrote:
to the Rage128's CCE engine. Although it only accelerates SolidFill and
ScreenToScreenCopies it should help a lot.
Hmm, maybe it's easy for someone who
One thing that would probably be good for r128 and radeon is add the option
back to disable CCE or CP and use the fuller 2D acceleration routines. And
also, if DRI isn't possible for some reason then fallback to the fuller
acceleration routines.
It already works this way: You have either
Dear Gareth,
I realize I used some very bad wording in my previous posts in this thread.
Please bear in mind that I'm not a native English speaker. It wasn't my
intention to flame or even criticize you.
I'll try very hard in this post to bring across what I really want to say, but
I'm afraid
Gareth Hughes wrote:
Mark Allan wrote:
So do we give up on open source drivers completely? I'm willing to bet
that there is some way to generate sufficient revenue to fund the DRI. I
don't know what it is, but it would be worth throwing some ideas around
rather than throwing our
Frank Worsley [EMAIL PROTECTED] writes:
When I get it written up I will post it to the list so everybody can
review it. Once we have made something nice I will either email it
or mail it to the different companies. Hopefully we can archieve
something doing that ... what do you all
Several have suggested that some sort of donation driven effort
be made with which to sustain DRI development.
Personally, I hope the DRI project continues on to be a
successful project, and any efforts by anyone to see it does,
hopefully turn out beneficial.
After reading some people's
On Mon, Sep 17, 2001 at 01:16:49PM -0700, Mark Allan wrote:
[..snip..]
The important thing is to have drivers available from a source you have
some confidence in. If Linus wrote a binary-only kernel module that
provided some functionality you require, would you have faith in it?
Binary only
* Frank Worsley ([EMAIL PROTECTED]) wrote:
[snip]
4. I think we have to also start a more coordinated effort to get specs from
the hardware developers. This weekend I will sit down and try to come up
with a nice document/letter/webpage aimed at management and titled something
like Why open
Will Newton wrote:
On Tuesday 18 Sep 2001 7:35 am, you wrote:
I think it is too early to put a donation page up on the website. Before we
can do anything like that a few important details have to be sorted out ...
What are the odds of the project coming under the XFree86 umbrella?
Note: I posted this on the dri-users list about a week or so ago
and no-one there was able to help me. I'm still not convinced
it's a bug, but I can't figure it out either. Advice would be
appreciated.
Also, everything (DRI, the mga driver, etc) is built into my kernel.
Ok, I
On Tue, 18 Sep 2001, Will Newton wrote:
On Monday 17 Sep 2001 9:16 pm, you wrote:
There's no good reason why you couldn't put an NVIDIA card in a sever
and use the open source 2D driver. You wouldn't want to enable DRI on
you server, either, because of lockup issues.
Look at it
On Tuesday 18 Sep 2001 4:36 pm, you wrote:
Look at it this way: a couple of security holes have been found in the
DRI drivers, and fixed. What's in the nVidia drivers?
What's in any binary application or driver you install?
I don't know. Er, that's my point...
People are willing to use
On Tue, 18 Sep 2001, Will Newton wrote:
On Tuesday 18 Sep 2001 4:36 pm, you wrote:
Look at it this way: a couple of security holes have been found in the
DRI drivers, and fixed. What's in the nVidia drivers?
What's in any binary application or driver you install?
I don't know.
On Tue, Sep 18, 2001 at 01:12:34PM +0100, Will Newton wrote:
What are the odds of the project coming under the XFree86 umbrella? AFAIK the
only reason that DRI was outside of XFRee86 was because it began at PI, and
then when it moved to VA Linux they hosted it on Sourceforge (?).
XFree86
On Mon, Sep 17, 2001 at 11:35:33PM -0700, Frank Worsley wrote:
1. Who is going to take on the leadership position for the project? Although
this is a community project we do need somebody in charge to act as a sort
of project lead and contact person for people outside of the project.
Will Newton wrote:
On Tuesday 18 Sep 2001 4:36 pm, you wrote:
Look at it this way: a couple of security holes have been found in the
DRI drivers, and fixed. What's in the nVidia drivers?
What's in any binary application or driver you install?
I don't know. Er, that's my point...
Mike A. Harris wrote:
After reading some people's postings on donating X amount of
money for feature Y, and the like, I thought about it and come to
the conclusion that donation driven DRI project even partially is
quite unrealistic. I'd like to discuss why I think that is so.
Mike,
Hey everyone,
I have the Rage Pro docs from ATI, I would now like to know *how* I can
get the source of the driver that people are working on currently for this
chip. Also I would like some information on what part of the driver I
need to look at.
Thanks-a-million :)
Andreas
Check the /var/log/XFree86.0.log file again.
It looks like your loading older modules from XFree86 4.0.x rather than
the 4.1.0 ones.
Alan.
On Tue, Sep 18, 2001 at 10:27:05AM -0500, Mark Bainter wrote:
Note: I posted this on the dri-users list about a week or so ago
and no-one there
On Tue, 18 Sep 2001, Ian D Romanick wrote:
Date: Tue, 18 Sep 2001 09:36:13 -0700 (PDT)
From: Ian D Romanick [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii
List-Id: dri-devel.lists.sourceforge.net
Subject: Re: Discussion of donation driven DRI project.
IMHO
On Tue, Sep 18, 2001 at 07:05:59PM -0400, Mike A. Harris wrote:
Daryll, are there dri project private lists I presume that could
be extended to new developers similar to XFree86's developmental
list?
There aren't really any at this point. We discussed most things in
public, and sometimes on
On Tuesday 18 Sep 2001 7:10 pm, you wrote:
Although security through obscurity is not a good solution, it is
effective to a certain degree. To my knowledge, no security holes have
been found in the NVIDIA drivers. They need to be found to be exploited,
and finding them is more difficult w/
On Tue, Sep 18, 2001 at 10:29:03PM -0600, Felipe Contreras wrote:
On Tuesday 18 September 2001 14:41, Andreas Kloeckner wrote:
I have the Rage Pro docs from ATI, I would now like to know *how* I can
get the source of the driver that people are working on currently for
this
chip.
On Tuesday 18 September 2001 19:05, Mike A. Harris wrote:
Very much agreed. This is moreso even for standard XFree86
driver development (2D et al.), and porting old 3.3.6 driver to
4.x.
Yes, I would love to see the CyberBlade on my laptop at least do 2D right
(Working correctly only in
Greetings,
I was compiling the tdfx.o module and I get these errors when I do
a make -f Makefile.linux in the
xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel directory.
make -f Makefile.linux
=== KERNEL HEADERS IN /lib/modules/2.4.2-2/build/include
=== SMP=1
On Tue, Sep 18, 2001 at 10:55:02PM -0400, Frank Earl wrote:
On Tuesday 18 September 2001 19:05, Mike A. Harris wrote:
Very much agreed. This is moreso even for standard XFree86
driver development (2D et al.), and porting old 3.3.6 driver to
4.x.
Yes, I would love to see the CyberBlade
I would like to track which regions of the screen have changed. This
would be of use for something like x0rfbserver which allows remote
access to the local x display.
Has anybody looked into something like this? What docs are availible?
It looks like most of the docs are user level or meant
On Wednesday 19 September 2001 04:42, Alan Hourihane wrote:
What's the problem Frank. I don't believe I've ever had a report from you
on problemsor if you have, can you refresh my memory on what these
problems are...(Oh, and which CyberBlade is it ?)
Never filed a report- had too many
On Wednesday 19 September 2001 14:34, Alan Hourihane wrote:
What about setting another Chipset rather than options ?
Tried all the gamut to see if there was any variation- no such luck with at
least my machine. Win98/Me shows it to be an Ai1 chip, which jives with the
info KDS has available
for what it's worth, there is cyberblade documentation
available at this web site:
http://www.creatis.insa-lyon.fr/~bellet/trident/
Alex
---
On Wednesday 19 September 2001 14:34, Alan
Hourihane wrote:
What about setting another Chipset rather than
options ?
Hello!
It's me again :-)
This time I need to utilize DMA to transfer data from videocard into system
memory (i.e the opposite direction), which is the only way to get decent video
grabbing from ATI AIW (for those who don't know AIW is a videocard with
onboard tv-decoder and other stuff). There
I've got the apg texturing patches applied to my checked out dri tree (trunk)
and I was wondering if they've ever been committed to any branch of the dri
cvs tree? I get the odd problem (programs using dri segfaulting at
indeterminate occasions, corrupted textures, out of memory (null heap
[ CC: to Mark to get the most competent comments on XAA ]
Gerd Knorr wrote:
the indirect buffers aren't flushed often enough. When I move a window
with amiwm, the contents don't move at first. Only when I move it
again do the contents appear in the current place. A quick comparison
I'm going to start getting the 3-5 branch uptodate with current cvs using the
old MesaSrcDir technique. I probably won't commit until Brian releases 4.0
it is merged across, unless anyone would rather I did so sooner. (Doing so
would require people to revert to the MesaSrcDir technique also).
Hello all:
Where are things standing with pcigart support for ATI
Mobility M1 (Mach64)under DRI?
Thanks
Alex DeWolf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Jeff, Rik, Others,
Can you please post a description of what the backwards compatibility kernel
code changes are, how they work, what developers are expected to do to keep
them working?
Has this code/technique been ported to the 3.5 branch? Has that been examined
for feasibility?
Keith
On Thu, 20 Sep 2001, Michel Dänzer wrote:
[ CC: to Mark to get the most competent comments on XAA ]
Gerd Knorr wrote:
the indirect buffers aren't flushed often enough. When I move a window
with amiwm, the contents don't move at first. Only when I move it
again do the contents
Hey all,
Sorry this is a little off topic, but I'm thinking of making a mips-based
laptop for my senior design project, and I was considering what video
chipset to use. Does anyone have an opinion on if one of the ATI chips
would be a good choice? Also, does anyone have a guess on my chances of
Mark Vojkovich wrote:
Mark, is there a way to flush DMA buffers after a batch of XAA operations
right now? If not, could it be added easily?
Wrap the BlockHandler and flush there. It gets called before the
X-server goes back to waiting on its file descriptors.
Luckily, the r128
Interesting Concept. The ATI mobility is pretty good, except for the
origional (anything based on mach64). ATI just released the
documentation to Mach64 to a lot of people, so your odds are kinda low
for getting anything else.
MICHAEL M DELANEY wrote:
Hey all,
Sorry this is a little off
On Tue, 18 Sep 2001 11:10:11 -0700 Mark Allan [EMAIL PROTECTED] wrote:
MA They shouldn't have to. But there are users who can. Look at the Utah GLX
MA project - that was necessitated by id software releasing games.
MA
MA Not true. If you knew your history, Dave Schmenk (now at NVIDIA) began
On Thu, Sep 20, 2001 at 10:00:33AM -0600, Keith Whitwell wrote:
I'm going to start getting the 3-5 branch uptodate with current cvs
using the old MesaSrcDir technique. I probably won't commit until
Brian releases 4.0 it is merged across, unless anyone would rather I
did so sooner. (Doing
Keith Whitwell wrote:
Jeff, Rik, Others,
Can you please post a description of what the backwards compatibility kernel
code changes are, how they work, what developers are expected to do to keep
them working?
Here is a quick rundown of how the infrastructure works:
During Xserver startup
On Sat, Sep 22, 2001 at 03:13:23AM +0200, Michel Dänzer wrote:
I've put up an updated version of the patch at
http://master.penguinppc.org/~daenzer/patches/r128-xv-dma.diff
Peter Surda found the bug which caused corruption with some videos, it's
pretty solid now. If noone objects, I'll
Anybody (Brian, Keith?) working on the Mesa-3.5-tree?
I've didn't see any activity for some days/weeks, now.
It would be very nice to see the Mesa-4.0/OpenGL 1.3 stuff comming, soon.
The current Mesa-3.5 stuff crash under UT (all versions) with the Voodoo5
after some seconds. At the beginning
Hi,
I've also been seeing the AMD-761 + radeon total lockup when X starts,
as described in
http://sourceforge.net/tracker/index.php?func=detailaid=221904group_id=387atid=100387
The X server fixes from ATI seem to fix this when running without dri,
but in dri mode, I still see the lockups 75%
Brian Paul wrote:
Here's the deal. The DRI developers, including myself, have been laid-off
from VA Linux. Today (Friday) is my last day.
That's sad. But how the world goes.
Daryll, what are you doing, next?
There's an effort to relocate us to a new organization but it's too early
to
On Sat, Sep 15, 2001 at 07:08:31AM +0200, Dieter Nützel wrote:
That's sad. But how the world goes.
Daryll, what are you doing, next?
Playing golf, riding motorcycles, and generally taking time off. I'm
waiting to see what happens with the relocation, and I'm looking at
other opportunities.
On Sat, 2001-09-15 at 00:25, Dieter Nützel wrote:
ReiserFS may be another problem.
Can't wait for that.
Most wanted, now.
I am working on it, but I am unfamilar with it all.
Are you seeing any specific problems, now? With the latest preemption
patch on 2.4.10-pre9, do you crash? oops?
Am Freitag, 14. September 2001 06:35 schrieb Robert Love:
On Thu, 2001-09-13 at 22:47, Dieter Nützel wrote:
-- ReiserFS may be another problem.
Can't wait for that.
Most wanted, now.
third, you may be experiencing problems with a kernel optimized for
Athlon. this may or may
I was able to successfully make World on this 4.1.99.1 ..
but after make install and reboot the log file shows my
dilemma:
(II) Loading /usr/X11R6-DRI/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.1.99.1, module version = 1.0.0
Module
Keith, Jeff,
I sent a patch for this some time ago to put the Shared Interrupts back
into the i810 driver. It looks to have been included by Gareth in
the head branch. Maybe this didn't get submitted to Linus yet?
-Matt
-Original Message-
From: Keith Whitwell [mailto:[EMAIL
Hey guys. Sorry if this has been addressed...
Just got a fresh laptop, the newly released HP Omnibook 6100.
It has an ATI Radeon Mobility M6 and 1400x1050 display.
4.1.0 detects the chipset but fails to detect panel size and errors
out. Is there a way to manually specify the panel size?
I
Nevermind,
I compiled latest CVS on a stock RH 7.1 box and moved the files over to
the laptop and things work great! Don't have DRI yet configured, but
hoping things will work well there also.
-Troy.
[EMAIL PROTECTED] wrote:
Hey guys. Sorry if this has been addressed...
Ok, I've been trying for days to get this sucker working. Here's all the
important info I can think of:
Running RH 7.1, clean install, everything installed from both discs.
ASUS A7V motherboard
Kernel 2.4.2-2
ATI Radeon 64Mb DDR VIVO card
Here's what X spewed into a log file (well, the
On Mon, 24 Sep 2001 21:49, you wrote:
Ok, I've been trying for days to get this sucker working. Here's all the
important info I can think of:
Running RH 7.1, clean install, everything installed from both discs.
ASUS A7V motherboard
Kernel 2.4.2-2
ATI Radeon 64Mb DDR VIVO card
Here's what
Hi,
I have been running the X 4.1 release for a while now and quite frequently
it has hard locked my box. In a solution to this i decided to upgrade to
the DRI-CVS, however when making World it ends with the following error.
/usr/i386-slackware-linux/bin/ld: cannot find -lXau
collect2: ld
I have been running the X 4.1 release for a while now and
quite frequently
it has hard locked my box.
Sorry, but you dont mention what hardware and software you are using.
So far i found the current XFree86 core rather stable myselves.
In a solution to this i decided to upgrade to
the
On Mon, 2001-09-24 at 12:49, Frank Jacobberger wrote:
Symbol mcount from module /usr/X11R6-DRI/lib/modules/fonts/libbitmap.a
is unresolved!
I got the same error this weekend when I compiled the DRI trunk from
cvs. I'd also like to know how to fix it.
Regards,
matt
--
Matt Matthews \
From slashdot:
3Dlabs is trying to drive the graphics interface away from hardware
specific extentions, as seen in DirectX. Instead, they are proposing an
open (no NDA) dialog on OpenGL 2.0. The guidelines mention
good-ol-fashioned platform independence (linux included) and emphasis on
El Mar 25 Sep 2001 07:27, escribiste:
On Sun, 23 Sep 2001, Manuel Teira wrote:
Perhaps we should work with the latest DRI trunk. Do you think it worth
the effort?
It seems that most of the changes I noticed have been in the drivers for
the newer cards, but I haven't really looked at it
On Tue, 25 Sep 2001, Alexander Stohr wrote:
Date: Tue, 25 Sep 2001 12:49:25 +0200
To: [EMAIL PROTECTED]
From: Alexander Stohr [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: RE: [Dri-devel] No Subject
I have been running the X 4.1 release for a while now and
quite frequently
it
Hey guys,
Not sure if you guys are using a beta version of redhat or any other
setup using a 2.96+ release of gcc, but if so...
It seems they are implementing a new optimization that is on by default
in the compiler that doesn't allow symbols to be resolved correctly in
the X
Hi,
Is there a known bug in the mga driver resulting in tribes2 switching
between SW and HW rendering on my G400 DH? All games patches seem to
be similar, latest one installed is #23669. Any options to set to run
fully in HW?
If not, is compiling from DRI CVS solving the problems?
Other games,
Troy A. Griffiths stated:
The host.def settings are:
/*
* The following changes are required in order to disable gcc's new
* 'merge-constants' optimization, because the XFree86 module loader is
not
* yet aware of the new ELF sections it produces, and will cause module
* loading to fail.
Svante Signell wrote:
Hi,
Is there a known bug in the mga driver resulting in tribes2 switching
between SW and HW rendering on my G400 DH?
yes, this is known.
All games patches seem to
be similar, latest one installed is #23669. Any options to set to run
fully in HW?
not without
On Wed, Sep 26, 2001 at 10:31:06AM +0200, Svante Signell wrote:
Hi,
After downloading the DRI CVS and following the instructions on the
web pages to build the DRI part and using /usr/X11R6-DRI as project
root, the installed X libraries and header files are not found:
cd
From: Angel [mailto:[EMAIL PROTECTED]]
In a solution to this i decided to upgrade to
the DRI-CVS, however when making World it ends with the
following error.
/usr/i386-slackware-linux/bin/ld: cannot find -lXau
collect2: ld returned 1 exit status
make[4]: *** [XFree86] Error
After upgrading my kernel from 2.4.9 to 2.4.10 and recompiling the mach64
drm module, I start X and get an oops. The X log looks as though all
setup has completed, all the way through the keyboard/mouse setup. The
box locks up, but I can ssh in and run ksymoops on the syslog. The
decoded oops
On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
From: Angel [mailto:[EMAIL PROTECTED]]
In a solution to this i decided to upgrade to
the DRI-CVS, however when making World it ends with the
following error.
/usr/i386-slackware-linux/bin/ld: cannot find -lXau
David Dawes wrote:
On Wed, Sep 26, 2001 at 08:37:38PM +0200, Alexander Stohr wrote:
From: Angel [mailto:[EMAIL PROTECTED]]
In a solution to this i decided to upgrade to
the DRI-CVS, however when making World it ends with the
following error.
/usr/i386-slackware-linux/bin/ld: cannot find
Hello people!
I was just wondering, what's the plan regarding
Radeon 8500 DRI support?
I been hearing rumors about ATI switching to
a unified driver structure much like Nvidia's.
Can anyone verify wether this is true or not,
and if it is true, how it will affect the DRI project?
On Thu, 27 Sep 2001, Dacobi Coding wrote:
Hello people!
I was just wondering, what's the plan regarding
Radeon 8500 DRI support?
I been hearing rumors about ATI switching to
a unified driver structure much like Nvidia's.
Can anyone verify wether this is true or not,
and if it is true,
On Wed, 26 Sep 2001, Frank Jacobberger wrote:
/*
* The following changes are required in order to disable gcc's new
* 'merge-constants' optimization, because the XFree86 module loader is
not
* yet aware of the new ELF sections it produces, and will cause module
* loading to fail. -
On Fri, 28 Sep 2001, Carl Busjahn wrote:
Date: Fri, 28 Sep 2001 11:30:11 -0400
From: Carl Busjahn [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format=flowed
List-Id: dri-devel.lists.sourceforge.net
Subject: Re: Re: Radeon 8500, what's the plan?
I have to
Does current i810 drm accelerate 2D path?
I get about 6mln pps in drawpix :(
Michael
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
The DMA buffers and the frame buffer are in
a
unified memory pool, so it isn't any quicker to put the data into DMA
and
then have hardware upload it. Very little consumer hardware provides
support
for the operations necessary to implement much of drawpixels anyway.
what about
Michael Zayats wrote:
what about glPixelsZoom? I would have been very pleased to see it hardware
accelerated...
when the pixmap wont change i would load it as a texture
and draw it as a quad.
if its changing use gltexsubimage to update it. i dont think its a
special path
for the 810
On Sun, Sep 30, 2001 at 10:09:47PM +0200, Marcelo E. Magallon wrote:
| Is it really a pure hardware problem? Rumors on comp.graphics.opengl
| are that the vendors don't invest time optimizing that path (in the
| driver) because there's not much demand for it. ...
Most consumer-level
On Thu, 2001-09-20 at 22:52, Michel Daenzer wrote:
Log message:
flush indirect buffer in the BlockHandler
Modified files:
xc/xc/programs/Xserver/hw/xfree86/drivers/ati/:
r128_driver.c
I just noticed that the radeon driver doesn't do this yet - does it work
well with
Hi,
I'm interested in the mach64 driver work and would like to help.
Utah-GLX and Xfree 3.3.6 never worked on my machine, so I decided to
upgrade to Xf 4.1.0.
At the moment, I know just very little about video hardware, but if
someone could point me in the right direction...
Jens
Hey all,
I too am interested (but my guess is a lot of people are, this mailing
list is probably getting flooded with requests) in the Mach64 DRI. I
checked the CVS but couldnt find a trace of it. Heard some rumors a few
people where developing it in their spare time, but i don't know if
their
Hey,
ATI has not been very cooperative with letting the documentation out,
but they may be now, it took them a month to get the documentation to
me, and by then School had started :-( There is a cvs branch for mach64
almost a year old which I have used with limited succes (some gl demos
I'm using the kernel module from 2.4.10. Everything else is from the
Slackware 8.0 release. XFree86 4.1.0 and a Radeon AIW graphics card.
- Original Message -
From: Michel Dänzer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 30, 2001 10:24 AM
Subject: Re: [Dri-devel]
601 - 700 of 46322 matches
Mail list logo
