Re: [Xpert]i830M: Missing BIOS Mode Info
Hi Manuel! Your problem is that DDC is failing, so it can't figure out what modes your monitor / lcd is capable of. You'll have to hardcode the modelines in your XF86Config. Here is some which I have made especially for testing the 830M driver. Put them in your Monitor section and in your screen section use the corresponding modeline names, e.g. Subsection Display Depth 24 Modes 1024x768@75Hz ViewPort 0 0 Virtual 1024 768 EndSubSection snip -- snip -- snip Modeline 640x350@85Hz 31.50 640 672 736 832 350 382 385 445 +hsync -vsync Modeline 640x400@85Hz 31.50 640 672 736 832 400 401 404 445 -hsync +vsync Modeline 720x400@85Hz 35.50 720 756 828 936 400 401 404 446 -hsync +vsync Modeline 640x480@60Hz 25.20 640 656 752 800 480 490 492 525 -hsync -vsync Modeline 640x480@73Hz 31.50 640 664 704 832 480 489 491 520 -hsync -vsync Modeline 640x480@75Hz 31.50 640 656 720 840 480 481 484 500 -hsync -vsync Modeline 640x480@85Hz 36.00 640 696 752 832 480 481 484 509 -hsync -vsync Modeline 800x600@56Hz 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync Modeline 800x600@60Hz 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync Modeline 800x600@72Hz 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync Modeline 800x600@75Hz 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync Modeline 800x600@85Hz 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync Modeline 1024x768@60Hz 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync Modeline 1024x768@70Hz 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync Modeline 1024x768@75Hz 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync Modeline 1024x768@85Hz 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync Modeline 1152x864@75Hz 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync Modeline 1280x960@60Hz 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync Modeline 1280x960@85Hz 148.50 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync Modeline 1280x1024@60Hz 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync Modeline 1280x1024@75Hz 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync Modeline 1280x1024@85Hz 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync Modeline 1600x1200@60Hz 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync Modeline 1600x1200@65Hz 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync Modeline 1600x1200@70Hz 189.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync Modeline 1600x1200@75Hz 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync Modeline 1600x1200@85Hz 229.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync snip -- snip -- snip I am having some problems with the new i830M support in CVS. More precisely, I have checked out and compiled the tree tagged `xf-4_1_99_2'. I did this on a i830M-based Dell Laptop (a Latitude C400) that runs the latest Linux kernel (namely, 2.4.16). I have compiled the kernel with AGP GART support and I have copied the i830.o DRM kernel module into the right place in `/lib/modules/2.4.16/'. X works fine in 8bpp up to 1024x768 and in 16bpp in 640x480. When I use the latter, DRI also initialises without any problems. So, it seems as if I got most of the installation right. However, the problem is that witn 16bpp I can't go beyond 640x480 and 24bpp doesn't work at all (despite this being advertised in the i810 readme and being within the capability of the hardware). When I attempt to run higher resolutions in 16bpp, I get the following error message: (EE) I810(0): No matching modes found in configuration file. (EE) I810(0): Only the following modes are supported by the BIOS in this bpp: (EE) I810(0): 640x480 (EE) I810(0): Please choose one of these modes. I suspect that this may be related to either the warning (WW) I810(0): Bad V_BIOS checksum and/or the fact that the system doesn't seem to support DDC; in fact, just before the fatal error, I get (II) I810(0): VESA VBE DDC supported (II) I810(0): VESA VBE DDC Level none (II) I810(0): VESA VBE DDC transfer in appr. 0 sec. (II) I810(0): VESA VBE DDC read failed (==) I810(0): DPI set to (75, 75) I have made sure that the driver allocated enough RAM for AGP, namely 32MB. I have also played with modelines and with an explicit `DacSpeed' option. All to no avail. I have had a quick look at the source and it seems that it is the routine `I830VESAGetModeInfo()' in `i830_driver.c', which is responsible for obtaining the information. Somehow it seems to come up with less modes than the machine really supports. I have read somewhere on Intel's web pages that the i830m allocates 2MB, 4MB, or 8MB of basic video memory dependent on the BIOS settings of the machine. Unfortunately, the Dell C400 doesn't seem to have such a
[Xpert]XF86Config file using Cybeblade XP on Solaris 8
Anyone be nice enough to send me a working copy of XF86Config file they have to suit a Satellite 4600 running Solaris 8. I have been having quite a few problems getting it working, particularly as it quits in the card database when using xf86config. Gets to about H section and then quits automatically. Is There a patch for this. Thanks Greg Turnbull Please send file to [EMAIL PROTECTED]
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
Mac Cody writes: I'm afraid that is what I may have to do. In fact I'm already preparing to do so (pulling the necessary .tgz files off the Slackware 7.1 CDROM). Tis a pity. XFree86 4.1.0 appears to be faster on my cards than 3.3.6. Hi Mac, the Slacware 7.1 CD should also contain the 3.3.6 sources. It shouldn't be too difficult to just implement interlace support. Why don't you check in the 3.3 code how it is done and add this feature to 4.x? Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Plane masking with Xlib??
Hi Jim Mark, Thanks for the reply, my program is working in HP unix, I am able to get both the out put in a same window(overlayed), the only change in Linux code is in XtOpenDisplay() part, there in HPUX the function call using the display parameter as 0:0 and second one using 0:1. In Linux the display perameters with 0:1 is giving error, so I made it NULL for both the XtOpenDisplay() function calls, how to achive in Linux the same functionality, since I am using NULL as display parameter I am getting two different display, unable to achive overlay. I am new to this X-window programming and overlay concept, pls explain. thanks in advance, Bala. --- Jim Gettys [EMAIL PROTECTED] wrote: Manipulating the plane mask on truecolor displays typically has little use these days: it is really a holdover hack from the days of pseudocolor. If you want to take two images and composite them, you really want to use the Render extension these days, at least if you are using XFree86. - Jim -- Jim Gettys Cambridge Research Laboratory Compaq Computer Corporation [EMAIL PROTECTED] __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]SiS630 Xv performance
I have a laptop with a SiS630 chipset and use XFree86 4.1 (sis driver with the vesafb hack). When I play a dvd in windowed mode (720x576) with xine and I use XVideo the cpu(1.1Ghz P3) is utilized at 66% while playing with XShm the cpu is utilized only at 31% ! (the same with mplayer) This effect is the same at all colordepths (16bpp and 24bpp). I thought Xv should take the strain off the cpu a bit... Anyone has an idea what may cause the problem ? Thanks, -Andre. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]2 Video cards
Hi all! I have 2 video cards on my Linux server this cards detected as --XFree86.0.log--- (--) PCI: (0:14:0) S3 Trio64V2/DX or /GX rev 22, Mem @ 0xd400/26 (--) PCI:*(1:0:0) ATI Mach64 GB rev 92, Mem @ 0xd900/24, 0xdb00/12, I/O @ 0xa0 -- But when my Xwindows 4.1.0 starts, only one card work: ATI Mach64. Why? I have enable S3 in XF86Config --- Section DeSection Device Identifier ATI Mach64 BusID PCI:1:0:0 Driver ati # unsupported card VideoRam8192 # Insert Clocks lines here if appropriate EndSection Section Device Identifier S3V+ Chipset generic Driver vga BusID PCI:0:14:0 # unsupported card VideoRam1024 # Insert Clocks lines here if appropriate EndSection Section Screen Identifier Screen 1 Device ATI Mach64 Monitor Samsung1 DefaultDepth 16 .. Section Screen Identifier Screen 1 Device ATI Mach64 Monitor Samsung1 DefaultDepth 16 ... Missing some line? Sorry for my bad English -- Good Luck! Sergey Pivovaroff ICQ: 83441469, Home page http://pivik.kiev.ua ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
On Tue, Dec 18, 2001 at 03:07:29PM +0100, Andre Werthmann wrote: I have a laptop with a SiS630 chipset and use XFree86 4.1 (sis driver with the vesafb hack). When I play a dvd in windowed mode (720x576) with xine and I use XVideo the cpu(1.1Ghz P3) is utilized at 66% while playing with XShm the cpu is utilized only at 31% ! (the same with mplayer) This effect is the same at all colordepths (16bpp and 24bpp). I thought Xv should take the strain off the cpu a bit... Anyone has an idea what may cause the problem ? It is because the driver uses memcpy for transferring of the data. The correct way to solve this is to add dma support. In current cvs XF86 r128 does this so it can be used as a reference implementation. Thanks, -Andre. Bye, Peter Surda (Shurdeek) [EMAIL PROTECTED], ICQ 10236103, +436505122023 -- rm -f /bin/laden msg02568/pgp0.pgp Description: PGP signature
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
Egbert Eich wrote: Hi Mac, the Slacware 7.1 CD should also contain the 3.3.6 sources. It shouldn't be too difficult to just implement interlace support. Why don't you check in the 3.3 code how it is done and add this feature to 4.x? Egbert. Hi, Hmmm. That will have to be another project added to the list of projects I'm wanting to do. I'll have to upgrade my garage computer to Slackware 8.0 (including the XFree86 4.1.0 sources) and then get the XFree86 3.3.6 sources from the Slackware 7.1 CDROM. Not a difficult undertaking, but I've some other tasks I must get back to. It was hoping that my upgrade to Slackware 8.0 would be a weekend activity, but I've spent two weeks on it now. Can't guess when I'll get to interlace support or the amount of work involved. I'll probably start on it this Spring. In the meantime, I've taken the XF86_SVGA binary from 3.3.6 and installed it on my system. Everything else is still the 4.1.0 distribution from Slackware 8.0. I'm now running back at 1024x768 on my NEC MultiSync 3V with the Cirrus PCI video card. No monitor shutdowns occuring. It is a curious thing! Mac ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
On Tue, 18 Dec 2001, Peter Surda wrote: On Tue, Dec 18, 2001 at 03:07:29PM +0100, Andre Werthmann wrote: I have a laptop with a SiS630 chipset and use XFree86 4.1 (sis driver with the vesafb hack). When I play a dvd in windowed mode (720x576) with xine and I use XVideo the cpu(1.1Ghz P3) is utilized at 66% while playing with XShm the cpu is utilized only at 31% ! (the same with mplayer) This effect is the same at all colordepths (16bpp and 24bpp). I thought Xv should take the strain off the cpu a bit... Anyone has an idea what may cause the problem ? It is because the driver uses memcpy for transferring of the data. The correct way to solve this is to add dma support. In current cvs XF86 r128 does this so it can be used as a reference implementation. That's silly. Plenty of other drivers do this without DMA and have large performance increases over XShmPutImage - typically a factor of two savings with scaling for free. In the worst case XvShmPutImage should be comparable to XShmPutImage. Absense of DMA capability is not the problem. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Plane masking with Xlib??
On Tue, 18 Dec 2001, Ba la wrote: Hi Jim Mark, Thanks for the reply, my program is working in HP unix, I am able to get both the out put in a same window(overlayed), the only change in Linux code is in XtOpenDisplay() part, there in HPUX the function call using the display parameter as 0:0 and second one using 0:1. I don't understand this. 0:0 and 0:1 are two different screens. In Linux the display perameters with 0:1 is giving error, so I made it NULL for both the 0:1 describes the second head in a multihead setup. If you don't have two monitors this can't succeed. XtOpenDisplay() function calls, how to achive in Linux the same functionality, since I am using NULL as display parameter I am getting two different display, unable to achive overlay. I am new to this X-window programming and overlay concept, pls explain. You mentioned planemasks, now you say overlays. The two are not the same. Most PC hardware does not support overlays. You can do some overlay-type things with planemasks in 8bpp, but this is a rather archaic usage of the X-Window system. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
Ok here are the numbers. ;) 1.) playing a dvd windowed with xine / Xv %CPU 1477 root 16 0 57884 24M 10968 R60,4 11,0 0:25 X 1666 andre 10 0 21772 21M 10932 S 3,7 9,7 0:02 xine 1669 andre 9 0 21772 21M 10932 S 1,9 9,7 0:00 xine 2.) playing a dvd windowed with xine / XShm 1710 andre 17 0 34836 34M 14796 R28,1 15,5 0:08 xine 1477 root 9 0 61724 27M 14808 S 2,1 12,8 0:37 X 1712 andre 10 0 34836 34M 14796 S 0,9 15,5 0:00 xine With Xv the XServer is eating up all the cpu time... Thanks, -Andre. PS: xvinfo gives prints out this: X-Video Extension version 2.2 screen #0 Adaptor #0: SIS Video Overlay number of ports: 1 port base: 43 operations supported: PutImage supported visuals: depth 16, visualID 0x22 depth 16, visualID 0x23 number of attributes: 3 XV_COLORKEY (range 0 to 16777215) client settable attribute client gettable attribute (current value is 66046) XV_BRIGHTNESS (range -128 to 127) client settable attribute client gettable attribute (current value is 0) XV_CONTRAST (range 0 to 255) client settable attribute client gettable attribute (current value is 128) maximum XvImage size: 720 x 576 Number of image formats: 2 id: 0x32595559 (YUY2) guid: 59555932--0010-8000-00aa00389b71 bits per pixel: 16 number of planes: 1 type: YUV (packed) id: 0x32315659 (YV12) guid: 59563132--0010-8000-00aa00389b71 bits per pixel: 12 number of planes: 3 type: YUV (planar) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
On Tue, 18 Dec 2001, Mark Vojkovich wrote: On Tue, 18 Dec 2001, Peter Surda wrote: On Tue, Dec 18, 2001 at 03:07:29PM +0100, Andre Werthmann wrote: I have a laptop with a SiS630 chipset and use XFree86 4.1 (sis driver with the vesafb hack). When I play a dvd in windowed mode (720x576) with xine and I use XVideo the cpu(1.1Ghz P3) is utilized at 66% while playing with XShm the cpu is utilized only at 31% ! (the same with mplayer) This effect is the same at all colordepths (16bpp and 24bpp). I thought Xv should take the strain off the cpu a bit... Anyone has an idea what may cause the problem ? It is because the driver uses memcpy for transferring of the data. The correct way to solve this is to add dma support. In current cvs XF86 r128 does this so it can be used as a reference implementation. That's silly. Plenty of other drivers do this without DMA and have large performance increases over XShmPutImage - typically a factor of two savings with scaling for free. In the worst case XvShmPutImage should be comparable to XShmPutImage. Absense of DMA capability is not the problem. Note that the author said for the images of the same type. I.e. no scaling is going on. What I think happens is that XShmPutImage with sis is done using DMA (as DRM driver exists), but XvShmPutImage is not. Hence the difference in cpu consumption. Vladimir Dergachev Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
On Tue, Dec 18, 2001 at 10:16:11PM +0100, Andre Werthmann wrote: Ok here are the numbers. ;) 1.) playing a dvd windowed with xine / Xv %CPU 1477 root 16 0 57884 24M 10968 R60,4 11,0 0:25 X 1666 andre 10 0 21772 21M 10932 S 3,7 9,7 0:02 xine 1669 andre 9 0 21772 21M 10932 S 1,9 9,7 0:00 xine 2.) playing a dvd windowed with xine / XShm 1710 andre 17 0 34836 34M 14796 R28,1 15,5 0:08 xine 1477 root 9 0 61724 27M 14808 S 2,1 12,8 0:37 X 1712 andre 10 0 34836 34M 14796 S 0,9 15,5 0:00 xine With Xv the XServer is eating up all the cpu time... Well then I guess it is a driver problem. It could also be exactly what I said (DMA), because the %CPU shown isn't lineary proportional, because of how it's measured (100Hz timer interrupt). I remember when I did calculations previously to adding DMA to r128, a 2fold increase in data amount caused 35fold increase in the number shown. (All who think about response, please note I'm explicitely talking about NUMBER SHOWN, not real CPU usage). May I suggest to try other dvd player (e.g. vlc, www.videolan.org), and write back how the numbers look like there. Vlc also has lower CPU consumption than xine btw, perhaps it'll help. Also, please try to do Xv fullscreen and run top over ssh from other machine. Bye, Peter Surda (Shurdeek) [EMAIL PROTECTED], ICQ 10236103, +436505122023 -- Better Artificial Inteligence than Natural Stupidity msg02579/pgp0.pgp Description: PGP signature
Re: [Xpert]SiS630 Xv performance
On Tue, 18 Dec 2001, Vladimir Dergachev wrote: On Tue, 18 Dec 2001, Mark Vojkovich wrote: On Tue, 18 Dec 2001, Peter Surda wrote: On Tue, Dec 18, 2001 at 03:07:29PM +0100, Andre Werthmann wrote: I have a laptop with a SiS630 chipset and use XFree86 4.1 (sis driver with the vesafb hack). When I play a dvd in windowed mode (720x576) with xine and I use XVideo the cpu(1.1Ghz P3) is utilized at 66% while playing with XShm the cpu is utilized only at 31% ! (the same with mplayer) This effect is the same at all colordepths (16bpp and 24bpp). I thought Xv should take the strain off the cpu a bit... Anyone has an idea what may cause the problem ? It is because the driver uses memcpy for transferring of the data. The correct way to solve this is to add dma support. In current cvs XF86 r128 does this so it can be used as a reference implementation. That's silly. Plenty of other drivers do this without DMA and have large performance increases over XShmPutImage - typically a factor of two savings with scaling for free. In the worst case XvShmPutImage should be comparable to XShmPutImage. Absense of DMA capability is not the problem. Note that the author said for the images of the same type. I.e. no scaling is going on. What I think happens is that XShmPutImage with sis is done using DMA (as DRM driver exists), but XvShmPutImage is not. Hence the difference in cpu consumption. Vladimir Dergachev I don't see any Image acceleration at all in the sis driver in CVS. I do see while loops polling registers in the Xv code paths, however. The code would imply that you can only program the overlay during the retrace, hence polling until the retrace for every XvShmPutImage request. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
Mark Vojkovich ([EMAIL PROTECTED]): I don't see any Image acceleration at all in the sis driver in CVS. I do see while loops polling registers in the Xv code paths, however. The code would imply that you can only program the overlay during the retrace, hence polling until the retrace for every XvShmPutImage request. Seems like they'd do alot better just: while (!pOverlay-VBlankActiveFunc(pSIS)); and hope they don't enter the blank while they're writing those registers. If they really need to synchronize something on the retrace, is it easy to put functions in DRI so that you can queue a request in the kernel? Regardless this driver is busted. :( -- Billy Biggs [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance
On Tue, 18 Dec 2001, Billy Biggs wrote: Mark Vojkovich ([EMAIL PROTECTED]): I don't see any Image acceleration at all in the sis driver in CVS. I do see while loops polling registers in the Xv code paths, however. The code would imply that you can only program the overlay during the retrace, hence polling until the retrace for every XvShmPutImage request. Seems like they'd do alot better just: while (!pOverlay-VBlankActiveFunc(pSIS)); and hope they don't enter the blank while they're writing those registers. If they really need to synchronize something on the retrace, is it easy to put functions in DRI so that you can queue a request in the kernel? Regardless this driver is busted. :( Maybe they don't really need to synchronize and it's arbitrary that the code is there in the first place. I find it odd that their hardware doesn't handle this automatically. I didn't think it was that expensive to double buffer registers. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance (a bit better now)
In the sis driver in sis_video.c I have disabled the wait for a retrace in set_overlay, so the overlay could be programmed outside a retrace... I'm just testing it at this moment, but so far everything works good and finally playing a dvd in fullscreen with Xv works smoothly on my laptop. :) 1.) XF 4.1 -fullscreen (1024x768) with xine /Xv (unmodified sis_video.c) 1477 root 16 0 57896 24M 10972 R60,6 11,0 2:57 X 2119 andre 10 0 22256 21M 11068 S 2,1 9,9 0:05 xine 2122 andre 9 0 22256 21M 11068 S 1,3 9,9 0:00 xine 2.) XF CVS -fullscreen (1024x768) with xine /Xv (without waiting for a retrace) 2418 root 18 0 22204 18M 11016 R27,0 8,3 5:05 xine 2155 root 10 -1 55528 21M 11724 S7,1 10,0 0:37 X 2412 root 9 0 22204 18M 11016 S 2,5 8,3 0:33 xine -Andre. On Tue, 18 Dec 2001, Andre Werthmann wrote: 1.) playing windowed with mplayer / Xv %CPU 1477 root 19 0 49372 15M 2456 R66,6 7,2 1:02 X 2052 andre 15 0 6020 6020 2388 S29,3 2,6 0:09 mplayer 2.) playing windowed with mplayer / XShm 2057 andre 18 0 5828 5828 2580 R35,4 2,6 0:04 mplayer 1477 root 9 0 49576 16M 2660 S10,5 7,3 1:26 X 3.) playing fullscreen (1024x768) with xine / Xv 1477 root 16 0 57896 24M 10972 R60,6 11,0 2:57 X 2119 andre 10 0 22256 21M 11068 S 2,1 9,9 0:05 xine 2122 andre 9 0 22256 21M 11068 S 1,3 9,9 0:00 xine 4.) playing fullscreen (1024x768) with xine / XShm 2134 andre 18 0 45052 43M 24672 S26,7 20,1 0:17 xine 1477 root 18 0 71808 37M 24892 R24,8 17,3 3:32 X 2136 andre 9 0 45052 43M 24672 S 1,5 20,1 0:00 xine ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SiS630 Xv performance (a bit better now)
Andre Werthmann ([EMAIL PROTECTED]): I'm just testing it at this moment, but so far everything works good and finally playing a dvd in fullscreen with Xv works smoothly on my laptop. :) Out of curiousity, do you see any tearing? -- Billy Biggs [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]mga Xv double buffer patch
On Wed, 2001-12-19 at 02:50, Billy Biggs wrote: Michel Dänzer ([EMAIL PROTECTED]): It seems to work nicely here. How soon can this be applied to the X tree? Is there a reason it hasn't yet been applied? It was applied on December 10th. See the cvs-commit archives. Ah, thanks. I guess there's no chance it will be applied to 4_1-branch? Don't think so as it's a feature addition, not a fix. Besides, 4.2 is close. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRM/Radeon directly (w/o XFree86)?
On Mon, 2001-12-17 at 15:44, Aleksandr Koltsoff wrote: Knowing that I risk of sounding weird, I ask anyway: Where can I find information/sources/examples on how to access DRM directly (under Linux)? I've read the PI-docs on the subject but they're rather high-level and I suspect somewhat out of date. I'd like info on the present code and overall design. Basically what I need is: - put some surfaces into the video memory (also in memory trough agpgart, need info on that as well ;-) - surfaces may be RGBA (A meaning alpha, not 'Dont care'), or some YUV (packed or planar) - render these surfaces to the screen at each screen refresh (yes, I want to sync to the vertical retrace) at various locations on the screen - support for multiple graphics boards (some may be multihead, some not) Since radeon chips have three texture units and they're capable of color-space conversion, seems only logical I'd like to use them directly. I do have the specs for the chip itself (if you can call them specs ;-), but was wondering how to reuse existing code (since it exists) and also agpgart. I'm not interested in reimplementing DRI, just accessing DRM/agpgart. And I know it will be non-portable code. OR if there is any sensible and fast way of doing this trough OpenGL and with X (multiple radeons don't go with X) I'd like to hear about that too. This would probably be better suited for dri-devel, but basically the DRM is just another kernel interface. Look at the X server and DRI driver code for examples how to use it. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]No AGP and DRI with ATI Radeon Mobility M6
I have a new Compaq 1720CA laptop with an ATI Radeon card and I can't get AGP and direct rendering to work on it. Here's what I have: PIII 1 GHz, running Linux 7.2 ATI Radeon Mobility M6 (8 MB Video RAM) Kernel 2.4.16 (also tried with default RedHat 7.2 kernel, 2.4.7-10) No compiled with devfs, CONFIG_AGP=M, CONFIG_DRM_RADEON=M, CONFIG_DRM=Y XFree 4.1.0 I'm not sure whether the two problems are related or not. First, I cannot load the agpgart module (so no usable /dev/agpgart). When trying to load the module, I get init_module: No such device. Also, whatever I do, I cannot get direct rendering enabled: % glxinfo | grep direct direct rendering: No OpenGL renderer string: Mesa GLX Indirect Here's what I've tried so far: -Compiling agpgart and radeon support into the kernel instead of modules. That didn't change anything: In both cases I end up with no device connected to /dev/agpgart, and something connected to /dev/dri/card0 -I tried lowering the resolution to 1024x768 (instead of the default 1400x1050), as suggested in a similar thread. It made no difference at all. -Tried both 2.4.16 and 2.4.7 (redhat). No difference. -Tried doing a modprobe radeon before loading X. The modeprobe works, but it doesn't change anything with X. As I said, modprobe agpgart fails, so I can't get AGP. Another note: In order to get XFree to work at all, I had to add VideoRam 8192 to the Device section in my XF86Config-4. Otherwise, XFree detected 0 MB. I'm attaching both my XF86Config-4 and my XFree log. Does anyone have an idea of what the problem is? Thanks, Jean-Marc P.S. Please also CC to me directly, as I am not subscribed to the list. XFree86 Version 4.1.0 (Red Hat Linux release: 4.1.0-3) / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.7-0.13.1smp i686 [ELF] Build Host: stripples.devel.redhat.com Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Tue Dec 18 21:52:30 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Radeon (generic) (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc102 (**) XKB: model: pc102 (**) Option XkbLayout us (**) XKB: layout: us (**) Option XkbVariant basic (**) XKB: variant: basic (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.1.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000e9c0, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,3575 card , rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,3576 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,2482 card 0e11,009c rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2484 card 0e11,009c rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card , rev 41 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,248c card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,248a card 0e11,009c rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,2483 card 0e11,009c rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,2485 card 0e11,005c rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4c59 card 0e11,b11b rev 00 class 03,00,00 hdr 00 (II) PCI: 02:04:0: chip 14f1,2f00 card 0e11,8d88 rev 01 class 07,80,00 hdr 00 (II) PCI: 02:05:0: chip 104c,8023 card 0e11,b1b1 rev 00 class 0c,00,10 hdr 00 (II) PCI: 02:06:0: chip 104c,ac50 card ,
Re: [Xpert]Tearing, with regard to viewing DVDs
On Tue, 18 Dec 2001, Harley Klein wrote: If my guess is correct with regard to what tearing might be, I see tearing when viewing DVDs with the latest ogle release. I'm using the latest CVS release on my Toshiba Satellite 1805-S204. It has the Trident CyberBlade Ai1 chipset. Is the apparent tearing an issue with the driver in the CVS release or possibly the software? Although this isn't in response to the SiS630 driver, I thought it was a relevant question. It's usually a driver issue. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Font Problems after Upgrading to 4.1.0
I installed 4.1.0 and now all the fonts are just boxes..is there a missing file or a bug in the install I have tried multiple install techniques and no luck...thanks... -- Chris Ortega ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
