Re: [Dri-devel] S3 VIRGE DRI
On Mon, 2002-07-08 at 18:36, David Willmore wrote: Log bits: (--) PCI:*(1:0:0) S3 ViRGE/MX rev 6, Mem @ 0x4000/26 (II) LoadModule: s3virge (II) Loading /usr/X11R6/lib/modules/drivers/s3virge_drv.o (II) Module s3virge: vendor=The XFree86 Project compiled for 4.2.0, module version = 2.0.0 Module class: XFree86 Video Driver ABI class: XFree86 Video Driver, version 0.5 (II) S3VIRGE: driver (version 2.0.0) for S3 ViRGE chipsets: virge, 86C325, virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2, 86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365, trio 3d/2x, 86C362, 86C368 (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset virge mx found (**) S3VIRGE(0): Depth 16, (--) framebuffer bpp 16 (==) S3VIRGE(0): RGB weight 565 (==) S3VIRGE(0): Default visual is TrueColor (==) S3VIRGE(0): Using HW Cursor (==) S3VIRGE(0): Using fb. (==) S3VIRGE(0): mx_cr3a_fix. (==) S3VIRGE(0): XVideo allowed (depends on chipset). (II) S3VIRGE(0): initializing int10 (II) S3VIRGE(0): Primary V_BIOS segment is: 0xc000 (II) S3VIRGE(0): VESA BIOS detected (II) S3VIRGE(0): VESA VBE Version 2.0 (II) S3VIRGE(0): VESA VBE Total Mem: 4096 kB (II) S3VIRGE(0): VESA VBE OEM: S3 Incorporated. M5 BIOS (II) S3VIRGE(0): VESA VBE OEM Software Rev: 1.0 (II) S3VIRGE(0): VESA VBE OEM Vendor: S3 Incorporated. (II) S3VIRGE(0): VESA VBE OEM Product: VBE 2.0 (II) S3VIRGE(0): VESA VBE OEM Product Rev: Rev 1.1 (--) S3VIRGE(0): Chipset: virge mx (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): I2C bus I2C bus initialized. (II) S3VIRGE(0): I2C device I2C bus:ddc2 registered. (II) S3VIRGE(0): I2C device I2C bus:ddc2 removed. (==) S3VIRGE(0): Using gamma correction (1.0, 1.0, 1.0) (--) S3VIRGE(0): videoram: 4096k (--) S3VIRGE(0): COMPAQ M5 BIOS found (--) S3VIRGE(0): assuming RefCLK value of 14.318 MHz (--) S3VIRGE(0): Detected current MCLK value of 100.227 MHz (--) S3VIRGE(0): LCD size 1024x768, clock 65.028 MHz (II) S3VIRGE(0): Monitor0: Using hsync range of 31.50-48.50 kHz (II) S3VIRGE(0): Monitor0: Using vrefresh range of 40.00-70.00 Hz (II) S3VIRGE(0): Clock range: 20.00 to 270.00 MHz (--) S3VIRGE(0): Virtual size is 1024x768 (pitch 1024) (**) S3VIRGE(0): Default mode 1024x768: 65.0 MHz, 48.4 kHz, 60.0 Hz (II) S3VIRGE(0): Modeline 1024x768 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (==) S3VIRGE(0): DPI set to (75, 75) (II) S3VIRGE(0): *** using default video mem config (II) S3VIRGE(0): ps3v-videoRambytes =4194304 (II) S3VIRGE(0): ps3v-bufferSize = 96 (II) S3VIRGE(0): ps3v-texSize = 655360 (II) S3VIRGE(0): Reserved back buffer at offset 0x18c000 (II) S3VIRGE(0): Reserved depth buffer at offset 0x276000 (II) S3VIRGE(0): Reserved 640 kb for textures at offset 0x36 (II) S3VIRGE(0): Reserved hw cursor at offset 0x3ffc00 (==) S3VIRGE(0): Write-combining range (0x4000,0x40) (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): CheckSymbol: GlxSetVisualConfigs OK (II) S3VIRGE(0): CheckSymbol: DRIScreenInit OK (II) S3VIRGE(0): CheckSymbol: drmAvailable OK drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 7, (OK) drmGetBusid returned '' (II) S3VIRGE(0): [drm] created s3v driver at busid PCI:1:0:0 (II) S3VIRGE(0): [drm] added 8192 byte SAREA at 0xcc8b1000 (II) S3VIRGE(0): [drm] mapped SAREA 0xcc8b1000 to 0x4001c000 (II) S3VIRGE(0): [drm] framebuffer handle = 0x4000 (II) S3VIRGE(0): [drm] added 1 reserved context for kernel (II) S3VIRGE(0): Going to S3VDRIMapInit (II) S3VIRGE(0): [drm] Registers = 0x4100 (II) S3VIRGE(0): *** bufs(0) = 16 (II) S3VIRGE(0): *** bufs(1) = 1 (II) S3VIRGE(0): [drm] buffers mapped with 0x8579058 (II) S3VIRGE(0): [drm] 17 DMA buffers mapped (II) S3VIRGE(0): Coming from S3VDRIMapInit (II) S3VIRGE(0): Going to S3VDRIPciInit (II) S3VIRGE(0): Coming from S3VDRIPciInit (II) S3VIRGE(0): Going to S3VInitVisualConfigs (II) S3VIRGE(0): Coming from S3VInitVisualConfigs (II) S3VIRGE(0): [dri] Visual configs initialized (**) S3VIRGE(0): Using FB (II) S3VIRGE(0): ps3v-videoRamKbytes = 4096 (II) S3VIRGE(0): Memory manager: ps3v-backOffset = 1622016; width_bytes = 2048;scanlines = 2047 (II) S3VIRGE(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles CPU to Screen color expansion Solid
Re: [Dri-devel] S3 VIRGE DRI
On Mon, 2002-07-08 at 06:51, David Willmore wrote: In X server startup, the drm fails to load. If I exit and try to modprobe it myself, I get errors about a bunch of AGP symbols not being resolved Try recompiling the module with (in s3v.h) __HAVE_AGP set to 0 (I should make this the default...) Lemme know, vale, - max lingua --- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Fwd: Re: [Dri-devel] RE: Dri-devel S3 VIRGE DRI in CVS now
On Thu, 2002-07-04 at 16:59, Dieter Nützel wrote: Sorry for my repost but I got no answer from you. I did not reply since I am still waiting an answer from S3/Via about this ; ) The same applies to the guy who asked me some infos about electrical specifications. So do you think it is possible now to get S3TC (S3 hardware texture compression into all the drivers? Vale, - max --- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] s3virge fixes in CVS
On Thu, 2002-07-04 at 17:28, Jens Owen wrote: Max, Have you seen how the Radeon driver has different routines for 2D accelleration with DRI enabled (uses CP) vs DRI disabled (uses MMIO)? Interesting. Really. I was not aware of that. I will get in touch with Kevin Brosius later this month and we will discuss about it. Thanks, yours, -max lingua --- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: S3 VIRGE DRI in CVS now
On Sat, 2002-06-29 at 23:27, Anders Haugen wrote: Hi, i did some changes and got the s3virge code from the cvs working here. seems the dma stuff wasn't initializing at all for me. 1) Your patches seem ok to me. I am quite busy up to 2nd half of July, so I wont be able to fully test them though, and then to commit to CVS. 2) Since you seem to be keen-eyed when it comes to coding, you could take the task to check what we could do to turn 2D acceleration on again. Code is already there, but something is not interacting well, since it still locks after a while. If you succeed the driver will greatly gain from this. Otherwise I will have a look later on July (even if would prefer to focus on Savage4/ProSavage driver dev) 3) Anybody else had luck with Anders patches? Vale, -max lingua --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: Failure to build the s3virge-0-0-1-branch
On Wed, 2002-06-26 at 12:45, José Fonseca wrote: Max, is there any file related to i830 missing or outdated in the s3virge branch? Or perhaps the i830 driver should be disabled on this branch. There was a stale #if 0 in drm/kernel/drm.h. Fixed now. Could you please let me know if this is enough to build things fine? It was needed to build thing against 4.1.0. Since sometimes people ask me for tarballs, and they do not have the latest code. I checked config/cf/host.def too, to see it was ok. It should just build support for s3virge. i830 was disabled both in XF86CardDrivers than DriDrivers. Why is it being built? Thanks, - max lingua --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Failure to build the s3virge-0-0-1-branch
On Wed, 2002-06-26 at 15:52, Alan Hourihane wrote: I'll do the merge now for you. Obviously this branch won't build at all until fixed up for the new drmCommand stuff. I have been away a couple of months from active development. Where could I gather more infos about drmCommand? Is it easy to understand just peeking at the code of other drivers? What are its benefits? Alan. --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: S3 VIRGE DRI in CVS now
Do you mean S3 Savage MX or is it a S3 virge MX??? Thanks, JrSky. S3 *** Virge *** MX. For Savage MX try utah. Or wait for us to code a driver ; ) Vale, - max --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: [Dri-patches] CVS Update: xc (branch: s3virge-0-0-1-branch)
On Tue, 2002-06-25 at 16:34, José Fonseca wrote: On Tue, Jun 25, 2002 at 02:43:39PM +0200, max wrote: In http://dri.sourceforge.net/snapshots/bleeding-edge/ as mach64 branch, the old radeon tcl branch, and soon the radeon 8500 branch, or for any other branch (x86 Linux only I'm afraid). OK. It's just a matter of a few keypresses for me to get the s3virge branch built every night. The only trouble you would have would be to give feedback to the people using those binary snapshots (which could be potential more than those willing to build from CVS directly). Not a problem, I will do. Besides this inconvenience, the other reason why I ask before enabling them was to know if the branch is in shape for releasing binary snapshots or if there are any caveats that would prevent that. Well, the driver is quite stable (it will let you run multiple opengl apps too). You will just have to disable 2D acceleration and configure your XF86config. I can write a short README if you want. Vale, - max lingua --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] Re: S3 VIRGE DRI in CVS now
On Tue, 2002-06-25 at 16:48, John J. Tobin wrote: Is the Virge MX+ supported? This is the one that was commonly found in notebooks, as that is what I will be testing it out on. Yep. That is the laptop on which I developed my driver on. so it will run better on it than on everything else ; ) All the virges models should be supported. Vale, -max lingua --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] S3 VIRGE DRI in CVS now
On Tue, 2002-06-25 at 19:28, Jens Owen wrote: Wow, looks like you've been busy. Let's see what kind of feedback you get. A bit I had to study (laws + Savage4 docs). A bit I have to workc. A bit I had to drive my Toyota MR2 Roadster. A bit I had to live. ; ) Feedback is starting to rise. Should I announce the branch on freshmeat? Vale, -max lingua --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
