--- Dave Airlie [EMAIL PROTECTED] wrote:
mach64. I'd do the same with savage.
Either way, seeing as the driver would be in the Mesa trunk, DRI
branches
don't seem to make much sense anymore to me, unless it's for work
on GLX
like the work Ian's doing.
The whole point of DRI
--- Tim Roberts [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Felix Kühling [EMAIL PROTECTED] wrote:
3. Separate commands and data
Right now commands and data are submitted to the chip as one data
stream, either via the BCI or via DMA buffers. For easier security
checking
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
DPMS never worked on my notebook with ProSavageDDR. The problem is
that
the register that controls HSync and VSync signals of the CRT doesn't
have any effect on the LCD display. The attached patch disables the
LCD
display via the bios if the
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
DPMS never worked on my notebook with ProSavageDDR. The problem is
that
the register that controls HSync and VSync signals of the CRT doesn't
have any effect on the LCD display. The attached patch disables the
LCD
display via the bios if the
--- Chris King [EMAIL PROTECTED] wrote:
Hello,
I've successfully gotten 3D rendering working with my ProSavage DDR
chip
using the savage-2-0-0 CVS from 2004-21-02, but I've encountered a
couple of problems:
1) 2D rendering is EXTREMELY slow. Almost as if it were using the
Vesa
CVSROOT: /cvs/dri
Module name: xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/22 08:14:43
Log message:
Merged the DRI-enabled Savage 2D driver from the
savage-2-0-0-branch into the trunk.
Modified files:
Felix,
I just updated my mesa tree and the savage driver does not seem to
be there. I thought you had moved it over? The DRI tree updated fine.
Am I missing something?
Alex
__
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
Felix,
I just updated my mesa tree and the savage driver does not seem to
be there. I thought you had moved it over? The DRI tree updated fine.
Am I missing something?
Alex
__
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
Nevermind... I figured it out.
Sorry for the spam.
Alex
--
Felix,
I just updated my mesa tree and the savage driver does not seem to
be there. I thought you had moved it over? The DRI tree updated fine.
Am I missing something?
Alex
__
Do
--- Martijn Uffing [EMAIL PROTECTED] wrote:
Ave people
DRI/MESA won't compile with gcc 2.95.4
My system is debian stable with gcc 2.95.4 as system compiler.
I get the error only with 2.95.4. If I use gcc 3.3.3 the whole
buildtree
compiles fine. I get the exact same error (and no error
--- George Lengel [EMAIL PROTECTED] wrote:
Hi,
I thought I read earlier in the week that the Savage driver moved to
the trunk
and the console corruption problem had been fixed. I pulled the
source via
CVS and recompiled but I still have my consoles all showing corrupted
text.
Did I
--- Mickaël_Cornet [EMAIL PROTECTED] wrote:
Hello,
First, thank you for your job, I have installed the savage-2-0-0-0
branch (it
is the first time I try it). No problem to install it.
So, I am happy to see that DPMS switch off my backlight and that my
savage
twister K use 3D, I can
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Thu, 2004-02-26 at 15:37, Alex Deucher wrote:
regarding the mouse problems, if you are using a fancy ARGB Xcursor
theme, the cursor will be drawn with software. If so, that's
probably
why the mouse flickers in blender.
The radeon
--- George Lengel [EMAIL PROTECTED] wrote:
On Wednesday 25 February 2004 06:02 am, Alex Deucher wrote:
I don't show any corruption on the savages I have access to (IX,
savage4). What chip are you running on? Did you follow the
instructions here:
http://dri.sourceforge.net/cgi-bin
I just checked out a fresh copy of mesa and the dri and I can't get it
to build:
../lib/GL/mesa/x86/3dnow_xform4.o
../../../../../lib/GL/mesa/x86/sse.o
../../../../../lib/GL/mesa/x86/sse_normal.o
../../../../../lib/GL/mesa/x86/sse_xform1.o
of glxinfo just to be sure. lots of times the
xfree86 log is correct, but an old copy of libGL or 3D driver causes
apps to use SW rendering eventhough hw is available.
Alex
regards Cristiano
On Thu, 2004-03-04 at 14:45, Alex Deucher wrote:
--- Cristiano De Michele [EMAIL PROTECTED] wrote
driver or an out of tree driver? I'm not sure why it's not working;
you may have to build it against the DRI tree.
Alex
On Thu, 2004-03-04 at 15:20, Alex Deucher wrote:
--- Cristiano De Michele [EMAIL PROTECTED] wrote:
Hi Alex,
this the log of the X I'm currently running (plain
debian
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Thu, 4 Mar 2004 06:29:51 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Cristiano De Michele [EMAIL PROTECTED] wrote:
ok but what about the other two problems?
in particular the fact that I can't use synaptics
module
For those of you messing with XvMC support on savage, I just checked in
a fix for the missing extension problem. I had forgotten to port over
the setup code from S3's driver. I tested it briefly on savage4, but I
only got an blue window. It's possible that the XvMC stuff is
prosavage/twister
--- Cristiano De Michele [EMAIL PROTECTED] wrote:
Hi,
I have linux 2.4.25 + swsusp 2.0.0.10
on compaq evo 1015 (ati radeon IGP 320M)
and I recently installed the dri trunk
of xfree86-xserver recompiling all sources
from scratch.
This way I got finally dri working but
when I tried to
--- Felix Kühling [EMAIL PROTECTED] wrote:
Mark,
I'm forwarding your message to the dri-devel mailing list. I can't
test
randr here. Alex how much do you know about randr? Can you reproduce
and
problems?
Unfortunately, I haven't really messed with randr much. I don't
personally find
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 5 Mar 2004 07:34:30 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Mark,
I'm forwarding your message to the dri-devel mailing list. I
can't
test
randr here. Alex how much do
--- Mike A. Harris [EMAIL PROTECTED] wrote:
On Fri, 5 Mar 2004, Felix [ISO-8859-1] Kühling wrote:
Date: Fri, 5 Mar 2004 16:47:50 +0100
From: Felix [ISO-8859-1] Kühling [EMAIL PROTECTED]
To: Alex Deucher [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Content-Type: text/plain
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 5 Mar 2004 07:34:30 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Mark,
I'm forwarding your message to the dri-devel mailing list. I
can't
test
randr here. Alex how much do
--- Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Was the DRI tree ever synced with the XFree86 tree prior to 4.4.0? I
downloaded and installed 4.4.0 on a NetBSD system, thinking that
MergedFB
would just work but, unfortunately, it doesn't.
Nope, no mergedfb in 4.4. Mergedfb is only
--- Cristiano De Michele [EMAIL PROTECTED] wrote:
Hi Michel,
I'm using your dri-trunk debian packages on a compaq evo n1015v
laptop with ati radeon IGP320M graphic adapter
and all works fine concerning suspend/resume (swsusp 2.0.0.10+linux
2.4.25) as long as I don't use agpgart module.
I
--- Sérgio Monteiro Basto [EMAIL PROTECTED] wrote:
On Thu, 2004-03-04 at 20:15, Alex Deucher wrote:
For those of you messing with XvMC support on savage, I just
checked in
a fix for the missing extension problem. I had forgotten to port
over
the setup code from S3's driver. I tested
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Was the DRI tree ever synced with the XFree86 tree prior to 4.4.0?
I
downloaded and installed 4.4.0 on a NetBSD system, thinking that
MergedFB
would just work but, unfortunately
--- Mario Premke [EMAIL PROTECTED] wrote:
- starting xawtv it says 'no overlay function' (and something
like:
trouble with v4l-conf) and the content of the xawtv frame is
scrumbled - I haven't had this behaviour before and didn't touch
the
XF86Config --- any hints ???
don't
--- Dave Airlie [EMAIL PROTECTED] wrote:
Hi,
I've just tried getting a solo Mesa working on 2.4.25, latest DRM
from DRI CVS and top of tree Mesa on r100,
my framebuffer console comes up, but when I start the server the
screen is
corrupted, when I run the test app I can see the
--- Fritsch [EMAIL PROTECTED] wrote:
I am using Radeon Snapshots on an IBM Thinkpad together with the
XFree86
binary.
All Version from before 20040302 work fine,
with later Versions I get faults in glxgears, which refuses running!
Does anyone experience same problems?
It might be an
. Before my changes to check available
videoram, the front/back/depth buffers would be arbitrarily allocated
and if you only have 16MB of video ram, the back buffer would overflow
into the front buffer.
Alex
Thanks,
Steve
On Fri, 2004-02-27 at 15:21, Alex Deucher wrote
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 12 Mar 2004 14:48:45 +
avilella [EMAIL PROTECTED] wrote:
The DRI seems to be enabled:
-
[snip]
yes, looks good.
-
and here is the log of:
[avb]$ LIBGL_DEBUG=verbose glxinfo
-
name of display:
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
There was a website with support for the PCI G450 (for alpha I
think):
http://www.instmath.rwth-aachen.de:8000/linux/G450-PCI/
However it seems to be down at the moment. Someone on the ML knew
the
guy who was doing
--- Andrew Morton [EMAIL PROTECTED] wrote:
Ian Romanick [EMAIL PROTECTED] wrote:
We're looking at reorganizing the way DRM drivers are maintained.
Currently, the DRM kernel code lives deep in a subdirectory of the
DRI
tree (which is a partial copy of the XFree86 tree). We plan to
--- Thomas Hellstrom [EMAIL PROTECTED] wrote:
Hi!
Via have, some time ago, released a drm module which seems quite
clean
and a dri / OpenGL implementation which Alan Cox fixed up some time
ago
and which is downloadable from your site. I don't think it has been
ported to be compatible
--- Jon Smirl [EMAIL PROTECTED] wrote:
I'm putting together a sample DRM CVS module so that everyone can
look at it and
help move things around until we get it right. But this brings up the
question,
where should it go? Into the the mesa or dri project? This question
is
complicated by
--- Thomas Hellström [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Thomas Hellstrom [EMAIL PROTECTED] wrote:
Hi!
Via have, some time ago, released a drm module which seems quite
clean
and a dri / OpenGL implementation which Alan Cox fixed up some
time
ago
and which
--- Thomas Hellström [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Thomas Hellstrom [EMAIL PROTECTED] wrote:
Hi!
Via have, some time ago, released a drm module which seems quite
clean
and a dri / OpenGL implementation which Alan Cox fixed up some
time
ago
and which
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 16 Mar 2004 16:31:37 -0800
Ian Romanick [EMAIL PROTECTED] wrote:
I spent some time today pulling the DRI interface structures and
function prototypes out of glxclient.h. I came across one snag
that I
missed before. It turns out
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-03-17 at 13:23, Keith Whitwell wrote:
Michel Dänzer wrote:
On Wed, 2004-03-17 at 10:14, Keith Whitwell wrote:
Jon Smirl wrote:
After the switch I can remove these directories from dri:
--- Thomas Hellström [EMAIL PROTECTED] wrote:
Thomas Hellstrom wrote:
Hi!
Here comes the via drm module patch against current (at least as
of
today :-) CVS
(/usr/local/src/dri-cvs/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm)
What we've done is the following:
1.
I've re-worked the non-Xv streams code and a few other things. I added
a new streams reset function that seems to fix the occasional console
corruption I got on my IX. I enabled the COB on savage4 and newer
chips and added an option to disable it. Tim's driver had it disabled
and had a note
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 19 Mar 2004 12:51:14 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I've re-worked the non-Xv streams code and a few other things. I
added
a new streams reset function that seems to fix the occasional
console
corruption I got on my
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 19 Mar 2004 12:51:14 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I've re-worked the non-Xv streams code and a few other things. I
added
a new streams reset function that seems to fix the occasional
console
corruption I got on my
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 19 Mar 2004 15:21:14 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
[snip]
There's still one problem. The hardware cursor is corrupted when
3D
apps
are active. It looks like the COB is scribbling over the memory
that
stores
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Sat, 20 Mar 2004 09:07:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
[snip]
No artifacts. The video is absolutely stable.
Cool. I've enabled it by default for prosavages and twisters. you
can
still disable it with the BCIforXv
--- Mental Patient [EMAIL PROTECTED] wrote:
Hello. I'm trying to determine a workaround/fix for a problem I'm
having
with my laptop ( an ibm thinkpad t22 ).
Whenever the laptop comes out of suspend, any DRI app (game,
screensaver, etc) causes the screen to hang. If I happen to be on the
, especially since it never even
gets written to the cob regs. How does the attached patch look
(untested - it's basically just yours with some further cleanups and
removes the 128K allocation)?
Alex
Regards,
Felix
On Sat, 20 Mar 2004 09:07:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote
Subject says it all. Doesn't seem to break anything in basic testing
here, but I'm not too familiar with the agp code. lowering the agp
mode may help lockups on flakey agp chipsets. Also for the AGP
aperture size, the old driver defaulted to 16 MB, so I did the same in
the patch. Any thoughts
2004 09:20:30 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
Subject says it all. Doesn't seem to break anything in basic
testing
here, but I'm not too familiar with the agp code. lowering the agp
mode may help lockups on flakey agp chipsets. Also for the AGP
aperture size, the old
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi Marcin,
Also CCing to Alex, he probably knows more about this.
Currently the driver looks like it's not supposed to render to the
front
buffer at all. When single buffering is used, the driver draws to the
back buffer and copies it over to
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 23 Mar 2004 08:16:49 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
[snip]
Anyway, the reason is that accelerated 3D rendering only works
with
tiled memory but the front buffer
--- Felix Kühling [EMAIL PROTECTED] wrote:
This commit works fine on the ProSavage but on the SavageIX there are
two new problems. :(
2D performance is a lot worse now. Moving opaque windows is really
slow.
And I get this from mplayer on movies that worked before:
VO: [xv] 352x272 =
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 23 Mar 2004 08:16:49 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
[snip]
Anyway, the reason is that accelerated 3D rendering only works
with
tiled memory but the front buffer
--- Mark Cass [EMAIL PROTECTED] wrote:
dri-devel,
i am using the dri tree build (Mesa/xc - no branch) of all drivers
(2d and 3d) on xfree86 version 4.3.0. my video card is a 32MB savage
4 pro. X is configured to use the savage drivers.
the problems i am noticing concern the
--- Felix K#252;hling [EMAIL PROTECTED] wrote:
On Thu, 25 Mar 2004 20:38:43 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
[snip]
Don't know which changes that would be. The only thing where the
tiling
of the front buffer would
--- Felix K#252;hling [EMAIL PROTECTED] wrote:
On Fri, 26 Mar 2004 10:53:40 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K#252;hling [EMAIL PROTECTED] wrote:
On Thu, 25 Mar 2004 20:38:43 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling
--- [EMAIL PROTECTED] wrote:
Hi Fiz,
Hi Felix
I'm not sure I understood the problem description correctly. The
cursor,
is it like random noise in a 64x64 pixel block that changes once or
more
often every second? Then my guess is that it's a problem with the
Command Overflow
Please try the attached patch and let me know if it fixes the problem.
Also available here:
http://www.botchco.com/alex/savage/twister.diff
Alex
--- [EMAIL PROTECTED] wrote:
Hi Fiz,
Hi Felix
I'm not sure I understood the problem description correctly. The
cursor,
is it like random
Felix,
I did a little research and I think I figured out a few things
regarding the integrated savages
(http://www.via.com.tw/en/ProSavage%20Chipsets/prosav_index.jsp). The
prosavage P/KN133 twister chipsets are the mobile prosavage core and
they use the savage4 2D and 3D
Could you also try this new version in addition to the last one? I
need to figure out what the bci enable bit is for twister.
http://www.botchco.com/alex/savage/twister2.diff
thanks,
Alex
--- [EMAIL PROTECTED] wrote:
Hi Fiz,
Hi Felix
I'm not sure I understood the problem description
Based on some research and feedback I've gotten, I've re-structured the
GBD, COB, and streams code. I put together a document based on my
findings here:
http://www.botchco.com/alex/savage/Savage_Guide.txt
I've tested on savage4 and savage IX, and all seems well. I'd like to
get more feedback
--- [EMAIL PROTECTED] wrote:
Hi Alex:
i have been probing your two patches. You can see the result of the
first
one in this screenshot:
http://www.e-oss.net/import2.png
i am just trying to compile your second patch but the xserver is
giving me
some errors.
The second patch is an
--- [EMAIL PROTECTED] wrote:
Hi again:
i have remove, download, compile and patch the dri-cvs again with
your two
patch and the result is the same.
http://www.e-oss.net/import2.png
I have proved with two diferent kernels (2.4.22-ac3 and 2.4.25) and
the
problem persist :(
any
Also try enabling the COB again when using the patch I just sent you.
I want to make sure I got that fixed as well.
Alex
--- [EMAIL PROTECTED] wrote:
Hi again:
i have remove, download, compile and patch the dri-cvs again with
your two
patch and the result is the same.
--- [EMAIL PROTECTED] wrote:
hi again:
I am having lots of problems and i dont know where the cause is.
Since i
use the second patch when i am using the savage driver my screen
fails, as
you could seen in my last screenshot.
I think that the problem was that, when i was proving the
--- [EMAIL PROTECTED] wrote:
I have aspire 1300, with s3 savage twister (8d02),
http://62.44.212.64:8080/s3_ProSavage_KN133/
look there. I compiled some time ago savage cvs and dri is now
enabled, but I
think it isn't still working.
You need to change the permissions on those files, I
--- [EMAIL PROTECTED] wrote:
I have aspire 1300, with s3 savage twister (8d02),
http://62.44.212.64:8080/s3_ProSavage_KN133/
look there. I compiled some time ago savage cvs and dri is now
enabled, but I
think it isn't still working.
You fps in glxgears do seem pretty slow. run ldd
--- [EMAIL PROTECTED] wrote:
sorry, now permissions are ok.
don't know what is problem. can you give me description like this how
things
work:
savage_hardware - kernel_drm - xfree_savage 2d or/and 3d
It looks something like this:
hardware - 2d driver
hardware - DRM - 3d driver
--- [EMAIL PROTECTED] wrote:
ldd_glxgears
http://62.44.212.64:8080/s3_ProSavage_KN133/
Compare this to ldd /path/to/glxinfo and make sure they are using the
same version of libGL.
Alex
__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
--- Sérgio Monteiro Basto [EMAIL PROTECTED] wrote:
I am sending this email again because seams doesn't arrive at first
time
Hi
well I update cvs trunk from dri ,
after some compile problems, I remove all and download it again.
and after make World and make install (this time without
--- [EMAIL PROTECTED] wrote:
I have aspire 1300, with s3 savage twister (8d02),
http://62.44.212.64:8080/s3_ProSavage_KN133/
look there. I compiled some time ago savage cvs and dri is now
enabled, but I
think it isn't still working.
How should I first help? More info about my computer
--- [EMAIL PROTECTED] wrote:
# I have aspire 1300, with s3 savage twister (8d02),
#
# http://62.44.212.64:8080/s3_ProSavage_KN133/
#
# look there. I compiled some time ago savage cvs and dri is now
# enabled, but I
# think it isn't still working.
#
# You fps in glxgears do seem
--- Daniel J. Michael [EMAIL PROTECTED] wrote:
I have a laptop, using a TwisterK, and I just applied this patch to
the latest CVS dri, then compiled and installed it. Now, when I start
X the display is massively corrupted, and basically useless. I went
back to the version I was using
--- Nicolas Sabouret [EMAIL PROTECTED] wrote:
Michel Dänzer a écrit :
With a 2.6 kernel, you also need to load the chipset specific AGP
module. I guess the log message could be improved about that.
Thanks Michel. Loading the ati-agp module made the whole thing work.
Sorry for asking such
want to update to the
latest cvs anyway, to make sure none of the other cvs problems are
getting you.
Alex
--On Monday, April 05, 2004 7:08 AM -0700 Alex Deucher
[EMAIL PROTECTED] wrote:
--- Daniel J. Michael [EMAIL PROTECTED] wrote:
I have a laptop, using a TwisterK, and I just applied
--- [EMAIL PROTECTED] wrote:
[snip]
I think this fixed it. It looks like the driver wasn't getting linked
to
the shader files after the mesa code shuffle.
It seems like all the problems were caused by make files after the
mesa
upgrade but just in case I've laid out all of my steps.
--- [EMAIL PROTECTED] wrote:
I think you're right Alex. This is what I think happened. I noticed
that
when the various Imakefile and Imakefile.inc were updated with
regards to
the file shuffle from the latest mesa update they were only
committed to
head. They weren't added to the
--- Dave Airlie [EMAIL PROTECTED] wrote:
Is anyone against just including mach64 in the trunk? I know it'
still
unsecure and unstable, but so is savage and that's in the trunk.
We
don't have to build it by default. plus it would avoid having to
update the makefiles on the branch
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Thu, 2004-04-15 at 17:13, Alex Deucher wrote:
Speaking of merging, what are everyone's thoughts on merging the
DDX
trees (drivers at least, I don't know about the rest, especially
with
the licensing)? I was thinking mostly DRI-xfree86 but I
of tests with several cvs versions and
diferent patches
(made by alex deucher) and all of them gave me a lot of problems..
at the begining with the 26-03-2004 cvs dri and mesa version i had
the
problem that
you can see in this screenshot.
http://www.e-oss.net/import.png
by chance i
--- Tom Vier [EMAIL PROTECTED] wrote:
i finally got dri working, but... i'm using 2.6.5 on x86 (dual
opteron
mobo with a single cpu). i have an agp 9200 and i'm using xfree
4.3.0.
whenever i scroll or sometimes when inputing text, i get these white
horizontal lines that appear in random
--- Jon Smirl [EMAIL PROTECTED] wrote:
I wasn't thinking about IGP style hardware when I answered. But you
do have to
wonder if that solution will still be around two years from now. It
probably
will be but it will be the most basic, cheapest solution that ships
for free on
every
--- Martin Spott [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
I don't know about that. I can forsee IGP becoming _the_ standard
method for video. Look at sgi... all of their video systems use
system memory, [...]
Really ? Which one ?
I know the O2 does, but MGRAS and VPro
--- Adam Jackson [EMAIL PROTECTED] wrote:
On Monday 10 May 2004 16:17, Adam Jackson wrote:
Anyone opposed to moving DRI's bug tracker to freedesktop's
bugzilla? I
ask because I _strongly_ dislike sourceforge's bug system,
particularly
compared to bugzilla. I'll even volunteer to import
--- Roland Scheidegger [EMAIL PROTECTED] wrote:
Chris Pickett wrote:
Chris Pickett wrote:
Hi Roland,
I'm sorry to be so persistent here, but what are the specific
steps
(not the exact commands, e.g. checkout pkg X is clear enough) we
need to do to apply this patch to our
--- Sven Luther [EMAIL PROTECTED] wrote:
On Thu, May 06, 2004 at 05:50:40PM -0700, Jon Smirl wrote:
--- James Simmons [EMAIL PROTECTED] wrote:
2) Ben suggestion that we mount userland inside the kernel during
early
boot and use a userland library. If we would use a library
then it
--- Alan Cox [EMAIL PROTECTED] wrote:
On Llu, 2004-04-26 at 03:38, Vladimir Dergachev wrote:
So the next question would be how does one hack radeon or r200
driver to
get down to a particular function ?
When I was trying to debug the sis6326 and via drivers the best way I
found with
--- Patrick McFarland [EMAIL PROTECTED] wrote:
Im trying to confirm if the new savage driver is actually in cvs now,
anyone know? (And anyone here actually use it? Does it work?)
yes, yes, and yes. All savages except the savage2000 are supported.
see this page for more info:
--- Adam Jackson [EMAIL PROTECTED] wrote:
On Monday 26 April 2004 17:59, Felix Kühling wrote:
The mach64 driver has moved to the trunk. Try building it there.
The
branch is broken for quite a while now. It won't be fixed.
So it's been merged then? As in, I should go update the wiki so
--- Vladimir Dergachev [EMAIL PROTECTED] wrote:
Keith - do these drivers work with XFree86 4.4.0, or do they require
something newer ?
Also, if one is starting on a new driver do you recommend using 4.4.0
codebase or something different ? (the simpler the better..)
I'd say stick with DRI
--- George Lengel [EMAIL PROTECTED] wrote:
Hello everyone,
I don't know if there is a more appropriate list for this, but I hope
someone
here can help with my problem.
I pulled the latest CVS for the DRI drivers to update the system for
my Savage
4.0 card. I wanted to see if I got
--- Dax Kelson [EMAIL PROTECTED] wrote:
Now that ATI has released R420 hardware what are the chances of
getting
docs for the now legacy R300/350 chips?
Your guess is as good as mine. All we can do is wait and see I guess.
It would be very very good if there was a good open source 3D
--- Vladimir Dergachev [EMAIL PROTECTED] wrote:
On the plus side, Vladimir Dergachev seems really interested in
getting
the R300 supported, with or without ATI's help. I'm certainly
willing to
test anything on the 9800 that I have floating around :-)
One small correction - with ATI
--- Jon Smirl [EMAIL PROTECTED] wrote:
Is there a document describing how memory management is handled for
the overall
AGP/VRAM space? I've found where texture memory is handled, but who
is
allocating space for framebuffers on multi-head cards?
Right now the framebuffer is managed in the
--- Egbert Eich [EMAIL PROTECTED] wrote:
Jon Smirl writes:
I'm putting together a document for Kernel Summit that describes
the issues
around graphics device drivers. The kernel developers are
currently making first
pass comments on it. As soon as I fold their comments in I'll
post
--- Egbert Eich [EMAIL PROTECTED] wrote:
Jon Smirl writes:
I'm putting together a document for Kernel Summit that describes
the issues
around graphics device drivers. The kernel developers are
currently making first
pass comments on it. As soon as I fold their comments in I'll
post
Update to the latest driver (dri trunk) based on tim's code. As I
recall, older drivers based on S3's code did not support gamma
correction properly.
Alex
--- Thibault Mondary [EMAIL PROTECTED] wrote:
Hi,
I am using savage driver from savage-2 cvs but it seems the switch
Gamma x y
z in
there is also an s3tc width field in the tiled surface regs (0x48c40,
etc.). you may need to mess with that.
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi Mark,
Your description of the problems sounds like the tiling code does the
right thing. However, in the driver there were
301 - 400 of 1146 matches
Mail list logo
