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 done some testing and it seems to work
fine. The patch only touches the 2D d
The r100 and r200 of course. :)
Alex
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> Merge which? The r100 & r200 or the 500TX & gamma? I think it would
> be
> a good idea to merge both, but "merging" the GLINT drivers will be
> much
> easier (since one of them hasn't been created yet!). H
--- Michel Dänzer <[EMAIL PROTECTED]> wrote:
> You need to find out where the register gets overwritten. I don't see
> any code doing it, and I've never experienced this problem.
Are you SMP? I have hyperthreading turned on. I'll try it again with SMP turned
off.
=
Jon Smirl
[EMAIL PROTECTED
Linus Torvalds wrote:
On Mon, 8 Sep 2003, Jon Smirl wrote:
I think I have tracked this down to the DRM drivers in the kernel not matching
the ones in DRI CVS. Some of the structures in the initialization IOCTL have
changed which caused one of the ring pointers to initialize to zero instead of
wha
On Tue, 2003-09-09 at 23:30, Jon Smirl wrote:
>
> This line in radeon_cp is causing the problem with the ring pointers.
> dev_priv->agp_vm_start = RADEON_READ( RADEON_CONFIG_APER_SIZE );
> agp_vm_start is coming out zero and I don't think it should be.
Indeed, as the name suggests, it's e
Linus Torvalds wrote:
On Tue, 9 Sep 2003, Linus Torvalds wrote:
I can do a new merge [ ... ]
Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it
lately, and I wonder if people are still using the old one for
development?
In the meantime, I could add you to the sf developer
--- Jon Smirl <[EMAIL PROTECTED]> wrote:
> Date: Tue, 9 Sep 2003 13:33:26 -0700 (PDT)
> From: Jon Smirl <[EMAIL PROTECTED]>
> Subject: Re: [Dri-devel] Fault in radeon DRM module
> To: Linus Torvalds <[EMAIL PROTECTED]>
>
> I haven't located the exact cause of this yet. Version skew is still my top
On Wed, 2003-09-10 at 01:17, Jon Smirl wrote:
> In this case I loaded the radeon kernel driver from CVS. I am running XFree
> from RH9. No code from embedded is involved. This is with i875P AGP.
>
> I first started X and it ran without problem.
> I stopped it and started it again.
> I get an oops
On Tue, 2003-09-09 at 22:11, Linus Torvalds wrote:
> On Mon, 8 Sep 2003, Jon Smirl wrote:
> >
> > I think I have tracked this down to the DRM drivers in the kernel not matching
> > the ones in DRI CVS. Some of the structures in the initialization IOCTL have
> > changed which caused one of the ring
In this case I loaded the radeon kernel driver from CVS. I am running XFree
from RH9. No code from embedded is involved. This is with i875P AGP.
I first started X and it ran without problem.
I stopped it and started it again.
I get an oops in radeon_do_cp_start()
It may be that embedded and Xfre
Alex Deucher wrote:
--- Ian Romanick <[EMAIL PROTECTED]> wrote:
In any case, I would really *NOT* like to see another driver end up
like
the r100 / r200 driver. The MGA driver, where multiple chips in the
same family are supported by the same binary, is a much better model
to
Is it worth tryin
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 design
On Tue, 2003-09-09 at 13:12, Linus Torvalds wrote:
> On Tue, 9 Sep 2003, Linus Torvalds wrote:
> >
> > I can do a new merge [ ... ]
>
> Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it
> lately, and I wonder if people are still using the old one for
> development?
It is
--- 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 *VER
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 establi
On Tue, 9 Sep 2003, Linus Torvalds wrote:
>
> I can do a new merge [ ... ]
Is the "dri.freedesktop.org" tree up-to-date? Nothing has happened on it
lately, and I wonder if people are still using the old one for
development?
Linus
On Mon, 8 Sep 2003, Jon Smirl wrote:
>
> I think I have tracked this down to the DRM drivers in the kernel not matching
> the ones in DRI CVS. Some of the structures in the initialization IOCTL have
> changed which caused one of the ring pointers to initialize to zero instead of
> what it needed.
On Tue, 2003-09-09 at 07:39, Alex Deucher wrote:
> and, from the log:
>
> fxkuehl: I have a Savage/IX (or something similar) in my ThinkPad
> T21.
> ...
> so is the savage4 the same sort of thing as a savage mx/ix?
> ...
> anholt: I believe so.
>
> Actually the savage mx/ix chips are based on
Eric Anholt wrote:
Just a headsup on what's going on with the CVS. We've got several of
the developers added (fxkuehl, daenzer, keithw, idr, jonsmirl, akin,
anholt). At this point I'm just waiting to get a new snapshot of the
repository to move it in. Unfortunately, the cvs.sourceforge.net
webs
Alex Deucher wrote:
To do that we're going to "port" the *OLD* 500TX driver to DRI.
:)
500tx is a what?
anholt: The GLINT before the MX.
...
anholt: It should be *much* faster. The Delta does all the
geometry setup. This is the mode the current gamma driver uses.
hmm
Part of this work may
Just a headsup on what's going on with the CVS. We've got several of
the developers added (fxkuehl, daenzer, keithw, idr, jonsmirl, akin,
anholt). At this point I'm just waiting to get a new snapshot of the
repository to move it in. Unfortunately, the cvs.sourceforge.net
website is down, so I've
Dieter Nützel wrote:
Am Dienstag, 9. September 2003 00:22 schrieb Ian Romanick:
Dieter Nützel wrote:
Building executable /opt/VTK/V4.0/VTK/bin/vtk...
/usr/X11R6/lib/libGL.so: undefined reference to
`glXGetContextReadDrawable' collect2: ld returned 1 exit status
This was fixed by file version 1.59
315 is NOT from the 300 series! it will NOT work! that is the new
series from sis and has a new core.
Check out Thomas' page for more info:
http://www.winischhofer.net/linuxsisvga.shtml
from the page:
"There are currently four groups of SiS VGA controllers:
* The old series (5597/5598, 632
from the log:
To do that we're going to "port" the *OLD* 500TX driver to DRI.
:)
500tx is a what?
anholt: The GLINT before the MX.
...
anholt: It should be *much* faster. The Delta does all the
geometry setup. This is the mode the current gamma driver uses.
hmm
Part of this work may lead i
The anon CVS problem is just as bad for Mesa as DRI, it's just that fewer
people are using Mesa so we don't hear as many complaints. Shouldn't we stay in
the same CVS with DRI? there are huge amounts of shared code
Note that people with SF logins to the project never see these problems.
--- Brian
Alex Deucher <[EMAIL PROTECTED]> wrote:
> [...] you can still find
> 300/305 PCI/AGP cards on some websites usually labeled as "sis 305
> 32mb" or similar.
Thanks for explaining. I assume I found a card with an SiS 315.
I'll see if it works, otherwise I'll give it to a friend running
Windows .
There aren't really any major brands that make sis cards that I've
heard of... usually they are sold labeled as "3D video card" or "Super
VGA card" with no discernable manufacturer on the box. some older oem
notebooks (clevos and such) use 630 chips; Sony made slim desktops
(LX-700/800/900) for a
Dieter Nützel wrote:
/opt/Mesa> cvs update
cvs [update aborted]: connect to cvs.mesa3d.sourceforge.net:2401 failed:
Connection refused
I have no plans to move the Mesa CVS repository at this time.
The anon CVS problems don't seem as critical for Mesa. I'm willing to
wait a bit longer to see if
/opt/Mesa> cvs update
cvs [update aborted]: connect to cvs.mesa3d.sourceforge.net:2401 failed:
Connection refused
Thanks,
Dieter
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Am Montag, 8. September 2003 09:26 schrieb Eric Anholt:
> On Sun, 2003-09-07 at 07:42, Dieter Nützel wrote:
> > Am Samstag, 6. September 2003 23:29 schrieb Eric Anholt:
> > > On Sat, 2003-09-06 at 14:16, Eric Anholt wrote:
> > > > CVSROOT:/cvs/dri
> > > > Module name:xc
> > > > Reposito
Am Dienstag, 9. September 2003 00:22 schrieb Ian Romanick:
> Dieter Nützel wrote:
> > Building executable /opt/VTK/V4.0/VTK/bin/vtk...
> > /usr/X11R6/lib/libGL.so: undefined reference to
> > `glXGetContextReadDrawable' collect2: ld returned 1 exit status
>
> This was fixed by file version 1.59 of l
Jon Smirl wrote:
I think I have tracked this down to the DRM drivers in the kernel not matching
the ones in DRI CVS. Some of the structures in the initialization IOCTL have
changed which caused one of the ring pointers to initialize to zero instead of
what it needed. The minor version number prob
32 matches
Mail list logo
