Re: [Dri-devel] geartrain broken on r200?
Am Sonntag, 8. Februar 2004 15:14 schrieb Dieter Nützel: > Ian Romanick wrote: > > Roland Scheidegger wrote: Ups, forgotten something. Do you see such huge DRI-Devel List delays, too? I haven't even received your mails about this topic... Greetings, Dieter --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
Alex, I'm working on 3D support for Savage IX right now. I've added register structures for SavageIX. Now I need to find out the chipset type in the 3D driver. That requires a few small modifications to the 2D driver. I'm not sure if I should work with the old or your new 2D driver. I'd prefer to work with your version, but I'd feel much more comfortable if it was in CVS so that we can keep our work in sync. Regards, Felix On Fri, 6 Feb 2004 09:36:48 -0800 (PST) Alex Deucher <[EMAIL PROTECTED]> wrote: > So I managed to finish the first round of integration of the S3 savage > driver with Tim's savage driver. [snip] > http://www.botchco.com/alex/savage/savage-20040206.tar.gz > > Alex --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
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 need to find out the chipset type in > > the > > 3D driver. That requires a few small modifications to the 2D driver. > > I'm > > not sure if I should work with the old or your new 2D driver. I'd > > prefer > > to work with your version, but I'd feel much more comfortable if it > > was > > in CVS so that we can keep our work in sync. > > > > That's fine with me. My only reason for not putting it into cvs is > that there are still some broken bits, but I guess it's 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. I think you could just commit to the existing branch for now. I sort of planned to make a new branch when we move the 3D driver to Mesa CVS, much like what's happening with mach64 right now. I just havn't decided when the right time for that would be. Maybe we can talk about that on IRC tomorrow. > > Alex > Felix > [snip] --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
--- 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 need to find out the chipset type > in > > > the > > > 3D driver. That requires a few small modifications to the 2D > driver. > > > I'm > > > not sure if I should work with the old or your new 2D driver. I'd > > > prefer > > > to work with your version, but I'd feel much more comfortable if > it > > > was > > > in CVS so that we can keep our work in sync. > > > > > > > That's fine with me. My only reason for not putting it into cvs is > > that there are still some broken bits, but I guess it's 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. > > I think you could just commit to the existing branch for now. I sort > of > planned to make a new branch when we move the 3D driver to Mesa CVS, > much like what's happening with mach64 right now. I just havn't > decided > when the right time for that would be. Maybe we can talk about that > on > IRC tomorrow. Sounds good. I'll commit what I have this afternoon or tomorrow depending on my schedule. Alex __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] patch: texcombine refactor for radeon
like the R200 one. It doesnt contain intendation fixup yet. I tried only with q3a. best regards, Andreas mesa_radeon_texcombine_refactor.diff Description: Binary data
[Dri-devel] ATI I2C, MONID
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? = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] ATI I2C, MONID
--- 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 the cards such that MONID might be used for DVI or CRT2, DVI might be used for CRT, etc. Alex > = > Jon Smirl > [EMAIL PROTECTED] > __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] New DRM design (was ATI I2C, MONID)
I have a new version of DRM at bk://mesa3d.bkbits.net/drm In it's current form it's 2.6 kernel only. Some support is generic but I've mainly be working on an R200. It is still under development with lots of work to do. Major features: 1) Get VBIOS ROM contents IOCTL 2) Driver automaps the registers and framebuffer (map can't be changed) 3) Supports sysfs 4) Generates a hotplug event when loaded, event runs a vm86 reset program if needed. 5) IOCTL support to set active VGA device when multiple cards are present (no more playing with PCI bridges from user space) 6) radeon only so far, adds kernel level I2C devices which makes EDID appear in sysfs 7) you can't have it and framebuffer loaded for the same device since they can't share PCI IDs, sysfs, hotplug, etc. Right now I'm building a mode setting API for it. My plan is something like this: 1) machine boots in VGA mode 2) DRM driver is built into the kernel 3) when hotplug event happens (early boot) these are done in user space... a) card is reset if needed b) card is initialized and CP is started, optimal mode is set c) a pseudo terminal is created, takeover_console is routed to the pseudo terminal d) very small user space app listens to pseudo terminal and implements terminal emulator using DRM API 4) Full user space starts, a) OpenGL library can be loaded b) initial app execs more complex app which implements VTs using OpenGL API c) you can run one of these for each video card -- multiuser support 5) xserver starts a) uses OpenGL for it's API, no access to framebuffer. = Jon Smirl [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
--- 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 need to find out the chipset type in > the > 3D driver. That requires a few small modifications to the 2D driver. > I'm > not sure if I should work with the old or your new 2D driver. I'd > prefer > to work with your version, but I'd feel much more comfortable if it > was > in CVS so that we can keep our work in sync. > That's fine with me. My only reason for not putting it into cvs is that there are still some broken bits, but I guess it's 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 Deucher <[EMAIL PROTECTED]> wrote: > > > So I managed to finish the first round of integration of the S3 > savage > > driver with Tim's savage driver. > [snip] > > http://www.botchco.com/alex/savage/savage-20040206.tar.gz > > > > Alex __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
--- 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 on the savage4. It works as well as > the S3 > > driver and fixes the mode setting problem I reported earlier > (stretching > > 1279 pixesl to 1280). Xv is indeed broken. One more thing I noticed > is > > that the text console is messed up after starting X. It looks like > it's > > showing the wrong part of video memory. At the top of the screen > there > > is still some text, but on the bottom there is just some funky > random > > stuff. And I don't see what I type. > > I am guessing I did something stupid. > > I finally have a good kernel built that is working nicely. I used > 2.4.23. > I pulled the CVS source again and then downlaoded the above source > tarball and > put it in /development/xc/xc/programs/Xserver/hw/xfree86/drivers > since this > is what the tar directory structure looked like to me (and untarred > it). I > then went to /development/xc/xc and did a 'make World' which went on > and on > and when I was through I had a new XFree86 executable and > savage_drm.o > savage_dri.o and some others. I then did 'make install' which copied > > savage_drv.o to /usr/X11R6/lib/modules/drivers. I also copied > savage_drm.o > to /usr/X11R6/lib/modules/dri since I saw the other *_dri.o files > there. I there are only 3 files you need to worry about: savage_drv.o - 2d driver savage_dri.so - 3d driver savage.o - kernel DRM module > 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 saw someone had similar > experience > trying to compile for the ProSavageDDR and Alex said the savage > kernel module > had to be compiled separate. So I went to > /development/xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel > and > typed 'make Makefile.linux' but got the message back 'Nothing to be > done for > `Makefile.linux'.'. So, did I unpack the tar package in the wrong > place or am > I still missing something? run 'make -f Makefile.linux' to build the kernel module. you may need to use 'make -f Makefile.linux LINUXDIR=/path/to/kernel/src' if it can't find your kernel source. also make sure you've run at least 'make dep' on the kernel source. > > How close am I? Just about there. once the kernel module is built copy it into your module tree and run 'depmod -a' to update your module dependencies. then load agpgart and savage and start X. Alex __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Savage: integrated driver
Hi, I built the module with the -f flag which made the difference. I copied it to my modules directory in my kernel tree and then did a modprobe savage. Then I killed X and restarted it. My XFRee86.0.log shows (II) SAVAGE(0): [junkers] sarea_priv_offset:0x0898 (II) SAVAGE(0): Direct rendering enabled (==) RandR enabled but if I run 'glxinfo' I get name of display: :0.0 display: :0 screen: 0 direct rendering: No 'glxgears gives me between 200 and 225 FPS when I run it. Is there something else I can run to see if I do have hardware 3D or not? There is a problem with the driver. My terminals (accessed by CTRL-ALT-F*) are all corrupted. It is like there are four columns of text across the screen each one with only a part of each letter. I did not see this with the 1.1.27t version I got from http://www.probo.com/timr/savage40.html. -- George Lengel (Worm) "Kohli head. You could have been lava bones. --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] mach64-0-0-7-branch status..
Okay I've checked in the DRM and Xserver changes to the above branch, I've added the PCI ids I think are correct for the chip variations, I'll hopefully get around to testing it in the next couple of days, (just have to drag out the laptop :-) If anyone else has a chance feel free to give it a go .. I'm not sure the Mesa driver works yet!! Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] GL_VERSION 1.5 when indirect rendering?
Am 2004.02.07 09:44:39 +0100 schrieb(en) Ian Romanick: [...] > as well. I'll try to have a patch tomorrow. The server-side of things Looks like its fixed in DRI CVS with/since your patch. I have to admit that I only tried with the new libGL.so and old Xserver/libs, not with old libGL and new Xserver. OpenGL version string: 1.2 (1.5 Mesa 6.1) [...] > think it needs the Ultimate Refactor...'rm -rf programs/Xserver/GL' ... and I was told 'rm -rf' means "read mail, really fast!" ;) greetings, Andreas --- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
