--- Mike Mestnik [EMAIL PROTECTED] wrote:
--- Alex Deucher [EMAIL PROTECTED] wrote:
--- Mike Mestnik [EMAIL PROTECTED] wrote:
The screen size(in pixels or mm) is now x1 + x2 by (y1 y2) *
y1 +
(y1 y2) * y2. Swap (y and
x) and (1 and 2) where needed. Then the DPI should
--- Goyo Roth [EMAIL PROTECTED] wrote:
Quoting Alex Deucher [EMAIL PROTECTED]:
snip
On that note, I am interested in getting involved in DRI development.
I've been
trying to read through all the recommended documents for new
developers from the
DRI site. I haven't finished all of them
S3/VIA released a code drop a while back for xfree86 4.2.0. it needs
to be ported to mesa 5.x to work with newer versions of xfree86. that
work is being done on a branch of DRI cvs. for now if you want HW 3D
you will need to use 4.2.0 with s3's code drop.
see these pages for more info:
turn off HW render accel. both HW render and 3D use the 3D engine and
I don't know if they both keep state properly. that's probably were
your corruption comes from.
Alex
--- Ryan Underwood [EMAIL PROTECTED] wrote:
Hi,
I've had some problems with certain DRI applications occasionally
you should find what you need here:
http://dri.sourceforge.net/cgi-bin/moin.cgi/ATIMach64
I'm not sure anyone has tested it on PPC yet though.
Alex
--- Tomas Groth [EMAIL PROTECTED] wrote:
Hi!
I have an old G3 iBook with an ATI Rage Mobility, and there
seems to be no hardware acceleration
it occurs.
Would installing a debug X server help track the cause of the
corruption
down?
On Tue, Dec 09, 2003 at 06:59:30AM -0800, Alex Deucher wrote:
turn off HW render accel. both HW render and 3D use the 3D engine
and
I don't know if they both keep state properly. that's probably
into
with it. ;)
Is there anywhere I can get a G400 databook for reference, or is that
not publicly available?
On Tue, Dec 09, 2003 at 07:55:20AM -0800, Alex Deucher wrote:
renderaccel. the reason for the curruption is that both the 2d
driver
and the 3d driver are using the 3d engine
there is no support for suspend and resume on matrox hardware. the
only driver with suspend/resume support is radeon. if you want to add
support you can take a look at the radeon driver for reference.
Alex
--- Serge Gavrilov [EMAIL PROTECTED] wrote:
Hello!
Several days ago I have installed
Felix,
I realize you are focusing on the 3D side, but I noticed that the HW
XvMC stuff isn't in cvs. I would assume that should pretty much just
drop into place once the mesa port is done? No sense in dropping that
if it works.
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi savage
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Wed, 17 Dec 2003 09:36:16 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
Felix,
I realize you are focusing on the 3D side, but I noticed that the
HW
XvMC stuff isn't in cvs. I would assume that should pretty much
just
drop
in 2.6 there are two agp related kernel modules that need to be loaded.
agpgart and your agp chipset specific module (via, sis, ati, etc.).
Alex
--- Adam K Kirchhoff [EMAIL PROTECTED] wrote:
So I decided to give 2.6.0 a shot this morning :-)
My Radeon 8500 (which previous worked with
perhaps some sort of conflict with the local header file? I recall
seeing a version of videodev.h in the 2d driver directory in cvs, but I
haven't really looked into it.
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
I'm confused ...
I solved my other kernel include file problems and now I
as I recall the savage hardware needs a tiled framebuffer for the 3d
engine, but 2d engine can use linear or tile. Most drivers use linear,
so that's probably what the savage driver did originally, now that it
has 3D support you need to get 2d working in tile mode for both to
work. there may just
Having briefly looked at the savage_dri.c file in cvs, there are
several XAA-like functions defined there, so there are two versions,
one for DRI (in savage_dri.c) and ones for XAA (in savage_accel.c).
e.g.:
static void
SAVAGEDRISetupForScreenToScreenCopy(
ScrnInfoPtr pScrn, int xdir, int
I'd be willing to help on the 2D side, I just need to get ahold of an
old savage board to test with. I have an old laptop with a savage ix
in it, but it's be in the process of being sold, so I doubt I'll be
able to mess with it, plus there is no 3d support for savage3D core yet
anyway.
Assuming
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Mon, 22 Dec 2003 15:30:47 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I'd be willing to help on the 2D side, I just need to get ahold of
an
old savage board to test with. I have an old laptop with a savage
ix
in it, but it's
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Mon, 22 Dec 2003 15:30:47 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I'd be willing to help on the 2D side, I just need to get ahold of
an
old savage board to test with. I have an old laptop with a savage
ix
in it, but it's
A lot of us would like that information, but unforuntately SiS refuses
to release any documentation for their graphics chips. You can try
taking it up with SiS directly, but I suspect you will not have much
luck.
Alex
--- [EMAIL PROTECTED] wrote:
I need technical reference (databook,
Does the via driver support 3D with dualhead? It seems to. I noticed
the following code in via_context.c:
GLboolean saam;
int count = 0, fbSize;
saam = XineramaIsActive(vmesa-display);
if (saam vmesa-viaScreen-drixinerama) {
vmesa-xsi =
Good to meet you.
Good luck with the source. Feel free to ask any questions on this
list. we'll try and help as best we can.
Alex
--- Anthony Best [EMAIL PROTECTED] wrote:
Hello,
I've just recently been able to get the mach64 drivers working on my
laptops Rage Mobility P/M and linux
Felix, I'm having trouble getting the savage DRM to build. Perhaps my
kernel is too old. As I recall remap_page_range() changed. perhaps
that's the problem. any idea how I can get it working with my current
kernel? I'm having trouble getting 2.4.24 working properly for my set
up.
Alex
gcc
Nevermind. seems to be a redhat only problem (they use the 2.6 MM stuff
in rh9)... I got it working using a vanilla kernel.
Alex
-
Felix, I'm having trouble getting the savage DRM to build. Perhaps my
kernel is too old. As I recall remap_page_range() changed. perhaps
that's the
. The
driver
has only three driver ioctls and they are only used for PCI cards.
Felix
On Wed, 7 Jan 2004 11:53:49 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
Felix, I'm having trouble getting the savage DRM to build. Perhaps
my
kernel is too old. As I recall remap_page_range() changed
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Wed, 7 Jan 2004 14:56:24 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
just as a follow up, I got the DRM to build under 2.4.24, (redhat
uses
2.6 MM in rh9). Unfortunately, I can't get pcmcia to work for me
in
2.4.24, so I can either
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Thu, 8 Jan 2004 15:40:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
well, I managed to fix the 2D corruption in tile mode on savage4.
the
problem is that the bits of the GBD (MM816C) have different meaning
on
savage4 vs. twister
savage4 uses 8 for bci enable while it's 0 on prosavage. that's why
you have to define SAVAGE4 to make it work. the enablemode_m7()
function uses 8 arlready. the BD's and BCI seems to work differently
on savage4 vs. prosavage.
Also FWIW, I tried both with and without the cob enabled and it
FYI, I just got 3D and 2D working on savage4. the PBD setup was wrong
in savage_dri.c. I'll be posting a patch soon. Also, what bpp should
depth buffer be? the same as the framebuffer?
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Thu, 8 Jan 2004 15:40:55 -0800 (PST)
Alex Deucher
The attached patch is a cleaned up version of the one I made this
morning. It enables DRI support for savage4 and shouldn't break
prosavage or twister, however, I'd like someone with prosvage or
twister to check it out before I commit it.
Both tiled and linear framebuffer mode now work with 3D.
they are, but I can't wait to see that speedup
myself.
:) Nice work.
Regards,
Felix
On Fri, 9 Jan 2004 12:45:10 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
The attached patch is a cleaned up version of the one I made this
morning. It enables DRI support for savage4
You might want to ask Alan Hourihane. he's done most (all) of the work
on that driver.
http://dri.sourceforge.net/cgi-bin/moin.cgi/Trident
see this thread for more:
http://marc.theaimsgroup.com/?t=10522413641r=1w=2
I think Alan started a DRM module in cvs. your best be would probably
be to
you need to build the savage kernel module. The code is in:
xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
Change to that directory and then type:
make -f Makefile.linux
or
make -f Makefile.linux LINUXDIR=/path/to/kernel/src
If you are using redhat 9 (possibly fedora as well),
--- Jesse Merriman [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
hmmm... if both agpgart and savage are loaded before X starts, I'm
not
sure what your problem would be. what does your kernel log or
dmesg
say when you load the modules?
Here's the end of my dmesg:
Linux agpgart interface
just do a cvs update and rebuild the kernel module
(xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel), DRI
driver (xc/xc/lib/GL/mesa/src/drv/savage) and 2D driver
(xc/xc/programs/Xserver/hw/xfree86/drivers/savage). in most cases you
can just copy the new versions over you old ones.
Right now no one has tested on supersavage. You will need to add the
supersavage PCI ID's to the DRM
(xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage.h)and
and also fix savage_driver.c in the 2D driver so that the DRI init
functions get called. you will need to add:
--- Marco Strack [EMAIL PROTECTED] wrote:
ok, changed the code and recompiled the source.
Now the drm module recognizes the card and inits it.
/dev/dri/card0 is present even though not accessable by any user
besides root.
(flags are ok and i also have a proper DRI Section in config...)
I just fixed 3D at 32 bpp on savage4 and commited the changes. It
ended up being a define with the wrong bits set. I get between 280 and
300 fps in glxgears on savage4 at 32 bpp and around 600 at 16 bpp.
textures still aren't quite right on savage4. I suspect textures need
to be setup slightly
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Mon, 12 Jan 2004 18:17:15 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I just fixed 3D at 32 bpp on savage4 and commited the changes. It
ended up being a define with the wrong bits set. I get between 280
and
300 fps in glxgears
--- Wlodzimierz Lipert [EMAIL PROTECTED] wrote:
Hi All People!
Following Your instractions I post this message on mailinglist.
I'd like to join DRI project as a developer(device drives).
I'd be thankfull if someone could send me some ditailed info on X and
DRI.I'm good with OpenGL
but
--- Konstantin A. Lepikhov [EMAIL PROTECTED] wrote:
Hi!
Guess I found the problem - looks like recent changes in
agpgart driver break its work on i850 chipset (this changes made
during
2.4.20-2.4.22 - after that this hangs is occur). Now I reproduced
this
hang with fglrx then using
--- Roland Scheidegger [EMAIL PROTECTED] wrote:
Dieter Nützel wrote:
[snip]
Roland
btw what's wrong with my message headers? I'm always getting Your
message to Dri-devel awaits moderator approval because of Message
has
a suspicious header.
I get the same thing from time to time.
, 13 Jan 2004 09:58:48 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Mon, 12 Jan 2004 18:17:15 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I just fixed 3D at 32 bpp on savage4 and commited the changes.
It
ended up being
I've made some changes to the savage driver to hopefully set up the
bitmap and tiling registers correctly for both 2D and 3D for all
chipsets (except savage2000). It's based on what I can glean from the
2D driver and what I've seen on my savages. I've also enabled 3D for
most savages in the DRM
whether or not 2D is tiled.
Does this make sense?
Alex
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
whoops. I'll have to check that out. Can you point me to the
code?
I'm assuming savage_span in the DRI somewhere
(0x48C48, value|(pSAVAGEDRI-depthOffset 5) );/* depth */
More comments inline ...
On Wed, 14 Jan 2004 08:06:24 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
Felix,
Last night I did some thinging about the pitch and linear vs.
tiled
mode. To be honest, I don't think
--- Jesse Merriman [EMAIL PROTECTED] wrote:
Felix Kühling wrote:
What you're describing is the typical symptoms of a chip lockup. I
havn't got one of those in a while on my ProSavage. Jesse, are you
using
the latest CVS for both the 2D and 3D driver?
I last updated everything
)
Alex Deucher [EMAIL PROTECTED] wrote:
I was just looking through the original savage code drop and I
noticed
this file:
LinuxDriver/XvMC/s3data.h
it contains a lot of useful info about registers and the BCI for
savage
chips.
for example:
#define TILED_SURFACE_REGISTER_0
this.
Alex
/Felix
On Wed, 14 Jan 2004 14:39:41 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I fixed the pitch in savagespan today. my assumption was right.
see
more below.
Alex
--- Felix K_hling [EMAIL PROTECTED] wrote:
[snip]
I can't say I'm an expert either
--- Ian Romanick [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
I think in theory anyone (2D, 3D, CPU) can write to any BD it as
long
as it is selected as the destination of that operation. you can
even
set one BD as a source and another as a destination I think.
Perhaps
Tim can
/Imakefile that I used and a small
patch
that fixes a few include file problems. I hope that does the trick.
Felix
On Thu, 15 Jan 2004 11:57:10 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
OT: XvMC, I've been playing with that today, but I can't seem to
make
it build. can you send
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I just plugged the Savage4 into my box and gave it a go. I'm trying
to
give a complete summary of what I noticed so far. First a few notes
about the card and my setup:
The card has only one DVI port, no VGA. I assume that this port
outputs
In theory this is possible, all you really need to do is direct one of
the crtcs to output to the tv-out port rather than one of the monitor
ports. unfortuantely I don't know anything about tv out on radeon. if
the gatos drivers support clone mdoe, 3D should work on the cloned
head. you might
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I got software fallbacks to work with Savage IX ;-), more or less.
It's
scribbling all over the screen, and what it draws depends on the
background. Furthermore, the way it scribbles stuff over the screen
depends on whether I have DisableTile
I'm not sure if this is a leak per se... the problem is the 2D and 3D
driver aren't too good at managing memory. the 3D driver may snag a
big chunk for a full screen 3D app and then keep it. It's then no
longer available for the 2D driver resulting in a bad alloc error. I
think Alan H. was
--- Rick Harris [EMAIL PROTECTED] wrote:
[snip]
Everything else worked as you described though I'm not sure why it's
only showing 640x480 for you Alex.
All resolutions work fine up to 1024x768 on the laptop (MobileSavage
IX/MV).
The problem we have is due to the fact that we are using
--- Alan Cox [EMAIL PROTECTED] wrote:
On Sul, 2004-01-18 at 01:56, Alex Deucher wrote:
I'm not sure if this is a leak per se... the problem is the 2D and
3D
driver aren't too good at managing memory. the 3D driver may snag
a
big chunk for a full screen 3D app and then keep it. It's
--- Ryan Underwood [EMAIL PROTECTED] wrote:
[snip]
On another topic, do you use a dualhead G400? If so, are you
able to
properly use DPMS on the second head?
I don't run XFree86 except when trying to hunt DRI related bugs.
It's
been well over a year since I really used XFree86
Wow that's awesome! if we are lucky SGI may contribute the guts we
need to get the DRI working with xinerama/dmx/chromium. It looks like
their multipipe GL already works with xinerama. Does anyone know
anymore about this or know what sort of license their code will have?
Alex
--- Dieter
--- Ryan Underwood [EMAIL PROTECTED] wrote:
On Tue, Jan 20, 2004 at 12:57:11PM +0200, Ville Syrjälä wrote:
The only problem I have with the mga driver right now is lack of
mouse
cursor in UT, though there is a claim in bugzilla that you fixed
it. Do
you have any details on the fix?
--- Ryan Underwood [EMAIL PROTECTED] wrote:
Hi,
GL_ATI_envmap_bumpmap seems to describe identical functionality to
DirectX6 EMBM. ATI's drivers support this extension and it is
implemented in Mesa apparently. Does anyone know of a demo or sample
code that utilizes this extension?
I'm
--- Ryan Underwood [EMAIL PROTECTED] wrote:
[snip]
No code was copied, only some defines. I need other people to check
the
code and tell me if it will break on other video cards. I only have
a
G400 DH, but there is G450, G550, G200 DH, G200 non-maven DH, etc
which
need to be tested,
--- Dave Airlie [EMAIL PROTECTED] wrote:
Hi all,
I've just implemented output for ffmpeg to opengl using
rectangular ycbcr textures, and the speed is quite good (compared to
non-ycbcr mipmapped textures :-), but now I've
noticed of course I can't use it on the NVIDIA (*evil*) closed
--- Robert S. Kerr [EMAIL PROTECTED] wrote:
Alex Deucher wrote:
--- Robert S. Kerr [EMAIL PROTECTED] wrote:
[snip]
My results have been good so far. I was able to get the driver up
and
running on a monitor quickly. X seems stable and I haven't had any
crashes so far
--- Ariel Garcia [EMAIL PROTECTED] wrote:
Hi,
both on my desktop and my laptop i am getting strange hangs
when running XFree packages (both debian testing/unstable,
4.2.1-{12.1,15}) with the newer linux kernels. This happens
for me since one of the 2.5.5* kernels (and
--- Robert S. Kerr [EMAIL PROTECTED] wrote:
Alex,
I'm sending this to you directly because I have been unable to get
this
message sent to the dri-developer's list. For whatever reason, the
dri-list doesn't appear to like my e-mail address. I knew you would
have some interest in this
--- Alan Hourihane [EMAIL PROTECTED] wrote:
On Tue, Jan 27, 2004 at 07:38:59PM +, Keith Whitwell wrote:
This is a good time to remind people/establish the principle that
driver
bug fixes should be propogated to the mesa-6_0_branch of the Mesa
repository. Brian's always done a good
-- it will still be my code. The DRI code needs too
much
integration. The porting work is actively going on, however, so a
solution is in sight.
Right. Alex Deucher is working on the 2D driver. Personally I have
doubts that the VIA code will ever make it into XFree86 in more or
less
its current
--- Andrew Morton [EMAIL PROTECTED] wrote:
Are any of the DRI developers watching the drivers_video-dri account
on kernel bugzilla? bugme.kernel.org.
Begin forwarded message:
Date: Thu, 22 Jan 2004 13:28:22 -0800
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new]
--- Ryan Underwood [EMAIL PROTECTED] wrote:
Anyone know anything about it? I just picked one up because it
looked
interesting (dual R128Pro chips). They are cheap now because there
is
no more driver support from ATI. I see on the DRI page that it is
unsupported but wondered if any
So I managed to finish the first round of integration of the S3 savage
driver with Tim's savage driver. The code is still very raw and needs a
major clean up, but it works for the most part. I warn you, the code is
still a mess.
What works:
- 2D
- 3D
- non-bios mode setting
- bios mode seeting
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 6 Feb 2004 09:36:48 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
[snip]
http://www.botchco.com/alex/savage/savage-20040206.tar.gz
Nice work! I tested 2D and 3D on the savage4. It works as well as the
S3
driver and fixes the mode
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Alex,
I'm working on 3D support for Savage IX right now. I've added
register
structures for SavageIX. Now I
--- Jon Smirl [EMAIL PROTECTED] wrote:
I'm working on some code for the R200 I2C devices. There are four of
them. It's
obvious what CRT, CRT2, and DVI do. But what does MONID do?
the same thing as the others. ATI wires their cards to correspond to
the respective names, but some oems wire
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Sun, 8 Feb 2004 09:28:51 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
Alex,
I'm working on 3D support for Savage IX right now. I've added
register
structures for SavageIX. Now I
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hi,
I tracked down the Savage4 texture corruption problem last night. A
patch is attached, but it'll break ProSavages. A real solution will
have
to wait at least until the 3D driver can determine the chipset. The
whole texture upload code is
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Mon, 9 Feb 2004 16:40:19 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
I think I fixed the problem that caused your prosavage to fail. I
forgot to add PROSAVAGEDDR and TWISTER to the bci setup function
(SavageInitialize2d
an unstable
branch anyway; plus I plan to fix those problems sooner rather than
later (probably this coming week). How should we work this? I can
just commit it, or we can move to a new branch. doesn't really matter
to me.
Alex
Regards,
Felix
On Fri, 6 Feb 2004 09:36:48 -0800 (PST)
Alex
--- George Lengel [EMAIL PROTECTED] wrote:
On Saturday 07 February 2004 02:48 pm, Felix Kühling wrote:
On Fri, 6 Feb 2004 09:36:48 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
[snip]
http://www.botchco.com/alex/savage/savage-20040206.tar.gz
Nice work! I tested 2D and 3D
--- Georgi Hristov [EMAIL PROTECTED] wrote:
Hi,
stopped X and restarted it and checked XFree.log and it showed my
new
driver
loaded, but still Direct Rendering:No. I confirmed this by running
glxinfo
and it said the same thing.
As I searched the archives to the list, I
I'm forwarding this to the devel list.
Alex
__
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html---BeginMessage---
Hi all,
Recently I've discovered (after some hours of debugging) that there's a
problem
I was looking through the the databooks regarding PCI gart and I
noticed that r128, radeon, and r200 all do PCI gart the same way. that
said, I also noticed that PCI GART is limited to 4 MB of system memory
when used with a PCI card and 32 MB when used with an AGP card. I
haven't yet looked at
--- Michel Dänzer [EMAIL PROTECTED] wrote:
On Wed, 2004-02-11 at 21:26, Alex Deucher wrote:
I was looking through the the databooks regarding PCI gart and I
noticed that r128, radeon, and r200 all do PCI gart the same way.
that
said, I also noticed that PCI GART is limited to 4 MB
--- Georgi Hristov [EMAIL PROTECTED] wrote:
Just to be sure, did you check out the savage-2-0-0-branch of DRI
cvs?
do you see any files that start with 'savage' in
xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel?
Alex
hi,
at first i just pulled the head
--- Rafael Maximo [EMAIL PROTECTED] wrote:
Hi,
First i would like to say that Alex and Felix are doing a
great
job with savage driver and every day it's getting better.
I found some problems here with my savage4, now the textures
are
showing correctly and working
--- cunha17 [EMAIL PROTECTED] wrote:
Hi all,
I'm experiencing some problem with my
Savage2000(Viper II) card and DRI.
Just for the records, I followed all
recomendation I could find in and out
of this list.
First of all I recompiled my
kernel(vanilla 2.4.24, since
fedora/redhat
--- Ryan Underwood [EMAIL PROTECTED] wrote:
On Sat, Feb 14, 2004 at 11:46:19PM -0800, Alex Deucher wrote:
To elaborate on what felix said, savage2000 is a different beast
than
any of the other savages. regarding the 2D driver, I have no idea
how
its bitmap descripters are laid out
--- Marco Strack [EMAIL PROTECTED] wrote:
hi.
just checked out the most recent savage_2.0.0 branch.
enabled dri and working ;)
xv working, consoles scrambled. chromium looking good, tuxracer is
somehow a
bit choppy and not playable, but accelerated.
all gl screensavers work.
--- 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 ;)
--- Felix K#252;hling [EMAIL PROTECTED] wrote:
Hi,
I just took a brief look at the savage 2D driver. It looks like the
COB
is never enabled. On Savage4 and ProSavages it explicitly left
disabled
in SavageInitialize2DEngine. On the Savage3D/MX/IX that function is
never even called. Yet I'm
I chatted with a friend of mine who is an IP lawyer regarding s3tc.
Here was his response:
I looked at the claims, and they all seem to be
related to processing, as opposed to data structures
or protocol, so it seems as long as the driver isn't
doing any processing you should be fine. Since you
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 few
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log
--- Jack Lecou [EMAIL PROTECTED] wrote:
Any chance this is forthcoming?
I was hoping to give it a test on my laptop's embedded Savage/IX, but
the DRM module seems to want AGP only.
As I recall it does support PCI, but only with 2.4.x kernels. I don't
think anyone has tested it though.
well... a few intersting odds and ends... talk about a frustrating day!
memory management: S3's whole memory management scheme is broken. it
does no checking of available memory. it just assumes there will be
enough for front, back, depth, and textures. first texture space gets
assigned, then
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hello S3 Savage users,
[snip]
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 command and data streams should be
--- Felix Kühling [EMAIL PROTECTED] wrote:
Hello S3 Savage users,
[snip]
Felix,
I'd like to give you a hand on the 3D driver while I still have some
free time, but I have to admit, I'm somewhat intimidated. What's a
good task that I can work on to get my feet wet on the 3D side? It's
--- Chris Ison [EMAIL PROTECTED] wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a HUGE
performance increase over my older PCI Radeon 9000. And for windows
sure enough, the overkill demo in quakeforge jumped from 33fps to
122fps within Windows.
When I tried it in
--- Dieter Nützel [EMAIL PROTECTED] wrote:
Am Freitag, 20. Februar 2004 13:49 schrieb Steve Dawson:
Alex Deucher wrote:
--- Chris Ison [EMAIL PROTECTED] wrote:
I brought an AGP Radeon 9200SE yesterday, thinking I would get a
HUGE
performance increase over my older PCI Radeon 9000
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module name:xc
Repository: xc/xc/programs/Xserver/hw/xfree86/drivers/savage/
Changes by: [EMAIL PROTECTED] 04/02/17 12:38:04
Log
--- Felix Kühling [EMAIL PROTECTED] wrote:
On Fri, 20 Feb 2004 08:28:55 -0800 (PST)
Alex Deucher [EMAIL PROTECTED] wrote:
--- Felix K_hling [EMAIL PROTECTED] wrote:
On Tue, 17 Feb 2004 12:38:04 -0800
Alex Deucher [EMAIL PROTECTED] wrote:
CVSROOT:/cvs/dri
Module
201 - 300 of 1146 matches
Mail list logo
