I'd be willing to donate to support DRI development.
I'd even be willing to donate a substantial amount
assuming it would guarantee some results. Maybe a
project like this would catch the eye of the HW
vendors and prompt them to put more effort into
opensource drivers.
Alex
-
Dear
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 ?
Does anyone have any news on support for iDCT and
Motion-Compensation or any of the video related
features of the radeons? Do the reference drivers
from ATi have anything for these features? Just
curious.
Thanks,
Alex
---
Jose Fonseca wrote:
On Mon, 2002-01-28 at 14:17,
Yeah the iDCT/MC stuff was what I was talking about.
Have they released the specs for this part of the
chips to developers so that an open source version may
be possible at some point?
Thanks for the information,
Alex
--- Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Wed, 30 Jan 2002,
I'm not sure they are the official maintainers, but as far as I
recall,
Thomas Winischhofer has done a lot with Sis and DRI, etc. (like make
the driver actually work) (http://www.webit.com/tw/linuxsis630.shtml),
and Matthew Sottek has done much of the work for i810/830.
Alex
I just saw over at the utah-glx project that the S3 savage 3D driver is
working with XF 4.x. It's not DRI, but for those who are interested, I
thought I'd point it out... maybe a good start for those looking to
port to the DRI.
Alex
__
Do You
I don't think the docs are much help with regard to 3D. there actually
is a working sis DRI driver for 300 series chips that can be found
here:
http://www.winischhofer.net/linuxsis630.shtml
perhaps it could be synced up to the current DRI tree.
Alex
Might want to post
I'm pretty unfamiliar with OpenGL programming. I have an idea for an
xfree module that I suspect would not be too hard to implement, but I
wanted to get some other opinions on it. What I'd like to do is create
a module called perhaps ogl-xv or glx-xv that would provide a generic
Xv adapter on
On Mon, 2002-09-30 at 22:14, Alex Deucher wrote:
I'm pretty unfamiliar with OpenGL programming. I have an idea for an
xfree module that I suspect would not be too hard to implement, but I
wanted to get some other opinions on it. What I'd like to do is
create
a module called perhaps ogl
yeah xawtv has an opengl plugin as well. I'll take a look if I ever
get a chance to. thanks for the suggestion.
Alex
--- Stefan Lange [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
I'm pretty unfamiliar with OpenGL programming. I have an idea for
an
xfree module that I suspect would
I'd be interested in helping out with the savage work. I don't know
much about the DRI, but I can help test. I'm actually working (slowly)
on adding dual head (duoview) support to the savage driver for the
mobile savages. I've started on the code, but I've been so busy lately
that I've had no
Dave you might try the DRI ML if this is about 3D acceleration. (i've
cc'd the list)
Alex
---
hi i sent you an email some time ago but have not got any reply
i need some help FAST! as the driver is now veary close to ready !!
can you let me know even if some one
I saw this posted on the dmx-devel (dmx.sf.net) ML today. Is anyone
familiar with the GLX proxy work? does it work with the DRI? Could
this be a solution for HW accelerated indirect rendering? what's teh
status of GLX Proxy and DMX? I'm very interested in it; also in
conjunction with DMX.
questions on the DMX list. Let's keep the
discussion
there (or at least cc the DMX list) so that people on the DMX list
don't miss out.
DMX, GLXProxy and Chromium really don't have anything to do with the
DRI in
particular.
-Brian
Alex Deucher wrote:
I saw this posted on the dmx
I too am curious about that. I've been working on adding duoview
support to the s3 savage driver. I talked to Tim Roberts a while back
and I figured out the basics of how it works. I've got a semi-working
driver, but alas, I think I need some help getting the second crtc to
output to the vga
I too am curious about that. I've been working on adding duoview
support to the s3 savage driver. I talked to Tim Roberts a while back
and I figured out the basics of how it works. I've got a semi-working
driver, but alas, I think I need some help getting the second crtc to
output to the vga
--- Sven Luther [EMAIL PROTECTED] wrote:
On Mon, Feb 24, 2003 at 01:28:15PM -0800, Alex Deucher wrote:
right now for these chips you set up the entity as shareable and
then
divide your framebuffer into two or more frambuffers, one for each
CRTC. Each instance of the driver then works
--- Linus Torvalds [EMAIL PROTECTED] wrote:
On Wed, 26 Feb 2003, Sven Luther wrote:
Yes, and you have to divide the fb memory in two, one for each
head, or
something such, and each head will have its separate offscreen
memory
manager, possibly using different screen strides.
Side
I'd be very interested in seeing your code, hacky or not. We were
actually just discussing this on this list and on the devel list at
xfree86.org. David Dawes said he has some preliminary work for setting
up multiple viewports into a single framebuffer. Sven Luther and
myself, among others,
Gabucino,
Do you know if either plugin uses MESA_ycbcr_texture? this would
avoid the need for you to convert YUV data to RGB in order to render it
as a texture. Should speed things up of OGL. when I looked at the
xine plugin source, it did not support this. For systems that do not
support
I've been thinking of trying to implement an XV adapter using OpenGL
and MESA_ycbcr_texture for YUV or regular RGB textures for RGB video.
This would not only provide a default Xv adapter (in the event that the
hw didn't have one) or it would provide hw accelerated video playback
on hw that
perhaps it would be better to just write opengl output plugins for
video applications that used MESA_ycbcr_texture. However, looking at
the code for several video apps, most that have an OGL output still use
RGB textures with the the YUV-RGB conversion done in software.
Alex
--- Keith Whitwell
whoops... I meant to replay to all...
--- Keith Whitwell [EMAIL PROTECTED] wrote:
Not sure I quite understand you - but definitely changing those apps
to use
the Mesa extension (if available) would be a win.
They convert the YUV frames to RGB in software and then display them as
OGL
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Michel
Dänzer
Sent: Tuesday, June 03, 2003 12:42 AM
To: Alex Deucher
Cc: Keith Whitwell; [EMAIL PROTECTED]
Subject: Re: [Dri-devel] [RFC] New Xv adapter using
MESA_ycbcr_texture
On Tue, 2003-06-03 at 00:09, Alex Deucher wrote:
perhaps
I've had several reports of DRI not working after a screen resize using
mergedfb code. I haven't really had time to tackle it, and
unfortunately, i'm not real familiar with how DRI interacts with a mode
change or xrandr. I was hoping someone on this list could point me to
where to look for DRI
BTW, bugzilla reference for this feature is here:
http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=276
Please test and post any comments or issues.
Thanks,
Alex
---
The attached patch adds mergedfb support (a single framebuffer with two
viewports looking
--- Michel D�nzer [EMAIL PROTECTED] wrote:
On Wed, 2003-06-11 at 21:47, Alex Deucher wrote:
I've had several reports of DRI not working after a screen resize
using
mergedfb code. I haven't really had time to tackle it, and
unfortunately, i'm not real familiar with how DRI interacts
The attached patch adds mergedfb support (a single framebuffer with two
viewports looking into it) to the radeon driver. the options are
consistant with the sis and mga drivers. I've also replaced the old
clone mode with the clone mode supplied by the mergedfb code. It's
behavior follows that
I've looked through the code and all the DRILock() and DRIUnlock() seem
to be right. the only things that stands out as potentially suspicious
is in RADEONAdjustFrame():
void RADEONAdjustFrame(int scrnIndex, int x, int y, int flags)
{
ScrnInfoPtrpScrn = xf86Screens[scrnIndex];
Ah... good eye. I'll give that a try. thanks for the help.
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Mon, 16 Jun 2003 10:21:20 -0700 (PDT)
Alex Deucher [EMAIL PROTECTED] wrote:
I've looked through the code and all the DRILock() and DRIUnlock()
seem
to be right. the only
I just wanted to thank you guys for your help. That fixed the bug!
see the latest updates here:
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=276
Thanks!
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
Disclaimer: I don't have any experience with multi-head
configurations.
For what it's worth I'm seeing the same behavior on my m6 using Xfree86
CVS from a couple weeks ago. I have to rmmod radeon to and restart X
to get 3D to work. same messages in my log file.
Alex
---
José Fonseca wrote:
(II) RADEON(0): [drm] created radeon driver at busid
on
good
time. When I have something worth to test I'll make some snapshots
from
this branch too.
Jos#233; Fonseca
On Fri, Jun 20, 2003 at 03:41:03AM +0200, Paul Heldens wrote:
I'm experiencing the same.
On Wed, 2003-06-18 at 16:16, Alex Deucher wrote:
For what it's worth I'm
Alan,
I don't suppose they released any code or docs for duoview support
for the old savage chips? I tried to add support for that a while
back, but never was able to get it to work.
Alex
--- Alan Cox [EMAIL PROTECTED] wrote:
On Llu, 2003-06-23 at 13:33, Alan Hourihane wrote:
No
Plus XvMC!
--- José Fonseca [EMAIL PROTECTED] wrote:
Savage: Savage MX/IX/ SuperSavage/ ProSavage/ Twister/K
It seams that at the moment DRI is only enabled for the Twister and
ProSavage:
if ((psav-Chipset == S3_TWISTER)
|| (psav-Chipset == S3_PROSAVAGE)) {
/* Setup
I don't know about the 3D stuff, but the 2D driver seems cleaner and
easier to follow than the current one (which this new one seems to be
based on) at first glance anyway...
Alex
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alan Hourihane wrote:
On Mon, Jun 23, 2003 at 01:50:02PM +0100, Alan
I have a t20 I can test on as well. I also plan to re-attempt dualhead
support using the new code as a base.
Alex
--- Alan Hourihane [EMAIL PROTECTED] wrote:
On Mon, Jun 23, 2003 at 10:21:30AM -0700, Ian Romanick wrote:
Alan Hourihane wrote:
On Mon, Jun 23, 2003 at 01:50:02PM +0100, Alan
what about https://savannah.nongnu.org/
Alex
--- Martin Spott [EMAIL PROTECTED] wrote:
Jos? Fonseca [EMAIL PROTECTED] wrote:
If not then the solution would imply moving the CVS repository to a
new
machine, but where would that be? XFree86.org? Some SF look-a-like?
As far as I know
CVS at sourceforge is using the backup server which has data that is
24+ hours old. I wasn't able to get it either.
Alex
--- Maximo [EMAIL PROTECTED] wrote:
At 09:13 AM 24/6/2003, you wrote:
On Tue, Jun 24, 2003 at 06:00:57PM +0600, Dimitry N. Naldaev wrote:
В сообщении от 24 Июнь 2003
once the agpgart stuff is in place I don't imagine it'll be that hard
to add DRI support to the radeon/r200 driver. I think the IGP chips
are pretty similar to their counterparts with dedicated memory. if the
9100IGP is anything like a 9200 it should work with the r200 driver
with a little work
I just saw this on extremetech today:
http://www.extremetech.com/article2/0,3973,1101038,00.asp
Looks like SiS is spinning off it's graphics chip division. perhaps
this could mean better access to databooks!
time will tell I suppose.
Alex
__
Do you Yahoo!?
SBC
I don't know what's involved in making the DRI work on multiple
physical graphics cards, but if you want HW accelerated 3D on a
dualheaded radeon card check out my mergedfb patch:
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=276
I'm not sure you'll be able to get dual independant 3D
thru the mergedfb patch code
asap. I think your idea of sharing one framebuffer as 2 virtual fb's
could work...thanks!
-dean andreakis
-Original Message-
From: Alex Deucher [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 3:27 PM
To: Andreakis, Dean (MED); [EMAIL PROTECTED
--- Alan Cox [EMAIL PROTECTED] wrote:
On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
The savage-1_0_0-branch wont work until the 3D driver is fixed up
for
Mesa 4.x - it's still based on Mesa 3.4.
Is there any good info on doing this since the CLE266 driver has the
same problem
and virge too possibly :) Speaking of which if anyone wants a virge
board for testing/porting, I've got an old GX (and possibly a DX as
well) sitting around.
Alex
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alan Cox wrote:
On Gwe, 2003-06-27 at 18:42, Alan Hourihane wrote:
The
The DMX (distributed multihead X) project has support for the GLX
extesion using some code from SGI called GLXproxy. I'm not familiar
with how it works exactly. Could this code be used to add support for
DRI for multiple video cards in the same machine? Or perhaps indirect
rendering? like
--- Richard F Weber [EMAIL PROTECTED] wrote:
So I guess my next questions are: 1) is the 2048x2048 a HW
limitation, or a SW/implementation limitation
AFAIK the maximum size of the GL context is a hardware issue.
However,
it shouldn't matter where it is displayed, that is it should
2D support (just chip IDs) was recently added to xfree86 CVS. You can
download that and test it or grab a pre-compiled binary here:
http://www.xfree86.org/~alanh/
For 3D support you have to use Ati's binary driver.
Alex
--- Matthew Caron [EMAIL PROTECTED] wrote:
Whom do I contact about Radeon
--- Michel Dänzer [EMAIL PROTECTED] wrote:
The comments regarding this code are a bit sparce and seem to imply
that the support was added for clone mode. Mergedfb works
similarly to
clone mode, however there are some differences; for instance if you
have two heads side by side. 3D
Some tips for those of you messing with the savage driver.
Alex
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com---BeginMessage---
Here are some hints on how to build the VIA/S3 Savage driver. You need to
make a couple of
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Sat, 2003-07-12 at 00:24, Alex Deucher wrote:
--- Michel Dnzer [EMAIL PROTECTED] wrote:
3D seems to work pretty well in mergedfb mode, but there are a
few
little issues,
Can you elaborate on these?
They are mentioned here
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Mon, 2003-07-14 at 00:34, Alex Deucher wrote:
--- Michel Dnzer [EMAIL PROTECTED] wrote:
On Sat, 2003-07-12 at 00:24, Alex Deucher wrote:
--- Michel Dnzer [EMAIL PROTECTED] wrote:
3D seems to work pretty well in mergedfb mode
--- Michel D#228;nzer [EMAIL PROTECTED] wrote:
On Mon, 2003-07-14 at 02:59, Alex Deucher wrote:
--- Michel Dnzer [EMAIL PROTECTED] wrote:
On Mon, 2003-07-14 at 00:34, Alex Deucher wrote:
however, the framebuffer on crtc1 is still shifted a few pixels
to
the left when you run
For those of you looking to do 2 screens of 1280x1024, you can always
to an over/under config (1280x2048) that should get around the 2048
limit. not optimal, but...
Alex
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
Speaking of agp, what would be needed to add apg 8x support to the
radeon driver? does the value of 'apgmode' just get passed on to the
agpcode? I'd imagine there might be some bits to flip on the radeon.
Alex
--- Dave Jones [EMAIL PROTECTED] wrote:
Folks,
Any comments ? The linkage
thats what I meant :)
--- Dave Jones [EMAIL PROTECTED] wrote:
On Mon, Jul 14, 2003 at 09:04:33AM -0700, Alex Deucher wrote:
Speaking of agp, what would be needed to add apg 8x support to the
radeon driver? does the value of 'apgmode' just get passed on to
the
agpcode? I'd imagine
--- Michel D�nzer [EMAIL PROTECTED] wrote:
Ah yes... my algebra skills are getting rusty... yes, they are
equilvalent. now the question is, should they be (I assume so)?
Yes.
I'm not sure how pageflipping is supposed to work.
The idea is that the DRM should preserve the
This proposal comes up periodically on this and other xfree lists, but
never really goes anywhere. Why not raise money from the open source
community to fund open source driver development? everything from
revamping X (ie, speeding up the development of 5.0 features) to adding
a new Xfree86 3D
What about tungsten graphics or Providenza Boekelheide, Inc. (Tim
Robert's company? Plus I'm sure there are other small development
companies that would be interested.
Alex
--- Mark Vojkovich [EMAIL PROTECTED] wrote:
On Tue, 15 Jul 2003, Alex Deucher wrote:
This proposal comes up
Support for HW accelerated indirect rendering is just a matter of
restructuring some library interfaces so that GLX commands can get
decoded and sent to the hardware rather than the sw renderer. It's in
the pipeline for future development by the DRI folks, but if it were
sponsored, it might
the code S3/VIA released was against xfree86 4.2.0. several people
have built the source against 4.2.0. check tim roberts' savage mailing
list archive for instructions
(http://www.probo.com/mailman/listinfo/savage40 ). I don't think the
initial driver drop enabled hw acceleration on savage
For those that are interested, I just wanted to mention that I've
posted new versions of my radeon mergedfb patch and my radeon
powermanagement patch. Please see bugzilla for more details. Binaries
and diffs are available on my website (listed on bugzilla).
Mergedfb:
There was a discussion about posting multiple radeon cards on the devel
and xfree86 MLs just before 4.3.0 was released (feb 2003). Marc and
Hui and several others were involved. If you can find the thread, it
might help you out.
http://marc.theaimsgroup.com/?t=10430550602r=1w=2
You might also be able to use Xv and just take snapshots of your
radeon desktop and send them to the Xv adapter on the card driving the
panel. much like how a tv cards sends video data to the Xv adapter
using offscreen images. There might be limitations on bandwidth and
the size of the overlay
Is a tree merged planned anytime soon? The 2D driver is getting
substantially different from the old one in the DRI tree. There are A
LOT of fixes in the xfree tree that many users of newer cards need to
have xfree work at all. Plus, if we want to merge the IGP 3D support,
that depends on the
there is a driver option in your config file to choose how much ram you
want to use for your adapter. I don't remember what it is off hand.
Alex
--- Dimitris Zilaskos [EMAIL PROTECTED] wrote:
Hello
I am using i830-20030820-linux.tar.bz2 on redhat 9 , p4 system 512
ram
intel
Some of the Xv code in CVS got put into mi* so you may need a new
'XFree86' binary.
Alex
--- Michel D�nzer [EMAIL PROTECTED] wrote:
On Mon, 2003-08-25 at 00:24, Felix Kühling wrote:
On Sun, 24 Aug 2003 10:06:04 +0200 (CEST)
Korosi Akos [EMAIL PROTECTED] wrote:
I have been off for a
There are no sis docs available for any thing newer than the 6326 as
far as I know (the 6326 docs were on the dri downloads page for a
while). There is also a utah-glx driver for the 6326.
Sis wrote the DRI driver for the 300 series, but I don't think they
ever released databooks for it. They
there are docs for the 300 series on utah-glx, but they are 2D only it
looks like:
http://sourceforge.net/project/showfiles.php?group_id=1098release_id=77440
Alex
--- Eric Anholt [EMAIL PROTECTED] wrote:
As some of you have heard, I'm working on getting the SiS DRI working
again. It's been
If memory serves, I believe radeon_probe.c gets compiled into ati_drv.o
so you'll need a new ati_drv.o as well.
Alex
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Tue, 2003-08-26 at 10:12, Korosi Akos wrote:
Michel Dänzer [EMAIL PROTECTED] Ãrta:
The latest working snapshot is
I'd be interested in this project. I beleive there was a project a
while back that did something like this using xnest. it was called
transluxent and was kind of a hack.
http://www.stud.uni-karlsruhe.de/~unk6/transluxent/
Also, speaking of pbuffers, Alan Cox mentioned that he a received a
code
--- Michel D�nzer [EMAIL PROTECTED] wrote:
On Thu, 2003-08-28 at 16:31, Alex Deucher wrote:
On a related note, I've been thinking about alternative ways to
implement mergedfb on radeon hardware. what if instead of creating
a
single framebuffer with two viewports, we stuck with the old
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Michel D�nzer [EMAIL PROTECTED] wrote:
The difference is that the 2D engine is only used by the X server,
whereas the 3D engine is used by every 3D client, and the 3D driver
still assumes that the locations of the front
you only need to update ati_drv.o if you make changes to radeon.h or (I
think) radeon_probe.h/c
Alex
--- Korosi Akos [EMAIL PROTECTED] wrote:
Hi all
Finally!!! It works
Thanks to everyone who helped with this work!
Expecially to Felix!
I have just one more question:
do I need
XvMC is an extension for Xvideo that does things like motion
compensation and iDCT in hardware. I'm not sure if that has anything
to do with your problem. Also I'm not sure if the savage mx/ix cards
even have hw motion comp, etc. that might have been added in the
savage4 and 2000 cores.
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Sat, 2003-08-30 at 13:06, Jouni Tulkki wrote:
Is there a way to make moving images and textures to video memory
faster?
Currently I'm using Radeon 9500 Pro and AGP 8x.
Curious, how do use AGP without the DRI being enabled? :) (And how 8x
I have two questions for you about the radeon driver.
the first relates to the CP and accel. I'm attempting to convert the
Xv code to use the CP. how do you check to find out if the driver is
using CP or MMIO accel? I considered using
info-directRenderingEnabled, but as far as I can see the
the open source radeon Xfree drivers do not support tv out yet. You
might check with the GATOS people (http://gatos.sf.net). it works in
the console because the BIOS is driving the outputs rather than the
driver.
Alex
--- Chris Ison [EMAIL PROTECTED] wrote:
I'm wondering if there is a way to
Linus,
Some dell OEM radeon cards offered Dual DVI ports and I believe there
are some other oems (tyan?) that will be offering Dual DVI cards. the
radeon 9000s and newer only have one tdms trandsmitter built in, but an
additional external one can be added on to drive the second DVI port.
for
I think it worked in the past, but I think something got broken
recently. I've seen several reports of it being broken recently on the
xfree MLs. there are some bugs for it on xfree bugzilla.
Alex
--- Linus Torvalds [EMAIL PROTECTED] wrote:
Is Xv output supposed to work on i830-based
An card from the 300 series sis cards should work:
300, 305, 540, 630/S/ST, 730
Alex
--- Martin Spott [EMAIL PROTECTED] wrote:
Eric Anholt [EMAIL PROTECTED] wrote:
If anyone wants to test, [...]
Which video card would you recommend for trying ? I'd see if I can
get
one,
Martin.
--
This is probably better asked on dri-devel (cc:ed).
--- Cheshire Cat Fish [EMAIL PROTECTED] wrote:
I am investigating supporting DRI and OpenGL for the Silicon Motion
driver.
I'm new to both of those, so some of these may be newbie sounding
questions.
1) I have the OpenGL code from the
PROTECTED] wrote:
--- Alex Deucher [EMAIL PROTECTED] wrote:
2) access ROM directly instead of relying on copy
in low RAM. This allows multiple cards. Required
MPP_TB_CONFIG fix in driver.
Is this patch necessary for xfree86? It may address
some of the issues
in the email threads I
Dualhead...
Right now there is dualhead support for the following cards in xfree86:
radeon
matrox
sis
via
chips
3dlabs (Sven mentioned that he had this quasi-working on the newer
cards, although I don't know the state of his driver)
The following cards have hw dualhead support, but no driver
--- Jon Smirl [EMAIL PROTECTED] wrote:
Hopefully these is the last versions. They implement:
1) add every know PCI ID
2) access ROM directly instead of relying on copy in
low RAM. This allows multiple cards. Required
MPP_TB_CONFIG fix in driver.
Is this patch necessary for xfree86? It may
) for a while with 630s as well. you can still find
300/305 PCI/AGP cards on some websites usually labeled as sis 305
32mb or similar.
Alex
--- Martin Spott [EMAIL PROTECTED] wrote:
Alex Deucher [EMAIL PROTECTED] wrote:
Eric Anholt [EMAIL PROTECTED] wrote:
If anyone wants to test
from the log:
idr To do that we're going to port the *OLD* 500TX driver to DRI.
:)
anholt 500tx is a what?
idr anholt: The GLINT before the MX.
...
idr anholt: It should be *much* faster. The Delta does all the
geometry setup. This is the mode the current gamma driver uses.
anholt hmm
idr Part
The 2D driver supports all savage chips, but the 3D driver seems to
only support the Prosavage and Twister (savage4 core) integrated chips:
from savage_driver.c:
if ((psav-Chipset == S3_TWISTER)
|| (psav-Chipset == S3_PROSAVAGE)) {
/* Setup DRI after visuals have been
--- Ian Romanick [EMAIL PROTECTED] wrote:
I'm aware of Sven's work, and I have been in contact with him. I
haven't persued getting docs form 3dlabs yet, but I may do so in the
future. IBM's lawyers are *VERY* picky, so getting docs under NDA
for
use in open-source projects is *VERY*
Is there a web based CVS viewer on freedesktop.org like there is on
xfree86 or sourceforge? I personally find it useful when I don't have
access to my PC. it's also nice for reference.
Alex
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site
--- Keith Whitwell [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
looks like the post size limit ate my first attempt to post this.
Anyway, I was finally able to access DRI cvs (from
dri.freedesktop.org), so I pulled the latest tree and created a
radeon
mergedfb patch against it. I've
Eric,
Now that you are finishing up the sis 300 series DRI port, how hard
would it be to add support for the 6326? there were databooks for it
flaoting around and there was a utah-glx driver as well. It's a pretty
basic 3D engine; it's it similar to the 300 series, it might be trivial
to add
Factoring it out is not a problem. the question is what to do with it
when I pull it out. create an external external libray like
libXMergedFB.so or something like that? what's the preferred method?
any existing examples I can look at?
Alex
--- Michel Dänzer [EMAIL PROTECTED] wrote:
As a
--- Alan Cox [EMAIL PROTECTED] wrote:
basic 3D engine; it's it similar to the 300 series, it might be
trivial
to add support, but then again, I'm not too familiar with sis
hardware
internals.
I actually took a brief look. The 6326 is a simple PIO engine that
needs
triangles fed it
at the moment I guess I'm
inclined to agree. thoughts?
Alex
--- Michel D�nzer [EMAIL PROTECTED] wrote:
On Wed, 2003-09-10 at 15:46, Alex Deucher wrote:
It seems like a lot of cards have this type of capability and
lots of
drivers are doing this somewhat independently of one another
How about a mergedfb branch if not the trunk? I'm pretty good about
keeping things up to date. I'm not yet an expert with CVS, but it
won't take long ;)
Alex
--- Alexander Stohr [EMAIL PROTECTED] wrote:
you would wonder how other developers could enjoy having
a look on your updates at the
S3/VIA released the source to their 2D/3D/XvMC driver that was based on
xfree86 4.2.0. it has not yet been ported to 4.3.0. if you don't mind
using 4.2.0, you can find instructions on how to build and install
their driver here:
http://probo.probo.com/pipermail/savage40/2003-July/41.html
Are you sure have mergedfb set up correctly? 3D should work on both
heads, not just one. check the man page for all the mergedfb options:
http://www.botchco.com/alex/radeon/mergedfb/cvs/DRI/final/radeon.4.html
Are you using pageflipping? If so, turn it off. it has some issues in
certain modes
Is anyone on either of these lists familiar with XGI? It seems to be a
new GPU manufacturer consisting of a merger of Trident and the SiS
graphics division.
here's their website:
http://www.xgitech.com/index.htm
They have some interesting products products (dual GPU solution). Some
of their
the linux driver, which is release
with
Linux OS, for almost all their own chips.
-Original Message-
From: Alex Deucher [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 5:30 PM
To: Thomas Winischhofer; [EMAIL PROTECTED]
Cc: Alex Deucher; [EMAIL PROTECTED]; [EMAIL PROTECTED
1 - 100 of 1146 matches
Mail list logo
